Hiring strategy
Job descriptions that get read (and don't scare off the people you want)
By Kelly Robinson · August 25, 2026 · 5 min read

A posting is an ad, not a legal document. Here is how to cut the requirement list, write for the candidate who is only half-looking, and stop filtering out great people before they apply.
To our readers in England, Wales and Northern Ireland, enjoy the Summer Bank Holiday on Monday, August 31. Replies from your side of the pond can wait until Tuesday.
Here is a test. Open your most recent job posting and read the first five lines. If they are about the company ("a fast-growing leader in...") rather than about the job, you have written an ad for the wrong reader. The hiring manager and the legal team already know what the role is. The only person who needs to be persuaded is a strong candidate who is half-looking, reading on a phone, and giving you about 40 seconds.
What a posting is for
A job description has one job: get the right people to apply and the wrong people to self-select out, quickly. It is not the internal role profile, not the offer letter, and not a list of everything the last person did. Those documents can exist. They should not be what you post.
The rewrite we do before every PKR search
- Open with the outcome. One or two sentences on what this person will own and what success looks like at one year. It is the same question that produces the scorecard, which is not a coincidence.
- Cut requirements to five. Research cited widely over the past decade suggests many candidates, and women in particular, skip roles unless they meet nearly all of the listed qualifications. Every nice-to-have you dress up as a requirement costs you applicants you would have loved.
- Separate "must have" from "helpful." If you cannot bring yourself to delete a bullet, move it under a heading that makes clear it is not a gate.
- Use the title people search for. "Growth Marketing Manager" gets found. "Marketing Ninja II" does not. Internal levels and codes belong in the HRIS, not the headline.
- Post the salary range. It is required in a growing list of U.S. states and across the EU, and it saves everyone an awkward first call.
- Describe the process. How many conversations, roughly how long, who they will meet. Candidates relax when they know the path, and you get fewer drop-offs between steps.
- Read it aloud. If a sentence would sound strange said to a candidate across a table, rewrite it.
What to leave out
- Years-of-experience minimums that are proxies for something else. If you mean "has led a team through a reorg," say that.
- Degree requirements the job does not actually need. Many employers have dropped them for most roles; it widens the pool without lowering the bar.
- Anything that references or implies a protected characteristic, including coded language like "digital native" or "recent graduate."
A good posting is shorter than the one you have now, says more about the work and less about the company, and tells the reader exactly what happens if they click apply. It takes about 15 minutes to fix. It changes who shows up.
Start with the scorecard
Download the one-page hiring scorecard (PDF)Sources & further reading
- Harvard Business Review — Why Women Don't Apply for Jobs Unless They're 100% Qualified (Tara Mohr)
- U.S. EEOC — Prohibited Employment Policies/Practices (job advertisements)
- Harvard Business School, Managing the Future of Work — research on degree requirements and skills-based hiring
- SHRM — Talent acquisition research and toolkits
- PKR Insights — Pay transparency is here: how to post a salary range
Was this useful?
Want to talk this through for your team?
A no-pressure 30 minutes with Kelly.
