Most job descriptions are written by committee, optimized for legal compliance, and designed to describe a fictional ideal candidate rather than a real role. The result is postings that attract the wrong people, repel strong ones, and waste everyone's time. Here's how to do it better.
Start With the Real Problem You're Hiring to Solve
Before writing a single line, answer this question: what is the specific problem this person will be solving in their first six months? Not the general function, not the team they'll sit on — the concrete problem. "We need someone to rebuild our data pipeline because it's causing reporting delays that affect pricing decisions" is a real problem. "Seeking a data engineer to join our growing team" is not.
Leading with the real problem attracts candidates who get excited about that specific challenge. It repels candidates who want a different type of work. That's exactly what you want — a self-selecting filter before the application even arrives.
The Required Skills Problem
The most damaging section of most job descriptions is the requirements list. Studies have consistently shown that male candidates apply when they meet 60% of listed requirements while female candidates tend to apply only when they meet 100%. This means inflated requirements lists systematically reduce diversity before you've seen a single resume.
More practically: requirements lists are often wish lists assembled by multiple stakeholders, not honest assessments of what the role actually needs. Ask yourself which requirements are truly mandatory for someone to succeed in the role on day one, and which are aspirational. If you'd genuinely consider a candidate who doesn't have a listed requirement, it shouldn't be in the required section.
What Candidates Actually Want to Know
Strong candidates — the ones with options — are evaluating you as much as you're evaluating them. They want to know things most job descriptions don't include: how success in the role is actually measured, what the team culture is like, what the biggest challenge the person in this role will face is, and what growth looks like from this position.
A job description that answers these questions honestly will attract candidates who are making an informed decision to apply — which dramatically improves the quality and seriousness of your applicant pool compared to a posting that reveals nothing.
Salary Transparency
Including a salary range is no longer optional in many US states — California, New York, Colorado, Washington, and others require it by law. Beyond compliance, it's simply more efficient. Candidates who screen themselves out because the range doesn't fit their expectations save everyone time. Candidates who apply knowing the range are more likely to accept an offer. The discomfort of posting the range is almost always smaller than the cost of hiding it.
The Length Problem
Most job descriptions are too long. Candidates skim them in 30 to 60 seconds. A focused, honest posting of 300 to 500 words outperforms a comprehensive 1,200-word document in both application quality and quantity. Write for the candidate reading on their phone between meetings, not for the recruiter who spent three hours writing it.
Use RecruiterSignal to evaluate the candidates your job description attracts — getting a clear picture of fit before you invest in a full interview process.