The Hidden Cost of a Bad Job Description
A poorly written job description does not just attract weak candidates - it actively repels strong ones. Senior candidates who see a wall of 25 requirements, vague role descriptions, and compensation ranges that do not match the seniority level will simply move on.
The job description is the first thing a candidate reads about your company. It is a marketing document for the role, and it deserves the same care as any customer-facing content.
Structure That Works
A high-performing job description has five sections:
The hook. A 2-to-3 sentence summary of the role's impact. Not the company history. What will this person build, change, or own?
What you'll do. 5 to 7 clear responsibilities. Use active verbs. Start with what the candidate will deliver, not what they will attend.
What we're looking for. Separate required qualifications from preferred ones. If you list 20 requirements, you will get applications from people who meet 12 of them, and the 12 they have chosen will vary widely.
What we offer. Be specific. "Competitive salary" tells candidates nothing. A range, equity details, remote policy, and meaningful benefits signal transparency.
The interview process. Outline the stages. Candidates who know the process drop out less often.
The Requirements Problem
Most job descriptions have too many requirements. Research consistently shows that women apply when they meet roughly 100% of the listed requirements, while men apply when they meet about 60%.
The fix: list only what is genuinely necessary for success in the first 6 months. Everything else is a preference.
Ask this question for each requirement: "If a candidate could not do this, would we withdraw the offer?" If the answer is no, it is a preference, not a requirement.
Language That Works Against You
Certain phrases correlate with lower-quality candidate pools and higher drop-off rates.
Avoid:
- "Rock star" or "ninja" (signals immature culture)
- "Fast-paced environment" without context
- "Must be willing to wear many hats" without explanation
- Extensive lists of technologies that are not all actually used
- "Bachelor's degree required" when the work does not require one
Use instead:
- Specific outcomes: "You will own our enterprise onboarding process and reduce time-to-live from 3 weeks to 10 days"
- Clear collaboration context: "You will report to the VP of Product and work closely with 3 engineers"
- Genuine culture signals: "We do async-first communication with two in-person offsites per year"
Salary Transparency
Posting a salary range reduces unqualified applications, speeds up the offer stage, and increases candidate trust. In jurisdictions where it is now legally required, it also keeps you compliant.
Reviewing for Bias
Run your job description through a bias checker before publishing. Common flags:
- Gendered language (aggressive, dominant, collaborative, nurturing used disproportionately)
- Requirements that screen out protected classes without being job-relevant
- Culture descriptions that implicitly favor one demographic
A job description that is honest, clear, and specific will reduce your time-to-hire, improve application quality, and set clearer expectations for the candidate who accepts the role.