Hiring for skills, not degrees: how to start

Hiring for skills, not degrees, starts by translating each role into the competencies it actually needs and assessing them on the same scale for every candidate. It’s not a change of rhetoric, it’s a change in what information you use to decide: instead of filtering by the university or the name of the previous employer, you filter by comparable evidence of what the person can do. And you don’t have to overhaul your entire process: one well-executed first move is enough.

Almost every hiring team says they want to do it. The missing step is almost always the same: how it’s actually done, in concrete terms, without dismantling the process you already have. This guide breaks it down into three steps, starting with a single role.

Step 1: translate the role into skills, not credentials

The original mistake is describing the role by the profile that “usually holds it” —this degree, this many years, this industry— instead of by what the person will have to do. Flip the order. Write down what they have to achieve in their first 90 days and what competencies they need to achieve it: communication, analysis, results orientation, whatever the role truly calls for.

That list of competencies is your new role description. The guide to choosing competencies by role helps you make this translation without inventing requirements the role doesn’t need.

Step 2: assess those competencies on the same scale

Defining the skills isn’t enough if each candidate then demonstrates them in their own way. The key to the approach is consistency: all applicants for the role go through the same assessment of the same competencies, so you can compare signal with signal and not impression with impression.

The CV claims skills but doesn’t demonstrate them. Assessing before interviewing gives you a comparable baseline the paper can’t, and leaves the interview to dig deeper into evidence, not to guess.

Step 3: decide with the evidence, not the prestige

The moment of truth is when a candidate shows up without the traditional CV but with the competency demonstrated. Hiring for skills consists, precisely, of giving that evidence the weight it deserves, instead of discarding them for not coming from the “expected” place. That’s where the approach widens your talent pool: you stop excluding from the outset those who can do the job.

This doesn’t mean banning credentials. Where the degree is a legal or technical requirement, it remains so. It means no longer using it as a shortcut when what matters is the skill.

Start with one role, not all of them

Don’t overhaul your entire hiring at once. Pick one role, translate it into competencies, define the common assessment, and run a full process that way. You’ll learn which competencies best fit the day-to-day of that role and which assessment gives you the most useful signal. That pilot becomes the template for the next roles. Skills-based hiring isn’t decreed, it’s built, and it’s built one role at a time.

In summary

Hiring for skills, not degrees, starts by translating each role into the competencies it actually needs and assessing them on the same scale for every candidate, so you decide with comparable evidence instead of prestige. It doesn’t require banning credentials —where the degree is a requirement, it remains so— or overhauling your entire process overnight: it requires starting with one role, defining its competencies well, and giving evidence the weight the name brand used to have. Done this way, you widen the talent pool and gain a comparable baseline; it can help reduce the weight of some biases, though the final decision is still yours. To see how a role’s skills translate into assessable competencies, explore the library.