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, which usually means the decision 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 it somewhere you can see. Deciding in advance which capabilities the role needs, then scoring every candidate identically against them, makes the judgment explicit and arguable instead of arriving as a feeling after a conversation. That is a real gain, and it is not the same as removing bias — someone still chose the capabilities.

How do you measure skills you cannot test directly?

For most product roles you cannot test the actual skill, because the actual 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 is what a situational judgment test does, and it is why the format exists.

Where should a small team start?

Write down the three capabilities the role cannot 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 18 August 2026

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

The definition, and the test that makes it real

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

So use a test that cannot 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 — which are not evidence of skill, they are evidence of how someone talks about skill.

That is the whole distinction. Not the intent, not the policy, not whether you dropped the degree requirement. Whether there is anything in the file that would survive the CV being deleted.

What counts as evidence, in descending order of usefulness

Not everything called an assessment produces evidence. These are ordered by how much of the actual job they observe, not by how rigorous they feel.

Work the person did on the job, that you can verify and interrogate. Strongest, and rarest — 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. Comparable, which is the property 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. Genuinely useful, and it is the cheapest upgrade most teams can make.
An unstructured interview. Not evidence. It measures fluency, similarity to the interviewer, and how the previous meeting went.
A portfolio or CV. Not evidence of skill; evidence of output plus presentation, and since 2024 not reliably evidence of 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 narrative can now be produced by someone who cannot do the work, in an afternoon. The correlation did not weaken gradually; it broke for a specific class of evidence, all at once.

That is why the same companies that ignored this idea for twenty years are implementing it now. Not conviction — the proxies stopped sorting.

Where skills-based hiring stops working

Three honest limits, because a page that presents this as free is not describing anything real.

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

Second, it does not 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 now written down before candidates appear, which makes it arguable rather than 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, and that is closer to a disposition than a skill.

The cheapest version that actually works

You do not 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.

Write down what this specific role cannot do without — three things, before anyone applies. Not a job description: the three capabilities that, if missing, make the hire fail.
Give every candidate the identical exercise or the identical set of questions. Comparability is doing most of the work here, not 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, which usually means the decision 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 it somewhere you can see. Deciding in advance which capabilities the role needs, then scoring every candidate identically against them, makes the judgment explicit and arguable instead of arriving as a feeling after a conversation. That is a real gain, and it is not the same as removing bias — someone still chose the capabilities.
How do you measure skills you cannot test directly?: For most product roles you cannot test the actual skill, because the actual 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 is what a situational judgment test does, and it is why the format exists.
Where should a small team start?: Write down the three capabilities the role cannot do without, before you post it. Everything else — exercises, assessments, structured interviews — gets better once that exists, and none of it works without it.