Most hiring post-mortems blame the interview, the recruiter, or the candidate. Far fewer look at the document that started it all: the job description. Yet a JD is the single most leveraged artifact in your whole hiring process — it decides who applies before anyone has spent a minute screening. Get it wrong and you don't just get fewer applicants; you get a pipeline quietly stacked with the wrong people, and you don't find out until three rounds and several weeks later.
The JD is a filter you set once and pay for repeatedly
Every vague line, inflated title, and unnecessary "must-have" changes who raises their hand. The cost of a bad JD isn't visible on day one — it shows up as a thin shortlist, mis-calibrated interviews, and a hire whose reality doesn't match the pitch. Reported patterns put that mismatch surfacing inside the first 90 days.
Why does a bad job description attract the wrong candidates?
Because a JD is a self-selection tool, and a bad one is miscalibrated. Candidates read it and decide whether they fit — so when it's vague, inflated, or buzzword-heavy, the people who apply are the ones most confident, not most qualified. You've effectively tuned the filter to favour the wrong signal, and every downstream step inherits that distortion.
Three failure modes do most of the damage. Vagueness ("manage inventory," "own the roadmap") gives no one a real basis to judge fit, so everyone applies. Inflated or cutesy titles ("Growth Hacker," "Sales Ninja," "Data Rockstar") confuse search and attract people optimising for the label rather than the work. And wishlist requirements — a dozen "must-haves" for a role that genuinely needs four — do something worse than you'd expect: capable candidates who read the list honestly count themselves out, while overconfident ones who ignored it apply anyway. You filter out the people you wanted and keep the ones you didn't.
Which specific lines cause the damage — and what to write instead?
The fix is almost always concrete. Here are the common offenders with a rewrite and the reason it works:
- The line that backfires
- "Manage inventory and related processes."
- Rewrite it as
- "Own stock accuracy across 3 warehouses; cut stockouts, reported weekly to the ops lead."
- Why the rewrite works
- A measurable, concrete duty lets the right people recognise themselves — and the wrong ones opt out.
- The line that backfires
- "Marketing Rockstar / Growth Hacker."
- Rewrite it as
- "Performance Marketing Executive (2–4 yrs)."
- Why the rewrite works
- A plain, searchable title matches how real candidates search and sets accurate expectations.
- The line that backfires
- 12 undifferentiated "must-have" skills.
- Rewrite it as
- "Must-have: 4 items. Nice-to-have: the rest."
- Why the rewrite works
- Long must-have lists make qualified people self-reject; splitting them widens a strong pool.
- The line that backfires
- "Aggressive, dominant self-starter; work hard, play hard."
- Rewrite it as
- "Proactive and collaborative; takes ownership of outcomes."
- Why the rewrite works
- Neutral wording avoids coded language shown to shrink the share of women who apply.
- The line that backfires
- "Fast-paced, wear many hats, rockstar, guru."
- Rewrite it as
- "You'll juggle 3–4 priorities weekly; here's a typical week: …"
- Why the rewrite works
- Specifics survive contact with reality; buzzwords set up the mismatch that drives early exits.
- The line that backfires
- Only the glamorous parts of the role.
- Rewrite it as
- An honest "day in the life," including the routine parts.
- Why the rewrite works
- A realistic preview is a retention tool — people who know the real job are likelier to stay in it.
- The line that backfires
- No salary signal at all.
- Rewrite it as
- A band, or a stated intent to discuss range early.
- Why the rewrite works
- A range filters out expectation mismatches before they waste rounds on both sides.
| The line that backfires | Rewrite it as | Why the rewrite works |
|---|---|---|
| "Manage inventory and related processes." | "Own stock accuracy across 3 warehouses; cut stockouts, reported weekly to the ops lead." | A measurable, concrete duty lets the right people recognise themselves — and the wrong ones opt out. |
| "Marketing Rockstar / Growth Hacker." | "Performance Marketing Executive (2–4 yrs)." | A plain, searchable title matches how real candidates search and sets accurate expectations. |
| 12 undifferentiated "must-have" skills. | "Must-have: 4 items. Nice-to-have: the rest." | Long must-have lists make qualified people self-reject; splitting them widens a strong pool. |
| "Aggressive, dominant self-starter; work hard, play hard." | "Proactive and collaborative; takes ownership of outcomes." | Neutral wording avoids coded language shown to shrink the share of women who apply. |
| "Fast-paced, wear many hats, rockstar, guru." | "You'll juggle 3–4 priorities weekly; here's a typical week: …" | Specifics survive contact with reality; buzzwords set up the mismatch that drives early exits. |
| Only the glamorous parts of the role. | An honest "day in the life," including the routine parts. | A realistic preview is a retention tool — people who know the real job are likelier to stay in it. |
| No salary signal at all. | A band, or a stated intent to discuss range early. | A range filters out expectation mismatches before they waste rounds on both sides. |
Rewrites are illustrative patterns, not a specific client's JD. Effects (coded-language and realistic-preview findings) are reported research directions, not AxureOne's own data — adapt the specifics to your role and market.
The through-line: replace adjectives with evidence. Every time you're tempted to write "dynamic," "rockstar," or "fast-paced," describe the actual thing instead — a real duty, a real week, a real number. Specifics attract people who want that job; adjectives attract people who like that sentence.
Is honesty in a JD actually good for hiring?
Yes — and counterintuitively, it's one of your best retention levers. A large share of employees report leaving a job because it didn't match what they were told during hiring, and candidates given a realistic job preview — the unglamorous parts included — are markedly more likely to stay. A JD that oversells buys you a bigger pipeline and a worse hire; a JD that tells the truth buys you a slightly smaller pipeline of people who actually want the real role. In a market where a mis-hire and a fast exit both cost real money, the honest version wins on economics, not just ethics.
This is also where transparency on pay helps. Publishing at least a salary band — still uncommon in India — cuts wasted rounds by filtering out expectation mismatches early, and signals a straightness that candidates increasingly expect. If you can't publish a number, being ready to discuss the range in the first conversation recovers most of the benefit.
Audit your next JD before you post it
Before a single word goes live, run the draft against this:
The 8-point JD self-audit
0 of 8 checkedWhere this fits in the bigger hiring picture
A sharp JD is step one, not the whole job — but it's the step that quietly determines the quality of every step after it. Get it wrong and the same distortion shows up as a thin shortlist, offers to people who then ghost you before joining, and the occasional mis-hire whose reality never matched the pitch. Get it right and you've narrowed weeks of downstream work before it starts. It's also why, in our end-to-end model, JD drafting is genuinely the first thing we do — not an afterthought handed back to you to write yourself.
Curious what the wrong hire actually costs once a weak JD lets one through? Run the numbers on the cost-of-a-bad-hire calculator, and if it's speed rather than quality that's slipping, why your hiring takes 45 days (and how to get it to 15) is the companion piece. When you'd rather hand the whole loop — starting with the JD — to someone who does it for a living, tell us what you're hiring for.