Is skills-based hiring slower?

Slower to set up, often faster to conclude. Writing the rubric and building the exercise costs hours before the role opens. After that, comparing eight scored results takes less time than reconciling eight sets of interview impressions across four people's calendars.

Do we have to abandon CVs completely?

No, and a policy that bans them tends to get quietly ignored. A CV is fine as context — where someone has worked tells you what environments they know. The change is that it stops being what the decision rests on.

Does this work for senior hires?

It matters most for senior hires, which is the opposite of how most companies deploy it. Senior candidates present well by definition — presenting is part of the job — so the interview signal is at its weakest exactly where the cost of a mistake is highest.

Skills-based hiring vs traditional hiring

By Sergio Gualda · 8 min read · Updated 18 August 2026

Traditional hiring sorts candidates on proxies — degree, employer, title, tenure — which is fast, cheap and works as long as the proxies stay correlated with ability. Skills-based hiring sorts on demonstrated ability, which is slower and more expensive up front and produces fewer wrong hires. The trade is not accuracy against speed in general; it is a small fixed cost per role against a large variable cost per mistake.

What each one is actually optimising for

Traditional hiring optimises for throughput. A recruiter with two hundred applications and a week has to reduce that pile using something readable at a glance, and a CV is exactly that. It is not laziness — it is the only tool that operates at the speed the funnel demands.

Skills-based hiring optimises for the cost of being wrong. It accepts a slower top of funnel in exchange for a decision that rests on something you could defend to the person you rejected.

Which is correct depends entirely on the ratio between those two costs. Hiring forty support agents: throughput wins, and it is not close. Hiring the second product designer at a twelve-person company: the mistake costs a year, and no amount of screening speed compensates.

Side by side, without the marketing

Every row below is a genuine trade rather than a win. If a comparison of these two only lists advantages on one side, it was written to sell something.

Speed to shortlist: traditional wins clearly. Reading CVs is faster than running anything.
Cost per candidate: traditional wins. Skills-based costs money or time per person assessed.
Comparability: skills-based wins outright. Two CVs are not comparable on any axis that matters; two identical exercises are.
Defensibility: skills-based wins. A rubric score can be shown to a rejected candidate. A hiring manager's impression cannot.
Access to non-obvious candidates: skills-based wins, and this is where the measurable business case lives. Proxies systematically hide career changers, self-taught people and anyone from an unfamiliar market.
Resistance to AI-generated applications: skills-based wins, but only for formats that do not reward polished output.
Setup effort: traditional wins. Skills-based requires deciding what the role needs before anyone applies, and that is the step teams skip.

The two failure modes, which are not symmetrical

Traditional hiring fails silently. You never meet the person you filtered out, so the mistake leaves no evidence anywhere in your funnel — and a process whose errors are invisible cannot improve, because there is nothing to learn from.

Skills-based hiring fails loudly. A bad rubric produces a score you can point at and argue with, and someone will. That feels worse and is much better: an error you can see is an error you can fix.

This asymmetry explains why traditional processes feel reliable. They are not producing fewer mistakes; they are producing mistakes nobody has to look at.

The hybrid most teams actually end up with

Almost nobody runs either one purely, and the mix that works is not a compromise — it is using each where it is strong.

Use proxies where the volume is high and the cost of a wrong rejection is low: the top of the funnel, the first cut, the roles you hire ten of. Use evidence where the volume is low and a wrong hire is expensive: the shortlist for a senior role, the first hire in a function, anyone who will set the standard for people hired after them.

The mistake is running it the other way round, which is more common than it sounds — heavy assessment on juniors because they will tolerate it, and a conversation over coffee for the senior hire because it would be awkward to ask.

Frequently asked

Is skills-based hiring slower?: Slower to set up, often faster to conclude. Writing the rubric and building the exercise costs hours before the role opens. After that, comparing eight scored results takes less time than reconciling eight sets of interview impressions across four people's calendars.
Do we have to abandon CVs completely?: No, and a policy that bans them tends to get quietly ignored. A CV is fine as context — where someone has worked tells you what environments they know. The change is that it stops being what the decision rests on.
Does this work for senior hires?: It matters most for senior hires, which is the opposite of how most companies deploy it. Senior candidates present well by definition — presenting is part of the job — so the interview signal is at its weakest exactly where the cost of a mistake is highest.