You are staring at a job advert that asks for a marketing manager with five years' FMCG experience, a professional qualification you've never heard of, and "demonstrable expertise" across three different platforms. You've done two of the three, maybe two and a half if you're generous with yourself. Do you apply anyway, or close the tab and keep scrolling?
For most of the last decade, the sensible answer was: don't waste your time. Job specs functioned as gatekeeping documents, and recruiters used them literally — miss one line item and an applicant tracking system might discard your application before a human ever opened it. That's changed faster than most job seekers realise. Large employers including IBM, Accenture and Bank of America have publicly stripped degree requirements from thousands of roles over the past few years, replacing them with lists of skills a candidate needs to demonstrate rather than credentials they need to hold. LinkedIn and Indeed have both reported a steady rise in UK postings that describe required capabilities instead of demanding a specific degree or a fixed number of years in an identical job title. The Chartered Institute of Personnel and Development (CIPD) has tracked the same shift among its member organisations, particularly in technology, financial services and the public sector.
Why the job spec is losing its grip
The honest reason has less to do with fairness and more to do with arithmetic. Employers who insist on a specific degree plus five years in an identical role are fishing in a much smaller pond, and in sectors with genuine skills shortages — data analysis, cybersecurity, project management — that pond has been fished dry. Widening the criteria to "can you actually do this job" rather than "have you done this exact job before, with this exact title, at a company we've heard of" opens the applicant pool considerably. It also, not incidentally, tends to surface candidates who are cheaper to hire than the ones with the matching pedigree, which is a detail employers rarely say out loud but recruiters will admit to over a coffee.
None of this means the job spec has become decorative. It means the spec is now doing a different job: instead of a checklist to be matched line for line, treat it as a description of a problem the employer needs solved. Read it that way and a line like "experience managing stakeholder relationships across departments" stops being something only project managers can claim — it's something an events coordinator, a senior teacher, or a charity fundraiser has probably done just as often, under a different job title.
What "skills-based" actually asks you to prove
Skills-based hiring shifts the burden of proof from your CV's header — job titles, employer names, degree classification — to its body: what you actually did, and what you can show for it. In practice, this shows up in three ways during recruitment:
- Application forms that ask for evidence against named competencies rather than a free-text "tell us about yourself" box.
- Skills tests or short work samples replacing, or sitting alongside, the traditional CV screen — a short written exercise, a spreadsheet task, a fifteen-minute case study.
- Structured interviews built around specific scenarios, such as "tell me about a time you had to persuade a colleague who disagreed with you," rather than open chat about your career history, and this format rewards candidates who prepare concrete examples in advance far more than it rewards a polished LinkedIn profile.
That last point matters more than it looks. A candidate who has never held a "leadership" job title but can describe, in specific detail, the week she talked a supplier down from a 12% price increase to 4% by walking them through the account's five-year order history, will usually beat a candidate whose CV says "Team Leader" but who goes vague under questioning. Skills-based hiring rewards specificity over seniority, and that is very good news if your career so far has been non-linear.
Rebuilding your CV around evidence
Start by deleting the responsibilities-based bullet point — "responsible for managing a team of six" — and replacing it with an outcome-based one: "cut onboarding time for new starters from six weeks to nine days by rewriting the induction handbook." The second version proves a skill (process improvement, documentation, stakeholder buy-in) without needing a job title to back it up. Do this for every line on your CV before you apply for anything, not just the roles where you're missing a requirement.
Where a job spec lists a skill you've genuinely never used in paid work, don't pretend otherwise, but don't skip the line either. A short "transferable skills" section, placed after your work history rather than instead of it, lets you say directly: "Not used Salesforce professionally, but administered a comparable CRM (HubSpot) for eighteen months, including building automated reporting dashboards." Recruiters running skills-based processes are specifically trained to look for this kind of honest mapping, because the whole point of the approach is catching capable people whose CVs would otherwise get auto-rejected by keyword matching.
The cover letter that does the translating
Most cover letters restate the CV in paragraph form, which wastes the one part of the application where you control the framing. In a skills-based process, use the cover letter to do the translation work the recruiter would otherwise have to do themselves — explicitly connect a skill you've used in one context to the context they're hiring for.
Naming skills you've never had a job title for
Nobody's CV says "conflict resolution" as a job title, yet almost everyone who has managed a rota, chaired a residents' committee, or coached a five-a-side team has practised it under real pressure. Name the skill explicitly, then give one sentence of proof, then move on — three sentences per skill, maximum. Cover letters that run past one page for a job spec this specific are, without exception, cover letters nobody finishes reading.
Talking about it at interview
Skills-based interviews are usually built around the STAR structure — Situation, Task, Action, Result — and interviewers trained in this method will interrupt a rambling answer to ask "and what did you specifically do?" That's not rudeness; it's the method working as intended, and it catches people out far more than a straightforward "tell me about yourself" ever did. Prepare four or five stories in advance, each mapped to a different competency — influencing without authority, working under time pressure, handling a mistake, learning something fast — and you'll be able to answer almost any behavioural question by picking the closest-fitting story rather than improvising on the spot. Write each one down beforehand as three bullet points — situation, what you did, what changed — because the candidates who stumble in these interviews are almost never short on relevant experience; they're short on a rehearsed way of describing it under pressure. A story you've told out loud at least once, even just to a mirror or a patient friend, comes out fluently. One you're recalling cold, mid-interview, tends to wander into irrelevant detail and lose the interviewer halfway through.
Where you genuinely lack a skill on the spec, say so plainly and pivot immediately to the closest thing you've done and what you learned from the gap. "I haven't run a budget of this size before — the largest I've managed directly was £40,000 for a departmental event programme, and I closed that year 8% under budget by renegotiating two supplier contracts mid-year" answers the question honestly while still proving competence. Vague reassurance — "I'm a fast learner and I'm sure I'd pick it up" — answers nothing, and experienced interviewers hear it as a dodge every time.
Where skills-based hiring still lets you down
It would be dishonest to present this as a fixed system.
Skills-based hiring works best at large, well-resourced employers who can afford to design proper skills assessments — smaller companies and recruitment agencies often still default to CV keyword-matching because it's faster and cheaper, whatever their careers page says about valuing potential over pedigree. And under the Equality Act 2010, skills tests themselves have to be applied consistently and can't disadvantage candidates on protected characteristics, which means some employers over-engineer their assessment process out of legal caution rather than genuine interest in fairness — the result, from a candidate's side, can be three separate skills tests for a role that used to require one CV and one interview.
The gap between what a company's recruitment marketing promises and what its applicant tracking system actually does can be wide. Apply the CV rewrite regardless, because a keyword-matched screen still reads outcome-based bullet points more favourably than vague responsibility statements — but don't assume every "skills-based" badge on a job advert means the process behind it has actually changed.
A few mistakes worth avoiding
- Applying for a role where you meet none of the core requirements, on the theory that skills-based hiring means requirements no longer matter. They still matter — the shift is in how you prove them, not whether you need them.
- Listing skills without evidence. "Strong communicator" on its own is filler; the same claim backed by one sentence of proof is a fact a recruiter can act on.
- Treating the skills-test stage as a formality, then losing the role at exactly the stage designed to reward preparation, because a strong CV screen was followed by a rushed, careless work sample.
- Forgetting to update your LinkedIn profile to match your rewritten CV — recruiters cross-check both, and a mismatch between "Team Leader" on LinkedIn and a detailed, outcomes-based CV reads as inconsistency rather than nuance.
None of this guarantees an offer. What it does is put you back in the pool of candidates a hiring manager actually reads properly, instead of the pile an applicant tracking system quietly filters out before anyone gets that far — and for a lot of people whose careers don't map neatly onto a job title, that's the difference that matters.