Between 2017 and 2022, degree requirements were dropped from 46% of high-wage job postings in the United States, according to research by the Burning Glass Institute. IBM, Google, Apple, Delta Air Lines, Bank of America, and Accenture have all published explicit commitments to evaluating candidates on demonstrated ability rather than academic credentials. This is not a trend. It is a structural correction to a measurement problem that has accumulated for decades.
The measurement problem: credentials are poor proxies for job performance, but they are easy to filter on. Skills assessments are better proxies, but they require more design effort. Skills-based hiring is the discipline of doing the harder thing — and the data shows it produces better outcomes.
What Skills-Based Hiring Actually Means
Skills-based hiring is a structured approach to recruitment where the selection decision is based primarily on a candidate's demonstrated ability to perform the core tasks of the role, rather than on credential signals — degrees, certifications, previous employer prestige — that are used as proxies for ability.
In practice, it changes three parts of the hiring process:
| Process Stage | Credential-Based Approach | Skills-Based Approach |
|---|---|---|
| **Resume filter** | Filter on degree, university ranking, employer tier | Filter on evidence of relevant work: projects, contributions, measurable outcomes |
| **First screen** | Verify credentials verbally, ask about background | Structured assessment of core competencies required for the role |
| **Technical evaluation** | Trust claimed experience | Verify claimed experience through work-sample tests, live problems, or portfolio review |
| **Final decision** | Weigh credentials and interviewer impression | Weigh structured assessment scores, calibrated against a defined rubric |
Skills-based hiring does not mean ignoring credentials entirely. A CS degree from a selective university is a weak but real signal about a candidate's analytical capacity. What it means is that credentials do not substitute for direct evidence of ability — they are one input, not the verdict.
Why Credentials Are Poor Proxies for Job Performance
The correlation data is weak. A 2023 analysis by the Burning Glass Institute measured the correlation between educational credentials (degree, institution ranking) and 3-year performance ratings for software engineering roles. The correlation was 0.11 — statistically present but practically negligible. Degree-based filtering predicts about 1% of the variance in job performance.
Credential access is socioeconomically skewed. A bachelor's degree from a target institution reflects not just intellectual capacity but also access to preparation — elite high schools, test prep, parental education level, financial stability during college. Using credentials as a primary filter builds socioeconomic and demographic skew into your pipeline at the first stage, before a single competency has been measured.
The talent pool is artificially constrained. LinkedIn estimates that removing degree requirements from a typical software engineering role expands the qualified candidate pool by 1.4x. For roles with historically tight supply — data engineering, ML, cybersecurity — the expansion is larger. You are not lowering your bar when you drop degree requirements; you are widening your access to talent you were previously invisible to.
Credentials certify past achievement, not future capability. A degree certifies that a candidate completed a specific curriculum 4-10 years ago. A skills assessment verifies what they can do now, on a task that resembles the actual role.
Key insight: Dropping credential requirements does not make your hiring process weaker. It makes it more dependent on skills evidence — which requires better assessment design, not lower standards.
How to Implement Skills-Based Hiring
Implementation fails most often not because of philosophy problems, but because teams adopt the label without doing the structural work. These are the five steps that determine whether it works.
Step 1: Define the competency matrix before writing the job description. Identify the 5-7 competencies that actually predict success in the role. Derive these from your best performers, not from a generic job description template. This matrix drives every subsequent decision.
Step 2: Rewrite your job description around work outcomes, not credentials. Replace "Bachelor's degree in Computer Science required" with specific outcome expectations: "Can design a REST API for a multi-tenant system and explain trade-offs between normalization approaches." This also improves self-selection — candidates who know they have the skill apply more confidently; candidates who inflated their resume self-select out.
Step 3: Design assessments that test the competency matrix directly. Each competency on your matrix needs at least one assessment method. Use the structured framework in our technical skills assessment guide to map competencies to appropriate methods.
Step 4: Calibrate your rubrics before the first candidate. Define what a 1, 2, 3, and 4 looks like for each competency, with concrete examples. Have 2-3 current team members complete the assessment and use their scores to anchor the scale.
Step 5: Track outcomes and close the loop. Compare 90-day performance ratings to assessment scores by competency. Identify which assessments are most predictive. Improve or replace assessments that show weak correlation with performance.
Assessment Methods That Support Skills-Based Hiring
Different methods measure different parts of the competency matrix. A complete skills-based process typically combines at least two.
Work-sample tests are the gold standard. A candidate completes a task that mirrors actual job work — debugging a real codebase segment, designing a schema for a described use case, reviewing a pull request for problems. Predictive validity: 0.54 (Schmidt & Hunter, 1998).
Structured technical interviews probe reasoning depth through a series of predefined questions with scored rubrics. More predictive than unstructured conversations (0.48 vs 0.38 validity). Consistency depends entirely on rubric discipline. See live coding interview best practices for a structured session framework.
Portfolio evaluation works for roles where candidates have a body of shipped work to reference. It requires structured evaluation criteria to avoid becoming a subjective impression exercise. See our full guide on how to evaluate a developer portfolio.
AI-led interviews are increasingly used for first-round screening at scale. A real-time adaptive conversation generates questions based on the candidate's claimed experience and probes depth on each claimed skill. Provides consistent first-round evaluation without requiring engineer time.
Key insight: The method mix should follow the competency matrix, not the other way around. Start with what you need to measure, then choose the method that measures it most accurately.
Real Trade-Offs to Consider
Skills-based hiring is not a cost-free upgrade. Understanding the real trade-offs helps implementation teams address them proactively rather than discovering them mid-process.
Time investment upfront. Building a competency matrix, designing calibrated assessments, and aligning hiring managers on rubrics takes 10-20 hours of focused effort per role type. The payoff is faster, more accurate hiring at scale — but the front-loaded cost is real.
Candidate experience for senior roles. Senior engineers with multiple competing offers will not complete a 3-hour technical assessment, regardless of how well-designed it is. For senior roles, skills-based evaluation needs to be efficient — structured conversational interviews or a short task combined with a deep follow-up conversation, not an extended standalone project.
Consistency requires ongoing calibration. Rubric drift is real. Interviewers gradually reinterpret score levels. Schedule quarterly calibration sessions where 2-3 recent assessments are re-scored by multiple reviewers and compared to original scores.
Legal considerations. Skills assessments used in hiring must be validated as job-relevant. Using an assessment that disparately impacts a protected group without demonstrated business necessity creates legal exposure. This is not a reason to avoid skills-based hiring — it is a reason to document that your assessments are directly tied to role requirements.
How Nextmantra AI Approaches This
Nextmantra AI is built on the philosophy that skills and demonstrated ability matter more than credentials. The platform reads the job description, builds questions targeted at the specific competencies required for the role, and conducts a 45-minute real-time voice interview that probes each claimed skill to its actual depth. The output is a structured evaluation report scored against the role's competency matrix — the same rubric applied consistently to every candidate, regardless of degree, school, or previous employer. See how Nextmantra AI handles this
Frequently Asked Questions
What is skills-based hiring?
Skills-based hiring is a recruitment approach that prioritizes demonstrated ability over credentials like degrees, certifications, and employer prestige. Instead of using a candidate's educational background as a proxy for competency, skills-based hiring verifies what candidates can actually do through structured assessments, work samples, and portfolio reviews. IBM, Google, Apple, and Accenture are among the large employers that have removed degree requirements for most roles in favour of this approach.
Does skills-based hiring improve quality of hire?
Research supports it. Work-sample tests — the core of skills-based assessment — have a predictive validity of 0.54 for job performance, compared to 0.18 for resume screening and 0.11 for educational credentials in engineering roles. LinkedIn's 2023 Workplace Learning Report found that 73% of talent professionals report skills-based hires perform at or above the level of credential-based hires, while 89% show better retention at 2 years.
What are the challenges of skills-based hiring?
The main challenges are structural, not philosophical. Skills-based hiring requires well-designed assessments, calibrated rubrics, hiring manager buy-in, and outcome tracking. Teams that adopt the philosophy without fixing the process often find they have replaced one inconsistent signal with another.
How do you identify the skills needed for a role?
Start with the actual work the role requires. Talk to your best performers in that role and ask what they do in their first three months. Identify the 5-7 competencies that most reliably predict strong performance — not every skill mentioned in the job description. Then design your assessment to directly test those competencies, not peripheral knowledge.
Which companies use skills-based hiring?
IBM removed degree requirements for approximately 50% of its US job postings as early as 2017. Apple, Google, and Microsoft have removed degree requirements for many technical roles. The Burning Glass Institute estimates that degree requirements were dropped in 46% of high-wage job categories between 2017 and 2022.
How does skills-based hiring reduce bias?
Credential-based filtering systematically advantages candidates with access to elite education, which correlates strongly with socioeconomic background and demographics. Replacing credential proxies with structured skill assessments creates a more level playing field — but only if the assessments themselves are standardized and evaluated consistently. Structured rubrics with predefined score levels are essential.
What is the difference between skills-based hiring and competency-based hiring?
Skills-based hiring focuses specifically on verifiable technical or functional abilities. Competency-based hiring is broader, encompassing both skills and behavioural competencies like communication and leadership. A rigorous hiring process for most roles needs both: skills assessments to filter on technical ability, and structured behavioural questions to evaluate soft competencies.
Conclusion
Skills-based hiring is not an ideological position — it is a measurement improvement. Credentials are weak predictors of job performance. Structured skills assessments are stronger. The move from one to the other requires more upfront investment, but it produces better hires, broader talent access, and more defensible selection decisions. The practical challenge is not convincing teams that skills matter — it is doing the design work to assess those skills consistently.
Ready to implement skills-based first-round assessments at scale? [See Nextmantra AI in practice](https://nextmantra.ai/platform)
Sources: Burning Glass Institute (2023). Dismissed: The Impact of Education Requirements on Job Listings. LinkedIn Talent Solutions (2023). Workplace Learning Report. Schmidt, F.L. & Hunter, J.E. (1998). The validity and utility of selection methods. Psychological Bulletin. IBM Institute for Business Value (2022). Skills-Credentialing. SHRM Foundation (2022). Skills-Based Hiring.