SKILLS-BASED HIRING ISN'T FAILING. IT NEVER ACTUALLY STARTED.

Somewhere in the last two years, a talent leader got a directive from leadership: go skills-based. No budget attached to it. No timeline. No mention of what the current interview process would need to change to actually support it. Just the instruction, dropped into a strategy meeting like it was a simple toggle to flip.

If that sounds familiar, you're not imagining the gap between what you were asked to do and what you were actually given to do it with. And you're also not the exception. You're the norm.

Skills-based hiring is, by most measures, the most talked-about hiring trend heading into 2026. A recent McLean & Co. survey found that it had the strongest level of implementation, planned or existing, of any emerging HR trend this year. Everyone is adopting it, or says they are. What almost nobody is talking about is why the results underneath that adoption keep landing somewhere between modest and nonexistent. That gap is the actual story, and it's the one worth writing about, because it's the one that will keep costing talent leaders credibility, budget, and time if it stays unnamed.

What skills-based hiring actually means

At its core, skills-based hiring is a simple idea. Instead of screening candidates primarily on credentials such as a college degree or years in a specific job title, you evaluate them on the specific, demonstrable skills the role actually requires. It's meant to widen the candidate pool, reduce the bias baked into credential-based filtering, and get closer to a real signal of whether someone can do the job.

In practice, most companies have implemented a much smaller version of that idea. They removed the degree requirement from the job posting. That's it. The posting language changed. The actual mechanics of how a candidate gets evaluated, who makes the call, and what evidence that decision is based on largely stayed the same. That distinction between the policy and the practice is where this entire trend either delivers or quietly fails, and right now it's mostly failing.

Why the adoption numbers don't match the outcome numbers

The intent-to-action gap isn't unique to skills-based hiring. The same HR Dive roundup that flagged skills-based hiring as the top trend also noted that 54% of HR leaders believe AI-specific upskilling will have high organizational impact, yet only 1% had actually implemented a strategy for it as of last year. This is a pattern across HR right now, not a one-off complaint about a single initiative. Leaders are naming the right priorities faster than their organizations can build the infrastructure to act on them.

Skills-based hiring shows the same pattern, but there's now a rigorous body of research behind it that makes the gap impossible to argue away. A joint study from Harvard Business School's Managing the Future of Work project and the Burning Glass Institute tracked what actually happened at companies that removed degree requirements from job postings. The findings are stark. For all the announcements and press releases, the increased opportunity promised by skills-based hiring showed up in fewer than 1 in 700 hires. For every 100 postings that dropped a degree requirement, fewer than four additional candidates without degrees were actually hired into those roles.

The researchers sorted the companies they studied into three groups. Roughly 45% made the change in name only, meaning their actual hiring behavior didn't shift in any meaningful way after the requirement disappeared from the posting. About one in five were what the study called backsliders, companies that saw a short-term bump in hiring accessibility that faded over time and didn't stick. Only a minority, the group the researchers called skills-based hiring leaders, made real change. Those firms increased their share of non-degree hires by nearly 20%, and it wasn't cosmetic. It came with results: non-degree hires at leading firms had a retention rate 10 percentage points higher than their degreed colleagues, and non-degree workers hired into roles that used to require a degree saw an average salary increase of 25%.

That's the part of this story that rarely makes it into the trend pieces. Skills-based hiring isn't a bad idea that doesn't work. It's a good idea that most companies never actually built. The ones who did build it are seeing real returns. The ones who didn't are the reason the trend has a credibility problem.

Joseph Fuller, the Harvard professor who led the research, put the core issue plainly in an interview with Forbes: "Process eats policy for lunch."

A hiring manager looking at three similar candidates, one with a degree and two without, will still default to the credentialed candidate unless something beyond the job posting actually changes. Removing a line item from a listing doesn't retrain a manager's instincts, and it doesn't give them a better way to evaluate what they're actually looking at.

The Skills-Based Hiring Gap

This is the pattern we see constantly in our work with talent leaders, and it's why we think about skills-based hiring through three layers instead of one policy decision. We call it the Skills-Based Hiring Gap, because the gap isn't between wanting this to work and it not working. The gap is between the one layer companies actually build and the two they skip.

Define. Assess. Calibrate. Most organizations stop at the first word.

Layer one: Define

This is the easy layer, and it's the one nearly every company gets to. Someone decides that a given role doesn't actually require a four-year degree, updates the job posting, maybe adds a line about "equivalent experience," and moves on. It costs almost nothing, it looks good externally, and it can be done in an afternoon. That's exactly why it's not enough on its own. A definition without a way to act on it is a statement of intent, not a hiring process.

Layer two: Assess

