The Job Description Trap
The Job Description Trap (and Why Reading It Too Logically Costs You the Role)
Most hiring managers cannot articulate exactly what they want, but they know it when they see it. That short sentence is doing more work in your job search than you might realise.
Strong candidates – VPs, senior directors, people with track records that make sense on paper – read job descriptions carefully, mirror every requirement back in their CV, and assume that is the brief. It is not. It is a defensible-on-paper artefact built by committee, and the real target lives somewhere else.
Reading the JD too literally means responding to the wrong brief. That gap is structural, and it starts before the role even goes live.
Job Descriptions Force Hiring Managers to Solve Two Problems at Once
A good job description requires the hiring manager to do something genuinely hard: define the problem and define the solution at the same time, on a single piece of paper.
The problem half is the part the business needs solved. What is going wrong in this team, this department, this function? What capability is missing? What is the gap that is costing money or slowing growth?
The solution half is the candidate. Years of experience. Specific skills. Industry background. Tools and technologies. Languages. Education. Reporting line.
If hiring managers could actually write both halves cleanly, every time, we would have solved sales. We would have solved business development. We would have solved most of strategy. Defining the problem and the solution in one shot is the work itself – it is what executives are paid for. Asking them to do it on a Word document with HR breathing down their neck is unreasonable.
So they do not. They cannot.
Most JDs Are Pulled Off SharePoint, Not Written From Scratch
What actually happens in most companies is far less rigorous than the candidate believes.
The hiring manager opens SharePoint. They find a JD from the last person who held the role – or a similar role, or sometimes a barely-related one. They tweak the title, change a few bullets, and forward it to the talent partner with a note saying “use this as a basis.”
The talent partner adds the standard boilerplate. The legal language goes in. The diversity statement goes in. The benefits paragraph goes in. The hiring manager glances at the final version, agrees it is “close enough”, and the role goes live.
By the time it reaches you, the job description is an artefact built by committee, recycled from history, padded with corporate template. It contains the official version of what the company thinks it wants.
It rarely contains what the hiring manager actually wants.
The Real Target Is "I Know It When I See It"
Most senior hiring managers cannot articulate what they want, but they know it when they see it.
This is not a failure of intelligence but a feature of how human judgment works at this level. A senior leader who has hired thirty people across their career has a felt sense of what good looks like in their team. They have a felt sense of who walks in and seems credible. They have a felt sense of which candidates other people in the building will trust. None of that lives on the JD. It lives in the room.
The decision rests on something quieter: whether this person feels like they will fit, get up to speed quickly, get on with the senior team, and not embarrass the hiring manager at the next leadership meeting. Bullet-point matching is not part of the felt decision.
Defensibility of decision making matters in corporate environments. The JD exists so that when the hire is made, HR and legal can show it was justified. But the JD is not the brief. The brief lives in the hiring manager’s head, and on the senior team’s whiteboard, and in the gap between the two.
Logical Applicants Miss the Real Brief
This is where strong candidates trip themselves up.
A logical applicant reads the JD carefully, mirrors every requirement back in their CV, references each bullet in their cover letter, and prepares examples for every line item in the interview. The whole approach is rational, organised and high-effort. It also misses the point.
When the candidate is in the room, the hiring manager is asking themselves three quieter questions, not running a checklist: Do I want to spend time with this person? Do they understand the business I am actually running, not the one I described on paper? Will the senior team back this hire?
The over-logical applicant frequently feels like a robot – someone who has reverse-engineered the JD and recited it back. That registers as effort, not fit. Worse, it tells the hiring manager nothing they did not already know. The applicant has just played the JD back at them, more politely.
The candidate who gets appointed is rarely the one who matched the JD most precisely. It is the one who showed they understood what the role was actually for – the one who could speak about the underlying business problem, the political constraints, the team dynamics, the strategic moment – and made the hiring manager think “yes, this person sees what I see.”
Decoding Beats Matching
The shift is not subtle. Stop matching. Start decoding.
Decoding a job description means treating it as a partial description of a problem, not a complete description of a person. The questions worth asking when you read a JD are not “do I tick the boxes?” but:
• What is going on in this business right now that made them write this role?
• What problem is this team trying to solve, and what kind of person would actually solve it?
• Why is this role being posted now, and not six months ago or six months from now?
• Who already works there at this level, and what does that say about the kind of person who fits?
• What is the JD telling you, and what is it carefully avoiding saying?
These are not interview prep questions. They are research questions you answer before deciding whether to apply, who to speak to, and what to say to them. The candidate who walks into the conversation having decoded the role – and who can articulate the underlying problem better than the JD does – is a different proposition entirely. They are positioning, not applying.
The job description is a compromise document. The real target is shaped in the hiring manager’s head and on the senior team’s whiteboard, long before the role goes live and long after you apply. Reading the JD too logically means responding to the wrong brief.
Approach it intentionally rather than reactively. Decode before you apply. And if you can have a conversation with someone close to the role before you ever submit a CV, do that instead. The roles worth having are not won on paper alone.