What Is Skills-Based Hiring? How It Works and Why More Companies Are Adopting It

Skills-based hiring is a recruiting approach that evaluates candidates based on demonstrated ability to do a job rather than on proxy credentials like degrees, job titles, or years of experience at specific companies. The shift in language from “qualified” (as defined by credentials) to “capable” (as defined by evidence of skills) sounds simple. The operational changes required to implement it are significant.

The approach is gaining traction because a growing body of evidence suggests that credentials are poor predictors of job performance across many roles, that the labor market for credentialed candidates is more competitive and expensive than it needs to be, and that a skills-based approach expands the talent pool while often improving the quality of hires.

This guide explains what skills-based hiring actually means in practice, the evidence for its effectiveness, how to implement it, and where it works and does not work.

What Skills-Based Hiring Actually Means

The term is used loosely, so a precise definition is useful.

Skills-based hiring is not:

Eliminating all consideration of experience
Hiring anyone who claims to have a skill
Removing all filtering criteria from job requirements

Skills-based hiring is:

Removing credential requirements (degrees, certifications, specific company name-dropping) that are not predictive of job performance in favor of requirements tied to actual capability
Evaluating candidates on demonstrated skills through work samples, assessments, structured interviews, or portfolio review rather than inferring capability from credentials
Defining job requirements in terms of what someone needs to do and demonstrate, not what their resume needs to say

The practical change is in how job requirements are written and how candidates are evaluated. A traditional job posting might require “Bachelor’s degree in Computer Science and 5+ years of experience at a software company.” A skills-based equivalent might specify “Ability to independently design and implement REST APIs, demonstrated through code samples or a technical assessment.”

The Evidence for Skills-Based Hiring

The case for skills-based hiring rests on two bodies of evidence: research on the predictive validity of different hiring methods, and data on credential inflation and the resulting talent pool restriction.

On predictive validity: The most comprehensive research on hiring validity (Schmidt and Hunter’s meta-analysis, updated through the 2000s) ranks different hiring methods by their correlation with job performance. Work samples rank highest (0.54 validity), followed by structured interviews (0.51), cognitive ability tests (0.51), and job knowledge tests (0.48). Educational credentials — specifically GPA and degree completion — rank much lower (0.34 and 0.10 respectively). This research directly supports the shift from credential-based to skills-based evaluation.

On credential inflation: The Harvard Business School “Dismissed by Degrees” research (Burning Glass Technologies, 2017) documented that employers added degree requirements to roles that previously did not require them, without evidence that degrees made candidates more qualified. This degree inflation increased recruiting costs, narrowed the talent pool, and excluded capable candidates. The Biden administration’s executive order removing degree requirements for federal jobs (2021) and state-level equivalent actions reflect a policy response to this documented pattern.

On outcomes: Companies including IBM, Apple, Google, Delta Air Lines, and PepsiCo have publicly reported removing degree requirements for many roles and report no decrease in performance quality among resulting hires. These are large-sample, real-world experiments, not controlled studies, but the pattern is consistent.

Where Skills-Based Hiring Works Best

Skills-based hiring is not equally applicable to all roles. The approach works best where:

The skills required are demonstrable. Software development, data analysis, writing, design, customer service, sales, project management, and most technical roles have skills that can be directly assessed. The assessment does not need to be complex — a work sample or a structured technical discussion is often sufficient.

The credential proxy is genuinely weak. A biology degree requirement for a laboratory researcher role has a plausible mechanism (the degree provides relevant knowledge). A business degree requirement for a sales development role does not — the skills needed (communication, persistence, curiosity, objection handling) are not primarily taught in business school.

The talent pool is constrained by credential requirements. If your recruiting pipeline is consistently thin or the candidates available with required credentials are more expensive than your budget supports, removing credential requirements and replacing them with skills assessment is the most direct intervention.

Where Skills-Based Hiring Is More Complicated

Licensed and regulated professions. Medical doctors, lawyers, licensed engineers, CPAs, and similar roles have credential requirements that are regulatory, not arbitrary — they reflect legal requirements for practice. Skills-based hiring does not apply to these roles in the same way.

Roles where the degree provides specific knowledge. An electrical engineer role that requires understanding of specific materials properties, circuit design, or regulatory standards may legitimately require a degree that provides that knowledge. The test is whether the knowledge is actually required, not whether the credential signals general competence.

Senior leadership roles where signaling matters externally. A Chief Legal Officer with no law degree or a CFO with no finance degree can face reduced credibility with investors, board members, or regulatory counterparties even if they are fully capable. The credential functions as a trust signal in external relationships, not just as an internal hiring filter.

How to Implement Skills-Based Hiring

Step 1: Audit Your Existing Job Requirements

Start with a content audit. For each open role (or a sample of common roles), identify every requirement and ask: “Is this a skill required to do the job, or is it a proxy credential?”

Common credential requirements that are often non-predictive:

“Bachelor’s degree required” for roles where the degree content is irrelevant
“Must have worked at a top-tier company” or “FAANG experience required”
Specific certification requirements where the certification does not directly test job-relevant skills
Vague experience requirements (“5-7 years of experience”) without specifying what experience needs to demonstrate

