73% of companies say they’ve adopted skills-based hiring. Only 40% have actually removed degree requirements from their job postings. The gap between claiming it and doing it is enormous.
Three years after skills-based hiring became the headline shift in TA, most organizations are still using résumés as their primary filter. The language changed. The process mostly didn’t.
What “skills-based” actually means
In theory: you assess candidates on demonstrated capability, not proxy credentials. A computer science degree doesn’t prove someone can write production-quality code. A finance MBA doesn’t prove someone can model a leveraged buyout. A job title on a CV doesn’t prove someone led anything.
In practice, most orgs have done one or more of the following and called it skills-based:
- Removed the degree requirement from one category of roles
- Added a skills section to their ATS fields
- Run a pilot with a pre-hire assessment vendor
None of that changes how candidates are actually evaluated. The résumé is still the first filter. The interview is still unstructured. The decision is still made on pattern-matching against past candidates who worked out.
Why the assessment gap persists
The hard part of skills-based hiring isn’t the philosophy. It’s the measurement. How do you assess “stakeholder management” or “first-principles problem solving” at scale when you have 400 applications for a single role?
A few common answers, each with real limitations:
Pre-hire assessments (cognitive, personality, work samples) help at the top of the funnel. But they add friction and drop-off, and many hiring managers don’t trust them enough to let them gate interviews.
Résumé-based screening with AI can parse skills claims faster, but you’re still trusting candidate self-report. People optimize their résumés for the keywords recruiters are scanning for. Skills listed ≠ skills demonstrated.
Unstructured interviews let hiring managers “probe” for skills, but without a rubric, two interviewers walk away from the same candidate with completely different read-outs. There’s no consistent data, so there’s nothing to improve on.
What skills-based hiring needs that most orgs don’t have
A question framework tied to specific competencies. Not “tell me about a time you led a team” — that’s too broad. More specific: “Walk me through the last time you had to influence a decision without direct authority. What was the situation, what was your approach, and what happened?” Tied to a clear scoring rubric that defines what a 1, 3, and 5 look like.
Consistency across every interviewer. One interviewer asking about strategic thinking and another riffing through project history doesn’t give you comparable data. The same core questions, scored independently before the debrief, do.
Data that travels with the hire. Skills assessed in interviews need to be recorded in a format you can actually use — linked to the candidate record, comparable across applicants, and reviewable six months later against performance. If your structured interview data lives in scattered Notion docs, it doesn’t exist as a data asset.
The companies genuinely doing skills-based hiring aren’t just running assessments. They’ve rebuilt how they interview.
The résumé isn’t going away
Here’s the honest nuance: résumés aren’t worthless. Demonstrated experience is still a signal. The error is treating them as a skills proxy rather than a conversation-starter.
The skill isn’t on the résumé — it’s in what the candidate says when you ask them about it. Skills-based hiring is ultimately an interview design problem. The sourcing funnel, the assessment tools, the job posting language — those are inputs. The interview is where skills are actually verified.
Most orgs invested in the funnel. The interview is still where the process breaks down.
Casuro builds structured AI interviews around specific competencies — not job titles, not credentials. See how it works →
