Glossary
A plain-language definition from the Curriculo hiring glossary.
Skills-based hiring selects candidates on what they can do, shown through work samples, tests, and past results, instead of degrees or pedigree.
Why it matters
Many jobs list a degree or years of experience as a stand-in for skill. That screens out capable people who learned on the job, changed careers, or came from bootcamps. It also lets in people with the right credentials who can't do the work. Skills-based hiring widens your pool and tests for the thing you need.
How to put it into practice
- List the skills the role needs, such as SQL queries or writing clear release notes.
- Remove degree and years-of-experience rules that aren't true requirements.
- Screen resumes for evidence of those skills in use.
- Add a short work sample or practical exercise that mirrors real tasks.
- Score every candidate against the same rubric.
A short example
A company drops the four-year degree rule from its data analyst post. It adds a 45-minute exercise: clean a small dataset and answer three business questions. Two of the strongest results come from candidates who would have failed the old degree filter.
How it relates to outcome-based hiring
Skills-based hiring asks whether someone can do the work. Outcome-based hiring asks what results they've produced with those skills. The two fit together. Use outcomes to screen resumes, then test skills in the interview.
Common mistakes
- Dropping degree rules but keeping the same narrow sourcing channels.
- Take-home tests that take a full day and drive good people away.
- Listing dozens of skills instead of the few that matter.
- No shared scoring rubric, so each interviewer judges differently.
Learn about outcome-based hiring, read the founder's guide to outcome-based hiring, and use the interview question generator to build skill-focused questions.