Wait, what? A degree can be valuable evidence and still be the wrong first filter for a particular job.
For much of modern hiring, employers have used qualifications, job titles and years of experience as convenient signals. Those signals are easy to read. But they are imperfect. They can exclude people who can perform the work but reached capability through another route, and they can admit people whose credentials do not guarantee current job performance.
Quick answer
Skills-first hiring shifts the centre of recruitment from pedigree to demonstrated capability. Instead of asking mainly, “What qualification do you have?” or “Where have you worked before?”, it asks, “What must this role actually do, which capabilities does that require, and what evidence would show that a candidate can perform them?” Credentials can still matter. Experience can still matter. The change is that they become evidence inside a broader decision rather than automatic substitutes for the decision.
This is now an active international labour-market agenda. In June 2026, the OECD launched A Skills-First Labour Market, describing skills-first approaches to hiring, talent management and development as increasingly important as labour markets change. OECD work on skills-first hiring and talent management discusses structured assessments, competency-based interviews and other methods for selecting on demonstrated skills.
The problem with proxies
Hiring is a prediction problem. An employer is trying to estimate how a person will perform in future work using evidence available now.
Qualifications, previous employers and job titles are proxies. They can carry useful information. A professional licence may be legally required. A rigorous technical qualification may indicate important knowledge. Years in a field can expose someone to difficult cases. But a proxy is not the same thing as the capability it is meant to represent.
Skills-first hiring becomes useful when it asks whether the proxy is doing too much work. Is the degree requirement genuinely connected to the task, or is it inherited from an old template? Does five years of experience mean five years of increasing capability, or one year repeated five times? Does a prestigious job title reveal what the person actually did?
Start with the work, not the candidate
A weak skills-first process begins by replacing degree filters with a long list of fashionable skills. A strong process begins with the work itself.
Break the role into outcomes and tasks:
- What must this person produce?
- What decisions must they make?
- What mistakes are costly?
- What information must they interpret?
- What relationships must they manage?
- What tools can change without changing the real job?
- Which capabilities must already exist on day one?
- Which can reasonably be learned after hiring?
Only then should the organisation decide what evidence to request.
Skills are not keywords
“Communication”, “leadership”, “analysis” and “problem solving” are not yet useful hiring criteria. They are category labels. To assess them, the employer needs observable performance.
For example, “analysis” might mean:
- identify the real question behind a messy request;
- distinguish reliable evidence from noise;
- compare plausible explanations;
- calculate or model relevant quantities;
- state uncertainty honestly;
- recommend an action that follows from the evidence.
Once the capability is expressed at this level, assessment becomes more defensible.
Evidence can come from several routes
Skills-first does not require one universal test. Different jobs justify different evidence. Useful evidence may include:
- structured work samples;
- job simulations;
- portfolio evidence;
- competency-based interviews;
- technical tests;
- apprenticeship or prior-learning records;
- microcredentials where they have meaningful assessment behind them;
- reference evidence tied to specific work;
- formal qualifications when they directly represent required knowledge or regulated competence.
The key is evidence fit. A presentation skill should not be inferred only from a multiple-choice test. A safety-critical technical competence should not be inferred only from a polished portfolio. The assessment should resemble the capability being claimed closely enough to be informative.
A work sample is not automatically fair
Skills-first hiring can sound more objective than credential-based hiring, but badly designed assessments can create new problems. A task may reward insider familiarity rather than the intended skill. An unpaid assignment may demand too much time. A simulation may disadvantage candidates who are unfamiliar with a particular interface even though the interface can be learned quickly. Automated screening may reproduce bias hidden in historical data.
The OECD’s 2026 discussion of skills-first hiring explicitly notes that algorithmic tools may help with some forms of screening while also creating risks of reproducing or amplifying bias depending on how they are designed and used. Skills-first therefore does not mean “use more tests”. It means use better evidence with clearer boundaries.
The assessment must preserve the target
Every hiring assessment needs a target capability. Then it needs discipline not to drift away from that target.
Suppose a role requires data interpretation. A take-home exercise also requires advanced visual design, specialised software and several unpaid hours. The employer may think it is measuring analysis while accidentally measuring spare time, tool familiarity and presentation polish.
A useful rule is: remove difficulty that is not part of the job signal you actually need.
Skills-first hiring changes who gets seen
One attraction of skills-first practice is that it can widen the search space. People may build relevant capability through vocational education, military service, caregiving, freelance work, self-directed learning, community leadership, apprenticeships, career transitions or adjacent occupations. A degree-first or title-first screen can miss them before they get a chance to demonstrate what they can do.
That does not mean every unconventional background should be treated as equivalent. It means the process should have a way to inspect capability directly rather than assume that only one route can produce it.
Credentials still matter where they carry real information
A skills-first approach is sometimes caricatured as “degrees do not matter”. That is too simple.
Credentials can serve several legitimate functions. They may represent structured knowledge, regulated practice, supervised training, professional ethics, sustained effort or a common baseline. In medicine, engineering, law and other regulated fields, certain qualifications may be necessary for public safety and legal authority.
The real question is whether the credential is proportionate to the role and whether it remains the best available evidence. Skills-first hiring is strongest when it removes unnecessary credential inflation without discarding meaningful standards.
Experience is evidence, not a unit of skill
Years of experience are similarly useful but incomplete. Time creates opportunity to learn, but time itself does not prove what was learned.
Two candidates with the same number of years may have faced radically different complexity. One may have repeated a stable routine. Another may have handled increasingly difficult cases, built new systems, taught others and recovered from failure.
A skills-first interview therefore asks for evidence of capability development rather than treating duration as the capability.
What good competency-based questions do
A useful competency-based question is not “Tell me about a time you showed leadership” because that can still reward storytelling skill more than the target capability. Stronger questions make the evidence inspectable:
- What was the situation?
- What information did you have at the time?
- What alternatives did you consider?
- What did you decide?
- What trade-off did you accept?
- What happened next?
- What would you change now?
This moves the interview from impression towards reasoning and evidence.
Do not confuse proof of capability with the hiring system
eduKateSG already owns the learning-side question in How Studying Works | Proof of Capability: how learning becomes evidence the world can trust. This article owns a different job: how employers design a selection process around demonstrated skills once that evidence reaches the labour market.
Likewise, Capability Legibility explores how capability becomes recognisable. Skills-first hiring concerns the institutional decision that follows: what evidence gets admitted, compared and trusted when a role is filled.
The AI screening problem
AI can help organisations process large candidate pools, extract skills from résumés, match profiles to roles and administer assessments. But scale increases the importance of governance.
If a system rejects candidates automatically, the employer should understand what the system is optimising, which data it uses, how errors are detected, what recourse exists and whether protected or unconventional career paths are disadvantaged. A skills-first system that quietly replaces degree bias with opaque model bias has not solved the underlying problem.
This is where skills-first hiring connects outward to eduKateSG’s How Human Oversight Works and How Technology Is Governed. Hiring evidence and hiring authority should remain traceable.
A practical skills-first hiring sequence
- Define the job outcome. What must be reliably achieved?
- Decompose the work. Which tasks and decisions create that outcome?
- Name the capabilities. Avoid vague labels where possible.
- Separate must-have from trainable. Do not over-specify the entry gate.
- Choose evidence. Match the assessment to the real capability.
- Reduce irrelevant difficulty. Do not test what the job does not require.
- Structure comparison. Use consistent criteria across candidates.
- Inspect adverse patterns. Ask who is being excluded and why.
- Keep recourse and human judgement where stakes require it.
- Validate after hiring. Did the selection evidence predict useful performance?
Validation closes the loop
Hiring methods should not become permanent merely because they feel modern. Organisations need return evidence.
If a work sample is meant to predict performance, compare assessment results with later job outcomes. If a competency interview is supposed to identify strong judgement, examine whether it actually does. If removing a degree requirement widens the applicant pool, check whether quality, retention and progression change.
This turns skills-first hiring from an ideology into an empirical system.
The deeper rule
Hiring is strongest when the evidence is closer to the work than the proxy is.
Sometimes a qualification is close to the work. Sometimes experience is highly informative. Sometimes a structured simulation tells you more. The skills-first principle is not to prefer one evidence type blindly. It is to ask what the job requires and then demand evidence that deserves to carry the decision.
The candidate should not have to look like the last person who succeeded. They should have to show that they can do the work—or can realistically become capable of doing it.