A skills-first job description does not mean lowering the hiring bar. It means replacing proxies — such as a degree, school name, previous job title or an arbitrary number of years of experience — with criteria that explain what a person needs to be able to do and how that ability will be verified. The shift is most useful when the job post, screening and interview all follow the same logic.
What changes in a skills-first job description
The OECD defines a skills-first approach as prioritising demonstrated skills, regardless of where or how they were acquired, rather than relying mainly on credentials and previous titles. The aim is not to treat education as irrelevant, but to prevent it from becoming a shortcut when the employer could specify the required capability more precisely. The 2025 report Empowering the Workforce in the Context of a Skills-First Approach also highlights a central challenge: skills need to be communicated and validated in a trustworthy way.
LinkedIn data shows this logic expanding in practice. In 2025, the platform reported that, across OECD countries, 14% of recruiter searches were filtered by skills, compared with less than 2% filtered by degree. The same study found an association between greater use of skills-based searches and a 12% higher likelihood of making a “quality hire” under LinkedIn’s own composite metric. This is correlation in platform data, not proof of causality, but it shows that skills-first thinking is moving from rhetoric into recruiting operations. See the methodology in LinkedIn’s report.
Start with the work, not the profile of the person who held the role before
A common mistake is to open a vacancy by copying the previous description and preserving historical requirements without asking why they exist. Instead, bring HR and the hiring manager together to break the role into real outputs. Four questions help:
- What outcomes must this person deliver? Describe observable deliverables, decisions, problems and responsibilities.
- Which skills are essential on day one? Separate what cannot wait from what can be taught during onboarding.
- What evidence would show that the skill exists? It could be a portfolio, work sample, solved case, simulation, relevant certification or structured behavioural example.
- Does the current requirement measure the skill, or is it only a proxy? If “bachelor’s degree” or “five years of experience” has no clear connection to the work, rewrite it.
LinkedIn itself recommends that skills-based job descriptions focus on responsibilities and competencies, distinguishing what a person needs to bring from what can be learned on the job. That guidance appears in How to Get Started with Skills-Based Hiring.
Build a skill → evidence matrix before writing the post
A simple matrix forces the team to justify each requirement. It also creates the bridge between the job description and the selection process.
| Skill | Why it matters | Acceptable evidence | How to assess it | Can it be learned later? |
|---|---|---|---|---|
| Data analysis | Turn indicators into decisions | Project, portfolio, case or documented result | Data exercise with defined criteria | Partly |
| Customer communication | Explain decisions and handle difficult situations | Examples from service, sales, support or projects | Structured interview + simulation | Partly |
| Professional writing | Produce clear, actionable messages | Writing sample or work document | Short role-related writing task | Yes, if the starting level is sufficient |
| Priority management | Work with competing demands | Example of planning and decision-making | Behavioural question with a rubric | Partly |
| Use of a specific tool | Perform critical tasks in the team’s system | Hands-on experience, course, certification or equivalent tool | Practical task or demonstration | Often, yes |
The point is not to demand “proof” for everything. It is to ensure that every mandatory item has an operational reason and a proportionate way to verify it.
How to rewrite degree and years-of-experience requirements
Replacing credentials with skills works best when the new wording describes capability, context and evidence. For example:
| Before | After, in skills-first logic |
|---|---|
| “Bachelor’s degree in Business, Economics or a related field.” | “Ability to interpret metrics, organise priorities and document decisions. We accept evidence from work, projects, academic education, courses or other pathways.” |
| “Minimum 5 years of project management experience.” | “Demonstrated experience leading projects from planning through delivery, including scope, deadlines, risks and stakeholder management. Be prepared to discuss two concrete examples.” |
| “Previous experience in our industry is required.” | “Ability to learn business rules quickly and make decisions in constrained environments. Industry experience is useful, but adjacent backgrounds will be considered.” |
| “Advanced Excel required.” | “Ability to clean data, combine sources, build formulas and create auditable spreadsheet analyses. The tool may be Excel or an equivalent; there will be a practical exercise.” |
| “Certification X required.” | “Certification X is required only when mandated by law, regulation, contract or role risk. Otherwise, describe the competency the certification is meant to prove and accept equivalent evidence.” |
This type of wording also helps candidates assess themselves. In 2023, LinkedIn found an 11% association between listing skills in the requirements section and a higher view-to-apply rate. The finding is observational, but it is consistent with making entry criteria easier to understand. The analysis is in Job Posts That Feature Skills Attract More Applicants.
When a degree, licence or time requirement can still make sense
Skills-first does not mean “credentials never matter.” There are situations where the credential is part of the real requirement:
- legal, regulatory or safety requirements: licensed professions, regulated activities or contracts that impose a specific qualification;
- formal technical knowledge that is difficult to substitute: when education is the most direct and defensible way to demonstrate an indispensable body of knowledge;
- client or external-certification requirements: when the obligation is real and documented;
- exposure to a specific level of complexity: if the team uses seniority as a signal of maturity, describe the complexity of the expected decisions instead of assuming a number of years guarantees it.
When in doubt, use a simple test: “If someone demonstrates the skill through another route, would they still be unable or legally barred from doing the work?” If the answer is no, the requirement deserves review.
Connect the job description to the selection process
A company can remove the degree from the job post and still choose candidates using the same old pattern. Research from Harvard Business School and the Burning Glass Institute illustrates that risk: among employers that removed degree requirements, the aggregate effect on hiring people without degrees was small; an HBS summary estimated that fewer than 1 in 700 new hires benefited from those reforms. The practical conclusion is not that skills-first “does not work,” but that changing job-ad language without changing screening, assessment and decision-making has limited reach. See Harvard Research: Fewer than 1 in 700 get hired without a college degree.
For that reason, every essential skill in the job post should appear in at least one assessment instrument:
- screening based on evidence and achievements, not only job titles;
- structured questions asked to every candidate for the same competency;
- short work samples proportionate to the role;
- rubrics with performance levels defined before interviews;
- a documented reason for the decision, reducing the drift back to implicit criteria.
Avoid long tests, unpaid production work or assessments that measure something different from the job. The principle is to verify the skill with the lowest reasonable burden.
A ready-to-use job description structure
- Role purpose: why the role exists and what problem it solves.
- Outcomes and responsibilities: what the person will do, in concrete language.
- Essential skills: a small number of specific, job-related capabilities.
- Learnable skills: what the company is willing to teach after hiring.
- Accepted evidence: professional experience, projects, portfolio, education, certifications, volunteering or other relevant pathways.
- Preferred criteria: items that are genuinely useful but not elimination factors.
- How selection will work: stages, assessment types and what will be observed.
Separating “essential” from “preferred” prevents a wish list from becoming an automatic filter. It also improves the conversation between HR and the hiring manager: every item placed under “essential” should survive the question, “What happens if the person does not have this on day one?”
Checklist: is the job truly skills-first?
- Does the post describe outcomes and responsibilities before credentials?
- Does every mandatory requirement correspond to a necessary skill?
- Were degree and experience requirements kept only when there is a clear justification?
- Does the wording accept different learning and experience pathways?
- Are essential skills few enough to be assessed properly?
- Is there at least one acceptable form of evidence for each critical skill?
- Does the selection process measure the same competencies advertised?
- Do interviewers use common criteria and rubrics?
- Are “preferred” items prevented from becoming hidden elimination criteria?
The standard becomes more demanding — and more explicit
A good skills-first job description does not promise that every background fits every role. It makes the requirement more defensible: instead of “we want someone with this history,” it says “we need someone who can do this, in this context, and we will accept these ways of demonstrating capability.” That is the central gain for recruiting and selection: less dependence on indirect signals and more consistency between the work, the requirement and the evidence.
