Skills-Based Hiring: What the Shift Away from Degrees Actually Means for HR Teams

Moving past the degree requirement takes more than deleting a line from the job ad

Subscribe to our newsletter
By Rob Green
Skills-Based Hiring: What the Shift Away from Degrees Actually Means for HR Teams

Skills-based hiring has gone from a progressive talking point to a genuine strategic shift. More employers are dropping degree requirements, and the reasoning is sound: a diploma tells you someone completed a course, not that they can do the job. But saying "we're skills-based now" and actually operating that way are two very different things, and most HR teams underestimate the rebuild required to make it work.

Why the Old Model Is Breaking Down

Degree-based screening was never really about degrees. It was a proxy, a fast way to filter a large pool of candidates without evaluating actual capability. That shortcut made sense when applicant volumes were high and assessment tools were limited. It also quietly excluded huge pools of capable people, especially career-changers, self-taught specialists, and candidates from non-traditional backgrounds, while doing very little to predict on-the-job performance.

The pressure to change has come from both directions: skills gaps in fast-moving fields like tech and data, and a growing body of evidence that degree requirements correlate weakly with actual job success in most roles.

The Practical Changes That Actually Matter

1. Rewriting job descriptions around competencies, not credentials.
Removing "degree required" is step one, not the finish line. Job descriptions need to state the actual skills and outcomes the role demands, in specific, testable language. "Strong analytical skills" is not a competency. "Can build and interpret a cohort retention model in a spreadsheet" is.

2. Building real assessment into the process.
Without a degree as a filter, you need something else to evaluate capability, and that something has to be a genuine skills assessment, not a gut-feel interview. Structured work samples, scenario-based exercises, and role-relevant tests replace the credential as the signal. This is the part most organisations skip, and it's the part that actually determines whether skills-based hiring works.

3. Training hiring managers to interview differently.
Many hiring managers have spent their whole career screening on pedigree. Asking them to evaluate a self-taught candidate's actual capability instead of their CV pedigree requires new interview structures and, frankly, new confidence. Structured, competency-based interview guides matter more here than almost anywhere else in the process.

4. Reworking how internal mobility and promotion criteria work.
If external hiring drops degree requirements but internal promotion criteria still lean on them, you've created a credibility gap. Skills-based hiring only holds together if skills-based progression follows it through the whole employee lifecycle.

5. Auditing your ATS and screening rules.
A lot of organisations announce they're skills-based while their applicant tracking system is still configured to filter out anyone without a degree field completed. If the technology behind the process hasn't changed, the policy hasn't either. This is one of the most common and most avoidable gaps.

Where This Gets Hard

The honest challenge is volume. Skills assessments take longer to build and longer to run than a CV scan. For high-volume roles, that's a real operational cost, and it's why so many skills-based hiring initiatives quietly regress back to credential shortcuts under time pressure. Getting this right takes the right technology stack behind the process, not just a policy change on paper.

Where Rectec Fits In

This is exactly the kind of shift where picking the right HR technology matters. Whether it's an ATS built for structured, skills-based screening or assessment tools that plug cleanly into your existing stack, the right fit varies enormously by organisation size and hiring volume. Rectec's market data and vendor comparisons help HR teams identify which platforms genuinely support competency-based hiring workflows, rather than just adding a "skills" tag to a CV filter, so the technology actually keeps pace with the policy.

FAQs

Does skills-based hiring mean removing all education requirements?
No. Some roles genuinely require a specific qualification, particularly regulated professions. Skills-based hiring means removing degree requirements where they act as an unnecessary proxy rather than a real requirement, and evaluating actual capability everywhere else.

How do you assess skills without adding significant time to the hiring process?
Short, role-specific work samples or scenario exercises are usually faster than a full-length technical interview and give a clearer signal than a CV review. The upfront investment is in designing the assessment well, not in running it.

What happens to internal employees without degrees under this model?
They should benefit. If promotion and internal mobility criteria are also rebuilt around demonstrated skills, employees who were previously capped by credential requirements gain a genuine path forward.

Is skills-based hiring only relevant for technical roles?
No. It applies just as well to sales, operations, and creative roles, anywhere a portfolio, work sample, or structured scenario can demonstrate capability more accurately than a qualification can.

How do we know if our ATS is actually supporting skills-based hiring?
Audit the filters and default screening rules. If a candidate without a degree field completed is still being auto-rejected or ranked lower, the system is undermining the policy, regardless of what the job description says.