About 64.8% of companies now report applying skills-based hiring practices, and 75% have rewritten job descriptions around explicit competencies rather than degrees or job titles, according to NACE. But rewriting the job posting is the easy half. Most companies making this shift still run the interview itself the same unstructured way they always have, which means the guesswork they removed from the resume screen quietly reappears in the interview room.
Skills-based hiring has crossed from trend to default
This is no longer an experiment at a handful of progressive employers. It's the default approach at a majority of companies tracked by NACE, and it shows up on both ends of the process.
The part most companies skip
Defining the skills a role needs is genuinely useful work. It forces alignment on what "good" looks like before anyone starts sourcing candidates. But a competency-based job description doesn't evaluate anyone by itself, the interview does, and that's where a lot of skills-based hiring initiatives quietly stall. Separate research on 2026 hiring practices found that 68% of hiring leaders now cite hands-on skill demonstration as the most trusted signal in an interview, well ahead of resume credentials or unstructured conversation. Trusting demonstration more is the right instinct. It just requires an interview built to capture it consistently.
What "structured" actually adds on top of "skills-based"
This is the distinction that gets lost. A skills-based job requisition tells you what to look for. A structured interview is what actually ensures every candidate gets evaluated against that same bar, by every interviewer, in a way you can compare afterward. Industry analyses of 2026 hiring data put structured interview formats at roughly double the predictive validity of unstructured ones, meaning they're substantially better at actually predicting who will succeed in the role. Skills-based sourcing without structured evaluation gets you a better-targeted candidate pool and the same inconsistent decision-making at the finish line.
A skills-based job description defines the bar. Only a structured interview proves who actually cleared it.
On where skills-based hiring initiatives stall in practice
Turning a skills-based req into a skills-based interview
In practice, this means three things happening together, not in sequence. The competencies defined for the role need to become the actual interview questions and the actual scorecard, not a separate document nobody references once interviews start. Every interviewer needs to score against that same rubric, not their own read of the conversation. And the evidence for each score, what the candidate actually said or demonstrated, needs to be captured well enough that a hiring committee can check it later instead of taking one interviewer's word for it.
The practical takeaway: if your job descriptions list skills but your interview guide is still a loose list of "get to know them" questions, the mismatch between the two is where good candidates are still getting evaluated on gut feel.
The bottom line for hiring leaders
Skills-based hiring is well past the point of needing a pitch. The open question for most companies isn't whether to adopt it, it's whether the interview itself has caught up to the job description. Closing that gap, defined competencies, a shared rubric, and a documented record of how each candidate measured up, is what turns a skills-based hiring philosophy into a skills-based hiring result.