How to Read a Job Description Like a Recruiter

A job description is not a specification. It looks like one. It has bullet points, requirements, qualifications, and a list of responsibilities that reads like a contract. Candidates treat it as a checklist: if I meet eight out of ten requirements, I should apply. If I only meet six, I should not.

That is not how hiring works on the other side of the table.

A job description is a negotiation between the hiring manager, who wants the perfect candidate, HR, who wants to standardise the process, and the recruiter, who knows that the perfect candidate does not exist and the job description needs to be flexible enough to attract the three or four people who could actually do the job well.

The result is a document that is part requirements, part aspirations, and part boilerplate. The skill is knowing which part is which.

The three layers of a job description

Every job description has three layers, and they are almost never labelled.

Layer 1: The non-negotiables. These are the requirements the hiring manager will not bend on. They are typically structural: a specific qualification (ACA/ACCA for a finance role, SRA authorisation for a legal role), a minimum number of years at a specific level, or a particular type of experience that is genuinely essential for the role. There are usually two or three true non-negotiables per job description, rarely more.

Layer 2: The strong preferences. These are the requirements the hiring manager would strongly prefer but will flex on for the right candidate. Sector experience often sits here. "Must have financial services experience" frequently translates to "we would prefer financial services experience, but if someone from a PE-backed industrial business can demonstrate the same complexity of stakeholder management, we would consider them."

Layer 3: The wish list. These are the requirements that appeared because the hiring manager described their ideal candidate during the intake meeting, and the HR team or recruitment partner wrote them down as requirements. "Experience with Workday" when the business is considering but has not yet committed to Workday. "International experience" when the role is domestic but the hiring manager thinks it would be nice. "MBA preferred" when no one on the current team has an MBA and the business has no track record of prioritising one.

How to tell which layer you are reading

Recruiters develop an instinct for this, but there are signals anyone can read.

Language signals. "Essential" and "must have" are not always non-negotiable, but they are more likely to be layer 1 or 2. "Preferred," "desirable," and "ideally" are almost always layer 3. The most honest job descriptions separate these explicitly. The least honest present everything as essential, which paradoxically makes the whole list less useful.

Qualification requirements. If the role requires a specific professional qualification (ACA, CIMA, ACCA, CFA, SRA), that is almost always a genuine non-negotiable, because the qualification is either a legal requirement or a deep signal of domain competence. If the role says "degree-educated," that is increasingly layer 3 at senior levels. If it says "MBA preferred," that is nearly always layer 3.

Experience duration. "10+ years of experience in X" is almost always soft. No hiring manager has ever rejected a candidate with eight years of excellent experience because the job description said ten. What the hiring manager actually means is "I want someone who operates at a senior level in this domain." The years are a proxy, not a threshold.

Sector requirements. "Must have experience in [sector]" is one of the most frequently flexed requirements in hiring. The hiring manager writes it because they want someone who can hit the ground running. The recruiter knows that a candidate from an adjacent sector with the right functional skills and a strong learning curve is often a better hire than a sector insider who brings yesterday's thinking.

Technology requirements. "Experience with [specific software]" is usually layer 3 unless the role is a technical specialist. A CFO who has used Oracle can learn SAP. A Head of Marketing who has used HubSpot can learn Salesforce. These are tools, not capabilities.

The hidden signals

Beyond the requirements, a job description contains signals that tell you more about the role than the bullet points do.

Reporting line. Who does this role report to? If a Head of Finance reports to the CEO, the role has strategic scope. If the same title reports to a Group CFO, it is an execution role. The reporting line tells you more about the seniority and influence of the position than the title does.

Team structure. "Managing a team of X" tells you about current scope. "Building a team" tells you this is a new function or a significant expansion. Building is harder and more interesting than inheriting. If the description mentions both, read carefully: "managing an existing team while building out additional capability" often means "the current team is not right and you will need to restructure it," which is a different job from either managing or building.

Why the role exists. This is the most important signal and the one most candidates overlook. Is this a replacement or a new hire? If replacement, why did the previous person leave? If new hire, what triggered the decision to create the role? The answers to these questions tell you more about what the hiring manager actually needs than any bullet point on the job description.

You can often infer the answer. A company that just received PE investment and is hiring a CFO for the first time is creating a new function. A company that has had three Heads of Marketing in two years has a problem that the job description will not mention. The context behind the role is the context that determines whether you want the job.

How this changes your approach

Once you can read a job description as a recruiter reads it, two things change.

You apply more strategically. Instead of matching yourself against ten bullet points and deciding you need eight to apply, you identify the two or three non-negotiables and assess yourself against those. If you meet the genuine non-negotiables and can make a compelling case for the strong preferences, you are a viable candidate, regardless of how many wish-list items you miss.

You position your CV more effectively. When you know which requirements are non-negotiable, you know what your CV needs to lead with. If the non-negotiable is PE-backed experience at a specific scale, your professional summary should signal that immediately. If the non-negotiable is a specific qualification, make sure it is visible in the first scan of the page. Do not bury your strongest qualification-to-requirement match in the third bullet of your fourth role.

This is the connection between reading the job description and writing the CV. The CV is not a fixed document that you send to every role. It is a positioning document that should be tailored, at least in its emphasis and framing, to the specific requirements that matter most for the specific role you are targeting.

I wrote about why this positioning matters in why you are not getting interviews. The candidates who understand what the job description is actually asking for, as distinct from what it literally says, are the ones whose CVs land.

Positioning your CV against the role

Reading the job description like a recruiter is step one. Step two is making sure your CV responds to what you have read.

The CV Intelligence Report does both. I assess your CV against the types of roles you are targeting, identifying where your positioning matches the non-negotiables, where it falls short on the strong preferences, and how to reframe your experience so that the hiring manager can see the fit without having to work for it.

Two tailored CVs. A LinkedIn assessment. And the reasoning behind every change, so you can apply the same thinking to every job description you read from here.

Because once you can see the three layers, you cannot unsee them. And once your CV is built to address the layer that matters, the wish list stops being a barrier and starts being what it always was: background noise.