What it is
Skills-based matching screens and ranks candidates against the specific skills a role requires, instead of the proxies recruiters have traditionally relied on: a named degree, a job title at a recognisable company, or a minimum number of years in the market. A candidate with the right skills but an unconventional background clears the bar; a candidate with an impressive title but a gap in the actual skill set does not.
The shift is from credentials that imply capability to evidence that demonstrates it. "5 years experience" is a proxy that assumes a skill was learned along the way. "Built and shipped production Node.js services on AWS" is the skill itself, stated directly. Skills-based matching scores the second kind of statement, wherever it comes from in a candidate's history.
A CV headline says where someone worked. A skills match says whether they can actually do the job.
Why it matters
Around one in five US job postings has already dropped a formal degree requirement, and LinkedIn's Economic Graph research finds that a skills-first approach can widen the addressable candidate pool by up to 19x in some sectors once degree and pedigree filters come off. Clients increasingly brief roles on capability, not credentials, and a shortlist built on titles alone increasingly gets rejected for missing candidates who would have been an obvious fit on skills.
For a desk, the payoff is fewer wasted screens and fewer rejected shortlists. A candidate who is strong on paper but weak on the actual skill set costs a call and a client's patience. A candidate who looks unconventional on paper but strong on skills is often the placement a keyword search would have filtered out before anyone looked twice.
How boilr handles it
In boilr, skills-based matching is the default way every shortlist gets built. You brief the role once, including the must-have skills, and your AI sales employee scans LinkedIn, GitHub, referral networks and passive pools, checking each profile against those skills specifically rather than title or tenure alone. The shortlist that lands in your Tasks inbox shows a match rationale broken down by criterion, for example "Skills: Node.js, Postgres, AWS - 6/6 matched", alongside seniority and location, so you see exactly which skills matched and which did not before you spend a minute on the call.
Because the criteria are explicit rather than implied by a job title, you can loosen or tighten them mid-search and boilr re-runs immediately with the new bar. Pipeline conflicts are flagged before a candidate reaches you, and the whole match, including which skill combinations actually convert to placements on your desk, flows into the Company Brain, so the next similar role starts from what already worked.
