Reading a job description like a recruiter does
Job descriptions aren't aspirational lists. They're sift criteria in disguise.
By the time a JD is published, every line in it has been through a hiring panel, a HR review, and a sign-off from a budget holder. Each word is doing work. The trick is reading it the way the recruiter who wrote it intended it to be read.
Here's the method.
The four sections worth reading carefully
Most JDs have the same four-section shape: role overview, main duties, person specification (or essential / desirable criteria), and a closing block about the team or department.
Only two of these are scoring sections. The other two are framing.
The role overview sets the tone and scope. Read it once to understand what the role is and how it sits in the team, then move on. Sift assessors don't score against it.
The closing block is about culture and selling the role to candidates. Useful for interview prep, irrelevant for the application.
The two sections that get scored against are the main duties and the person specification. The person spec especially. Most assessors are scoring directly against bulleted criteria in the person spec, often using a structured rubric.
This means: when you're writing your application, you're writing against the person specification. Not the role overview. Not the closing block.
The signal in the verbs
Every duty and criterion in a JD starts with a verb. The verb tells you what's actually being expected.
- "Manage", "lead", "own", "drive", "deliver" → primary responsibility. You're the named person accountable.
- "Support", "contribute to", "work with", "assist" → secondary responsibility. You're helping someone else deliver.
- "Develop", "build", "design", "create" → original work expected. You're producing something new.
- "Maintain", "ensure", "operate", "follow" → execution against an existing standard. You're keeping things running.
The verbs cluster by grade. Junior roles use more "support" and "contribute to". Senior roles use more "lead" and "own". When a JD mixes them — "lead the design of X while supporting the team in Y" — it's telling you about the priority order.
When you draft your application, match the verb level. Don't claim "I led" against a duty that says "contribute to" — it reads as inflation. Don't write "I supported" against a duty that says "lead" — it reads as undersold.
The "essential" vs "desirable" split
The person specification almost always splits into two columns or two lists: essential and desirable.
These are not equal weights. Essential criteria are gating — fail to evidence one, and you're often rejected at sift. Desirable criteria differentiate — they're used to rank candidates who all meet the essentials.
The implication for your statement: cover every essential criterion fully, even if briefly. Cover the desirable criteria where you have strong evidence, skip them where you don't. Many candidates spread their words evenly across all criteria and end up with weak coverage of the essentials, which gets them rejected on a technicality.
The repeated phrases
Most JDs repeat key phrases across the role overview, duties, and person spec. Sometimes the same phrase appears five times across the document. This repetition is signal.
Repeated phrases are the criteria the panel cares most about. They might also be the keywords the role's ATS is scoring against, if the role is filtered electronically. Either way, they're the words you want to mirror in your application — not paraphrased, the same words.
Pick out the repeated noun phrases ("stakeholder engagement", "service redesign", "complex casework", "regulatory compliance") and use the exact phrasing back to the panel. It feels repetitive. It scores.
The phrases that mean something different than they look
A few JD phrases mean something specific that isn't always obvious to candidates outside the sector.
"Self-starter" / "able to work autonomously" usually signals a role with limited supervision. The team is busy, the manager is stretched, you'll be expected to make decisions without checking. Strong evidence for this looks like: making calls without waiting for sign-off, designing your own approach to a problem, escalating only when needed.
"Working in a fast-paced environment" usually means competing priorities, frequent reprioritisation, and tight deadlines. Strong evidence: examples where you delivered against shifting priorities, dropped lower-value work, or worked across multiple parallel streams.
"Strong communication skills" is the most overused phrase in the sector. It almost always means something specific in context — usually written communication (drafting papers, briefings, ministerial submissions) for Civil Service, or stakeholder management for private sector. Read the surrounding duties to figure out which it is, then evidence that specific kind.
"Demonstrable experience of..." is recruiter-speak for "we need concrete examples, not just CV bullets". When you see this phrase, the panel is expecting evidence in the supporting statement, not just inference from your work history.
The grade signals
You can usually tell what grade a role is from the JD even before checking the salary band:
- Operational language, focus on individual delivery, "experience of" criteria → junior (EO/HEO equivalent)
- Project leadership language, "responsibility for", expectation of managing others → middle grade (SEO/Grade 7)
- Strategic language, "leading change", "influencing across the organisation", "developing policy" → senior (Grade 6/SCS)
This matters because it tells you what scale of evidence you should be bringing. A senior role wants examples of leading change across functions, not examples of running a team well. If your strongest examples are operational and the role is strategic, the application is fighting uphill.
The fifteen-minute first read
The first time you read a JD, give it 15 minutes. Read it once through to understand the role. Then read it again with a highlighter — physical or digital — and mark:
- Every essential criterion
- Every repeated noun phrase
- Every "demonstrable experience of..." line
- Every grade signal
What you end up with is a structured map of what the panel will be scoring against. Your application is then a response to that map, not a freeform narrative about your career.
This is what recruiters do when they read JDs. It's also what assessors do when they read your application. Reading the JD this way puts you on the same wavelength as the people who'll be marking you.