Skills-Based Hiring Was Supposed to Fix This. It Didn't.
Three years ago, skills-based hiring was the thing everyone in talent acquisition as supposed to be doing. Drop the degree requirement, assess capability, not pedigree and open the door to people who could actually do the job but had never had the credential that used to be the price of entry.
I was fully behind it and I still am, in theory.
The theory was right. The problem is what happened when theory met a real ATS, a real hiring manager, and a real final interview panel.
Most companies did not remove anything. They added something.
A skills assessment got bolted onto the front of the existing process. Sometimes a coding test, sometimes a case study, sometimes a structured work-sample exercise. Candidates now had one more hoop, and for a while the language around it was genuinely optimistic: wider pools, fairer shortlists, less bias toward the same three universities.
Here's what didn't change. The degree requirement usually stayed in the ATS filter, doing its old job further up the funnel, invisible to anyone who wasn't looking for it. Even where it was formally removed from the job description, recruiters kept sourcing the way they always had, on LinkedIn, searching the same universities and the same "recognisable" employers, because that's what the search filters made easy.
And even when a candidate without the traditional pedigree made it all the way through the skills assessment and landed in the final interview, something predictable happened. Faced with two similarly scored candidates, one with a familiar CV and one without, hiring managers defaulted to the familiar one. Not out of malice. Out of the same instinct that's driven hiring decisions for decades: the familiar feels safer, and nobody gets fired for hiring someone who looks like the last five successful hires.
The skills test didn't remove that instinct. It just added a step before the instinct got to make the decision anyway.
Why the data still looks good on paper
Ask most TA leaders how their skills-based hiring initiative is going, and you'll hear something like "we've seen a 15% increase in candidates without a degree entering our pipeline." True, probably. And almost entirely beside the point, because entering the pipeline was never the hard part. The hard part was always the moment a human with a preference makes the final call, and that moment hasn't been touched.
This is the thing about implementing half a solution is that it produces metrics that look like progress. More diverse applicant pools. Better top-of-funnel numbers. A press-friendly stat for the careers page. None of it tells you whether who actually gets hired has changed, because almost nobody is tracking that specific number, the one that would actually prove or disprove the whole initiative.
I've sat in enough internal meetings to know how this goes. Someone presents the pipeline stat, the room nods sagely and nobody asks for the offer-acceptance breakdown by the same category, because that's the number that would actually complicate the story.
What it would take to make this real
If you're serious about skills-based hiring actually changing outcomes, not just optics, there are three things that matter more than the assessment itself.
Remove the filter, not just the language. If your ATS is still screening on degree or "top tier" employer history behind the scenes, saying "we don't require a degree" in the job ad is decoration.
Blind the CV at the point the skills score gets reviewed. If a hiring manager sees the assessment result and the CV at the same time, the CV wins more often than you'd like to admit. Separate them, even just for the shortlisting conversation.
Track who actually gets the offer, not who enters the pipeline. If your skills-based candidates are getting interviewed at the same rate as before but hired at a lower rate, you don't have a sourcing problem, you have a decision-making problem, and no amount of top-of-funnel diversity fixes that.
None of this is complicated, you know how to do this, but it’s all a bit awkward because it means telling hiring managers their gut instinct isn't as reliable as they think, and that conversation goes about as well as you'd expect.
Where this actually lands
I don't think skills-based hiring failed because the idea was wrong. I think it failed the way most good ideas fail inside big organisations: it got implemented as an addition rather than a replacement, because addition is easier to sell and easier to roll back if someone complains.
The companies that actually see different outcomes from this are the ones willing to remove something, not just add something. Most aren't willing to do that yet. So we're left with a lot of assessment tools generating a lot of data that mostly proves the old bias is still running underneath, just with better spreadsheets to hide in.
The idea wasn't the problem. Nobody had the nerve to finish implementing it.
About
Martin Dangerfield, Talent Acquisition Strategist. Straight-talker. Community builder. Talent Strategy Director at the rec hub,
I help in-house TA teams get better with a combination of sharper strategies, smarter hiring, and no-nonsense support. Since selling my business, I have been helping to grow the rec hub in its global mission to deliver an amazing embedded recruitment solution. I've built TA teams from scratch, scaled global functions, sold a business, and consult on all things talent acquisition.
I run #truManchester and #truLeeds because I believe the best ideas don't come from panels, they come from people talking honestly in a room. I'm not here for buzzwords or silver bullets.
I'm here to help TA people do the job properly.
South African-born, UK-based, and European in perspective, I'm Gen X, proud of it, and not afraid to say what others won't.
This is the work I care about. If you care too, stick around.