What Skills-Based Hiring Actually Means (And What It Doesn't)
Everyone claims to do skills-based hiring now. Most of them are just removing degree requirements and calling it done. Here's what it actually takes.
Skills-based hiring is the most talked-about trend in talent acquisition right now. 85% of employers claim to use it. 53% have removed degree requirements from at least some roles. It's become a positioning statement, a press release, and — at most companies — not much else.
Here's the problem: removing a degree requirement isn't skills-based hiring. It's credential-blind hiring. The difference matters.
What credential-blind hiring looks like
You take 'Bachelor's degree required' off the job posting. You tell your team you're committed to opening up access. You continue to screen resumes the same way, with the same implicit signals — prestigious companies, recognisable brand names, career trajectory that looks like yours. The pipeline changes slightly. The decision-making doesn't.
This is better than hard credential gatekeeping. It's not skills-based hiring.
What skills-based hiring actually requires
True skills-based hiring means evaluating candidates on demonstrated ability in the competencies that predict success in the specific role — and it requires three things most companies skip:
Defining the competencies explicitly. Not 'strong communicator' or 'team player' — those are vibes. What specific decisions will this person make? What technical capabilities do they need on day one versus day ninety? What cognitive demands does the role actually place on them?
Measuring those competencies directly. This means work samples, structured interviews with validated questions, or cognitive assessments — not resume review, reference calls, or unstructured conversation. The measurement method has to be linked to the competency, or you're still screening on proxies.
Comparing candidates on the same criteria. If interviewer A evaluates 'problem-solving' through a case study and interviewer B evaluates it through a conversation about a past project, you don't have a skills-based process — you have two different processes happening in parallel.
Why most companies stall here
Building a genuine skills-based hiring process is operationally harder than it looks. Competency frameworks take time to develop. Structured interview questions have to be written and validated. Interviewers have to be trained to score consistently. For a company accustomed to 'we'll know it when we see it,' this feels like building a machine when you could be moving fast.
The irony is that the upfront investment pays back almost immediately. Shorter interview cycles. Better candidate comparisons. Fewer 'we hired the wrong person' post-mortems. The teams that do this work spend less time rehiring.
The AI acceleration
What AI changes is the cost of entry. Building a structured, competency-based evaluation process used to require a dedicated HR team and months of design work. AI can now handle the scaffolding — generating competency frameworks, writing structured interview questions, scoring candidates against rubrics consistently — which brings the operational overhead down to something a lean team can actually manage.
Skills-based hiring is worth doing. Just make sure you're actually doing it — not just removing the degree filter and moving on.
Umamy operationalises skills-based hiring with AI-generated competency frameworks and structured interviews built for lean teams.