Is skills-based hiring the same as dropping degree requirements?

No, and confusing the two is why most implementations fail. Removing a requirement takes a proxy away without putting evidence in its place, so the decision usually falls back on interview impressions, a less reliable signal than the degree was. Removing the proxy is the second step. The first is having something to replace it with.

Does skills-based hiring reduce bias?

It moves bias somewhere you can see it. Deciding in advance which capabilities the role needs, then scoring every candidate identically against them, makes the judgment explicit and arguable instead of leaving it as a feeling after a conversation. That's a real gain, though bias remains: someone still chose the capabilities.

How do you measure skills you can't test directly?

For most product roles you can't test the actual skill, because the skill is deciding under ambiguity over weeks. What you can observe is which action someone takes when the situation is described and no option is obviously right. That's what a situational judgment test does, and it's why the format exists.

Where should a small team start?

Write down the three capabilities the role can't do without, before you post it. Everything else (exercises, assessments, structured interviews) gets better once that exists, and none of it works without it.

What skills-based hiring actually means

By Sergio Gualda · 9 min read · Updated 23 September 2026

Skills-based hiring means the hiring decision rests on evidence of what someone can do, rather than on proxies for it such as a degree, a former employer, a job title or years served. The practical test is simple: if you removed the CV from your process entirely, could you still decide? If not, you aren't hiring on skills, whatever the policy says.

The definition, and a test for it

Every definition of skills-based hiring says roughly the same thing: assess what a person can do rather than where they've been. The definitions are fine. The trouble is that almost every company now says it hires this way, and almost none of them do.

So use a test that can't be talked around. Take your last hire. Remove the CV, the LinkedIn profile and the referral from the file, and ask whether what remains would have been enough to decide.

In most processes what remains is a set of interview impressions. Those tell you how someone talks about skill, which is a different thing from skill.

That's the distinction. Intent, policy and dropping the degree requirement don't settle it. What settles it is whether anything in the file would survive the CV being deleted.

What counts as evidence, in descending order of usefulness

Plenty of things called assessments produce no evidence. These are ordered by how much of the job they observe, whatever their rigour feels like.

Work the person did on the job, that you can verify and interrogate. The strongest and the rarest, since most of it is confidential or collaborative enough that attribution is guesswork.
A structured exercise every candidate does identically, scored against a rubric written before anyone submitted. It's comparable, and that matters most.
A situational assessment: what would you do here, with no correct option available. Weaker than watching someone work, stronger than watching them describe it, and the only one that scales to every candidate cheaply.
A structured interview with the same questions and a scoring guide for every candidate. Useful, and the cheapest upgrade most teams can make.
An unstructured interview. This isn't evidence. It measures fluency, similarity to the interviewer, and how the previous meeting went.
A portfolio or CV. It shows output plus presentation rather than skill, and since 2024 it doesn't reliably show either.

Why it took a technology shift to make this urgent

Skills-based hiring is an old idea that stayed optional for decades, because the proxies worked well enough. A degree from a known institution, four years at a company you respect, a portfolio with visible craft: none of those measured skill directly, but they correlated with it enough to sort a pile.

Generative AI broke the cheapest of those proxies. A polished portfolio, a well-written cover letter and a coherent case study can now be produced in an afternoon by someone who can't do the work. The correlation didn't weaken gradually. It broke for a whole class of evidence, all at once.

That's why companies that ignored the idea for twenty years are implementing it now. Conviction had little to do with it; the proxies stopped sorting.

Where skills-based hiring stops working

It has three limits, and any page that presents it as free is selling something.

First, it's more expensive up front. Writing a rubric, running a consistent exercise and scoring it takes hours that scanning CVs doesn't. The saving comes later, in hires that work out, and later is exactly when budgets stop paying attention.

Second, it doesn't remove judgment, it relocates it. Someone still decides which skills matter for this role, and that decision carries every bias the CV screen carried. The gain is that the decision is written down before candidates appear, which makes it arguable instead of invisible.

Third, skills are the wrong unit for some roles. For a first product hire at a five-person company, the question is less which skills someone has than whether they can operate with no support and no brief. That's closer to a disposition than a skill.

The cheapest version that works

You don't need a platform to start. You need three things, in this order, and each one is worth more than the tool you might buy instead.

Before anyone applies, write down the three things this role can't do without. Skip the job description; list the three capabilities whose absence makes the hire fail.
Give every candidate the identical exercise or the identical set of questions. Comparability does most of the work here, more than the content.
Score against a written rubric, separately, before anyone discusses. Discussion after independent scoring surfaces disagreement; discussion before it produces consensus around whoever spoke first.

Frequently asked

Is skills-based hiring the same as dropping degree requirements?: No, and confusing the two is why most implementations fail. Removing a requirement takes a proxy away without putting evidence in its place, so the decision usually falls back on interview impressions, a less reliable signal than the degree was. Removing the proxy is the second step. The first is having something to replace it with.
Does skills-based hiring reduce bias?: It moves bias somewhere you can see it. Deciding in advance which capabilities the role needs, then scoring every candidate identically against them, makes the judgment explicit and arguable instead of leaving it as a feeling after a conversation. That's a real gain, though bias remains: someone still chose the capabilities.
How do you measure skills you can't test directly?: For most product roles you can't test the actual skill, because the skill is deciding under ambiguity over weeks. What you can observe is which action someone takes when the situation is described and no option is obviously right. That's what a situational judgment test does, and it's why the format exists.
Where should a small team start?: Write down the three capabilities the role can't do without, before you post it. Everything else (exercises, assessments, structured interviews) gets better once that exists, and none of it works without it.