This is where the real cost lives, and it's the layer most companies quietly skip. Actually evaluating whether a candidate has a skill, in a structured, consistent way, requires building something: a work sample, a scored exercise, a rubric that multiple evaluators can apply the same way. It takes time to build, budget to run, and buy-in from hiring managers who are used to making faster, gut-level calls. Without it, "skills-based" interviewing often just becomes a conversation where the interviewer decides whether they like how the candidate talked about their experience. That's not a different hiring method. That's the same subjective process wearing a new label.

Layer three: Calibrate

This is the layer almost nobody names, and it's the most important one. Even with a real assessment in place, does every hiring manager evaluating that assessment apply the same bar? Does "strong" mean the same thing to the manager in engineering as it does to the one in sales? Without calibration, you haven't removed bias from the process. You've moved it downstream, out of the resume screen and into the interview room, where it's harder to see and even harder to audit. This is also exactly the failure mode a recent Software Advice survey of 1,000 HR leaders identified as an emerging problem for 2026: something researchers are calling "skillfishing," where candidates exaggerate skills on resumes or in interviews, aided by AI tools that make it easier to sound qualified than to be qualified. Without a calibrated way to actually test for the skill rather than just talk about it, skills-based hiring becomes exactly as easy to game as the credential-based process it was supposed to replace.

What it costs to skip layers two and three

The cost of stopping at layer one isn't neutral. It's not a wash. It shows up as mis-hires who interview well and underperform once they're actually doing the job, because nothing in the process tested for the skill directly. It shows up as inconsistent hiring bars across teams that quietly damage internal equity. And when leadership eventually asks why the skills-based hiring initiative "isn't working," the trend takes the blame for a system that was never actually built. That's the part that should worry talent leaders most. You inherit the reputational risk of an initiative you were never resourced to execute properly.

A quick way to check where your organization actually stands

Before you can make the case for what's missing, it helps to know exactly where the gap is. Ask three questions about a role you've recently hired for under a "skills-based" label.

Did you define the specific skills the role requires in concrete, observable terms, rather than general categories like "strong communicator" or "self-starter"? That's layer one.

Did candidates go through a structured assessment, something scored or evaluated consistently, rather than a conversation where the interviewer formed an impression? That's layer two.

Do you know whether two different hiring managers evaluating the same candidate against the same assessment would land on the same conclusion, and has anyone actually checked? That's layer three.

Most organizations can answer yes to the first question, answer it uncertainly for the second, and have no idea for the third. That's not a criticism. It's simply where the trend actually stands right now, for almost everyone.

Making the case for the budget

If you're the talent leader who got the "go skills-based" directive without the resources to build layers two and three, the research above is useful for more than context. It's ammunition. You now have a credentialed, well-documented case that the version of skills-based hiring most companies are running doesn't produce the outcomes leadership is expecting, and a clear explanation of why: it's missing the two layers that actually determine whether it works. That reframes the conversation from "we need more budget for a nice-to-have" to "the initiative leadership already approved needs two more components to deliver the return they're expecting." That's a fundamentally different ask, and it's one grounded in outside research rather than internal opinion, which tends to travel further in a budget conversation.

The work underneath the trend

Skills-based hiring was never really the problem. The problem is the same one we see across almost every hiring initiative that gets adopted as a policy change instead of a system change: the first, visible, low-cost step gets taken, and the harder, more expensive work that actually determines the outcome gets left for later, and later rarely comes. Skills-based hiring can genuinely widen your candidate pool, reduce reliance on a flawed credentialing signal, and improve retention and performance, but only for the organizations willing to build all three layers, not just the one that fits in a press release.

Frequently asked questions

Does skills-based hiring actually reduce bias?

It can, but only when the assessment and calibration layers are built out. Removing a degree requirement alone tends to shift bias rather than remove it, since hiring managers without a structured way to evaluate skills often default back to familiar signals like pedigree or communication style.

Is skills-based hiring realistic for an early-stage startup?

Yes, and in some ways it's easier to do well at a smaller scale, since there are fewer hiring managers to calibrate and less legacy process to unwind. The risk for early-stage companies is usually skipping straight to layer one without ever building a lightweight version of layers two and three, which tends to show up later as inconsistent hiring quality as the team scales.

What's the difference between skills-based hiring and competency-based hiring?

The terms are often used interchangeably, but skills-based hiring typically refers to the broader shift away from credential requirements toward evaluating specific, job-relevant skills. Competency-based hiring usually refers to the structured interview and assessment methodology used to actually measure those skills. In the framework above, competency-based methods are what layer two is built from.

How long does it actually take to build real skills-based hiring infrastructure?

For a single role, building a defensible assessment and calibration process typically takes a few weeks of focused work, not months, but it does require dedicated time from someone who owns it, not something added to an already full workload. The organizations that succeed tend to treat it as a defined project with an owner, rather than an ongoing aspiration.

Do Better Consulting works with talent leaders who are ready to build the infrastructure behind the initiatives they've already been asked to run. If this is the gap you're standing in, book a consultation.