Replace removed credential requirements with specific skills or demonstrated abilities: “Ability to write clear, audience-appropriate technical documentation (assessed via writing sample)” instead of “Bachelor’s degree in English or Communications.”

Step 2: Design Skills Assessments for Common Roles

For each role family, design one or two practical assessments that directly test the core skills. This is the most time-intensive part of implementation.

Good skills assessment design:

Tests skills that are actually used in the role, not adjacent or similar skills
Is completed in 30-60 minutes for most roles (longer assessments increase candidate drop-off)
Is scored consistently against a defined rubric by trained evaluators
Compensates candidates for significant time investment (particularly for executive or senior roles)

Common assessment formats by role type:

Software engineering: Coding challenge, code review exercise, system design discussion
Writing/content roles: Writing prompt on a relevant topic (unpolished is fine; the skill is writing, not knowledge of your company)
Data/analytics: A small dataset analysis with interpretation, or a case study
Customer-facing roles: A role-play scenario, a written response to a simulated customer situation
Management roles: A case study discussion, or a structured scenario interview focused on specific situations

Step 3: Update Interview Scorecards and Training

Skills-based hiring requires interviewers to evaluate evidence of skills rather than proxy signals. Interviewers who have been trained to look for “top school, top company, clear trajectory” on resumes need to be retrained to look for specific behavioral evidence of the skills being assessed.

This is a behavioral change that requires explicit training, not just a policy memo.

Step 4: Track and Audit Outcomes

After implementing skills-based hiring for 12-18 months, audit the outcomes:

Is quality of hire (as measured by 12-month performance) equal to or higher than the credential-screened cohort?
Has the talent pool diversity (across demographic dimensions) increased?
Is the cost-per-hire different (positively or negatively)?

If quality of hire is lower for a specific role or skill assessment, investigate whether the assessment is measuring the right skills or needs revision.

Technology for Skills-Based Hiring

Several platforms support skills-based evaluation:

HackerRank and Codility are the most widely used technical assessment platforms for software engineering roles. Both provide coding challenges with automated scoring and enable recruiters to screen candidates at scale before live interviews.

Karat offers structured technical interviews conducted by trained technical interviewers, providing a consistent first-round technical screen without consuming engineering manager time.

Pymetrics uses neuroscience-based games to assess cognitive and behavioral traits, then matches candidates to roles based on trait profiles of successful incumbents. The approach is evidence-based but requires validation that the assessed traits are genuinely predictive for the specific role.

Vervoe and Workable Assessments are more general skills assessment platforms that support custom assessment creation for non-technical roles.

Greenhouse, Ashby, and Lever support work sample and assessment steps as stages in the ATS pipeline, allowing skills assessments to be integrated into the existing recruiting workflow.

Frequently Asked Questions

Does skills-based hiring mean ignoring experience entirely? No. Relevant experience is evidence of skills — it just should not be the only evidence, and the specific credentials attached to the experience (which company, which degree) should not substitute for evidence of capability. An interview structured around what a candidate has accomplished and how they did it is skills-based even if it explores past experience.

How do you prevent candidates from faking skills assessments? For written or portfolio-based assessments, proctoring is an option but adds friction. More practically, live technical discussions that probe the work submitted (explaining approaches, answering follow-up questions) quickly surface whether a candidate understands what they submitted. The goal is not to be foolproof — it is to be better than credential proxies, which are also easily gamed.

Is skills-based hiring better for diversity? The evidence suggests yes, with important caveats. Removing credential requirements removes a filter that disproportionately excluded candidates who could not afford degrees or who attended schools with less name recognition — which correlates with demographic characteristics. However, poorly designed skills assessments can introduce different biases. Assessments need to be validated as job-relevant and monitored for adverse impact.

Does removing degree requirements hurt employer brand? In the short term, some candidates interpret the absence of a degree requirement as a signal that the role is less prestigious. In practice, the shift at major employers (Apple, IBM, Google, Tesla) has not visibly damaged their employer brand. The signal that matters to candidates is whether the company recognizes genuine capability.

What is the biggest mistake in implementing skills-based hiring? Removing credential requirements without adding structured skills evaluation. This leaves hiring decisions even more subject to interviewer bias and gut feel than the credential-heavy process did — it just removes a flawed filter without replacing it with a better one. Skills-based hiring only works when credential removal is accompanied by credible skills assessment.

Skills-based hiring is a meaningful improvement over credential-based evaluation for a wide range of roles. The research supports it, leading employers practice it, and the talent pool benefits are real. The implementation requires work — specifically, designing good skills assessments and training interviewers to evaluate capability evidence rather than credential proxies. Organizations that do both consistently get better hires at lower cost from a larger candidate pool.

Related reading:

Structured Interview Process — The operational implementation of skills-based evaluation
Greenhouse ATS Review — ATS platforms that support skills-based workflows
What Is an ATS? — The technology layer that enables skills-based hiring at scale