Skills-based hiring: from talk to verifiable practice

“We hire for skills, not for titles.” It’s one of the most repeated phrases in HR in recent years, and almost everyone subscribes to it. The problem is that, when you look closely at how those same companies decide, you find the usual: they filter by university, they prioritize the most prestigious CV, and the final decision comes out of an interview that each person ran their own way. The discourse changed; the practice, much less so.

Skills-based hiring is hiring for the skills and competencies the role needs, instead of for title or career history. But the difference between saying it and doing it isn’t about conviction, it’s about infrastructure: to really hire for skills, you have to be able to assess them in a verifiable and comparable way. Without that capability, skills-based hiring stays a nice slogan that doesn’t change any decision.

Why the discourse is easy and the practice is hard

Declaring that you value skills costs nothing. Verifying them does. And that’s where the real bottleneck is: a skill that isn’t measured consistently ends up being assessed by unreliable proxies —the name of the university, the years in the previous role, fluency in a conversation—. Those proxies are precisely what skills-based hiring claimed to want to leave behind, but they come back through the window when there’s nothing to replace them with.

The CV states skills, but it doesn’t demonstrate them. If your process keeps leaning on paper and impression, no matter how much you talk about competencies: you’re hiring just like before, with new vocabulary.

What verifiable practice looks like

Moving from discourse to practice requires a few concrete changes:

1. Translate the role into competencies, not credentials. Define which skills the position really needs —not which title usually has them— and turn them into something assessable. This means working with behavioral competencies instead of letterheads.
2. Assess those competencies with the same yardstick for everyone. Apply to each candidate the same assessment of the defined skills, to get a comparable signal. If each one demonstrates their skills differently, you can’t compare them.
3. Combine what the role asks for. Depending on the role, that can include a technical assessment of the concrete skill, a cognitive measure, and the position’s competencies. The guide to types of assessments helps you choose.
4. Decide with the evidence, not with prestige. When a candidate without the traditional CV demonstrates the competency, the approach consists precisely of giving their evidence the weight it deserves.

What skills-based hiring does and doesn’t do

It does: broaden the candidate pool by no longer filtering by credentials that don’t always anticipate performance; give an opportunity to those who have the skill even without the traditional title; and give you a comparable base to decide. It doesn’t: make bias disappear on its own —a poorly designed assessment can also bias—, or make every title irrelevant —in some roles it’s still a legal or technical requirement—. The approach provides a common, verifiable yardstick; careful design and interpretation with judgment remain yours.

In short

Skills-based hiring is hiring for the skills the role needs instead of for title or career history, but the difference between the discourse and the practice lies in being able to assess those skills in a verifiable and comparable way. Almost all companies say they do it; few change their decisions, because verifying competencies is harder than declaring them. Real practice requires translating the role into assessable competencies, measuring them with the same yardstick for everyone, combining the assessments the position asks for, and deciding with the evidence and not with prestige. Done this way, it broadens the talent pool and gives a comparable base; it doesn’t make bias disappear on its own or render every title irrelevant, but it turns a good intention into a process that really hires for skills.