How to Write a Job Description That Attracts the Right Talent
Most job descriptions repel good candidates. Here is how to write one that is clear, honest, and appealing.
Why Most Job Descriptions Chase People Away
Most job descriptions are written by committee and read like it. They stack requirements nobody could meet, list perks nobody wants, and describe a role in language so vague that strong candidates skim and move on. The cost is real: every bad posting means weeks of wasted recruiting and a pipeline full of the wrong people.
Good candidates read job descriptions with a critical eye. They are looking for signals about what the work is actually like, who they would report to, and whether the company has its act together. A posting that hides those facts behind jargon and wish lists tells them the answer is no.
The fix is to write the posting as if you were explaining the job to a sharp person you wanted to hire. Be specific about the work, honest about the tradeoffs, and clear about what success looks like. The structure below does that without turning the posting into a wall of text.
What Strong Candidates Look For
| What they want | What postings usually give them | What to do instead |
|---|---|---|
| A clear picture of the daily work | A list of vague responsibilities | Describe two or three real projects they would own |
| Realistic requirements | Ten must-haves no single person meets | Split into must-have and nice-to-have, keep musts under five |
| Honest salary range | Competitive salary, no number | Post the actual range, or at least a real band |
| Who they report to | Nothing about the team or manager | Name the role they report to and how the team works |
Lead With the Work, Not the Company
The first paragraph of a job description is the most read part of the whole posting, and most companies waste it on a boilerplate company overview. Candidates already looked at your homepage. They want to know what they would do all day. Open with the work.
Describe the role in two or three sentences: what the person owns, who they work with, and why the role exists now. If the position is new, say so and explain what triggered it. If it is a backfill, mention what the previous person moved on to do. Context like this signals a healthy organization.
Concrete examples beat abstractions. Instead of 'drive strategic initiatives,' write 'lead the migration from our legacy billing system to the new platform, working with engineering and finance.' The second version tells a candidate exactly what their first year looks like.
Building the Posting in Five Moves
- 1Write the opening about the work
Two or three sentences on what the person owns and why the role exists. Cut the company mission statement from this section. Candidates can read that on your site.
- 2List responsibilities as outcomes
Phrase each bullet as a result, not a task. 'Ship the analytics dashboard by Q3' beats 'own analytics.' Outcomes tell candidates how they will be measured.
- 3Split requirements into two tiers
Keep must-haves to four or five items that are genuinely non-negotiable. Move everything else to nice-to-have. Long must-have lists especially push out qualified women and minority candidates who self-select out unless they meet every line.
- 4Add the real context
Mention team size, reporting structure, remote or hybrid policy, and travel expectations. Vagueness here reads as a red flag and costs you applicants.
- 5Close with salary and a clear next step
Post the salary range. Explain the interview process in a few lines so candidates know what they are signing up for. Both reduce wasted time on both sides.
Phrases to Cut From Every Posting
- Rockstar, ninja, guru, and other titles that signal ego-driven culture.
- Fast-paced environment, which usually means understaffed and chaotic.
- Wear many hats, which is code for no clear role and too much work.
- Self-starter who needs no direction, often a warning about absent management.
- Competitive salary with no number attached, which candidates read as below market.
- Endless requirement lists that no human could fully meet.
Read the posting aloud to someone who does the job you are hiring for. If they laugh at a requirement or cannot explain a responsibility, rewrite it. The people already in the role are the sharpest judges of whether your description matches reality.
Requirements That Filter the Wrong Way
Requirement lists are where most postings do the most damage. Every line you add narrows the applicant pool, and many of those lines filter out exactly the people you want. A study by Harvard Business School found that requiring a college degree for roles that do not need one screens out large numbers of capable workers, many from underrepresented groups. Audit each requirement against the actual work.
Years-of-experience asks are another common problem. Asking for seven to ten years for a mid-level role often has no basis in the work itself. Describe the level of skill and independence you need instead, and let candidates map their own experience to it. You will get a better, more diverse pool.
What the Data Shows
Would a sharp person you want to hire read this posting and think, this sounds like a good job? If the answer is not clear, the posting is not ready.
Make your writing sound human
Humanize AI-generated text in one click with AI Humanizer Lab.
Try for free