How to Write Better Job Descriptions That Attract Qualified Candidates

Most job descriptions are written in a rush. A hiring manager sends bullet points to a recruiter, the recruiter pastes them into a template, and the posting goes live within an hour. The result is a document that technically describes a role but fails at its actual job: attracting the right people and discouraging the wrong ones.

The cost of a poorly written job description is invisible but real. Vague requirements attract hundreds of unqualified applicants who consume recruiter time. Bloated requirement lists discourage qualified candidates - especially women and underrepresented groups - from applying. And generic language makes your role indistinguishable from the 50 other postings a strong candidate sees that week.

Why Most Job Descriptions Fail

Job descriptions fail for predictable reasons, and understanding those patterns is the first step toward fixing them. The most common failure mode is treating the job description as an internal document rather than a candidate-facing one. Internal requirements documents serve a different purpose than recruiting content - conflating the two produces postings that read like procurement specifications instead of opportunities.

The second common failure is requirement inflation. Over years of hiring, organizations accumulate requirements that no longer reflect what the role actually needs. A mid-level marketing position ends up requiring an MBA, 8 years of experience, fluency in six tools, and industry-specific certifications - when the actual work could be done well by someone with strong fundamentals and 3-4 years of relevant experience.

Structure That Converts: The Five-Section Framework

Effective job descriptions follow a consistent structure that gives candidates the information they need in the order they look for it. After analyzing high-performing postings across thousands of roles, a clear pattern emerges.

Section 1: The Hook (2-3 sentences)

Open with what makes this role interesting or impactful - not with your company boilerplate. A software engineer wants to know what they will build and why it matters. A sales leader wants to know the market opportunity and team they will inherit. Lead with the work, not the company history.

Section 2: What You Will Do (5-7 bullets)

Describe the actual work in concrete terms. Replace vague bullets like "drive strategy" with specific outcomes like "define and execute the Q3 expansion into two new market segments." Candidates should be able to read this section and picture their first month on the job.

Section 3: What You Bring (5-7 bullets)

Separate absolute requirements from preferences. Label them clearly: "Required" and "Nice to have." For each requirement, ask whether you would actually reject an otherwise strong candidate who lacked it. If the answer is no, move it to preferences or remove it entirely.

Section 4: What We Offer (4-6 bullets)

Include compensation range, benefits, and the working arrangement. Be specific. "Competitive salary" means nothing. "$120K-$150K base plus equity" tells candidates exactly what to expect. Include details about remote policy, team size, reporting structure, and growth paths.

Section 5: How to Apply (2-3 sentences)

Tell candidates what happens after they apply. "You will hear from us within 5 business days" sets a concrete expectation and signals that your process is organized. Outline the interview stages so candidates can plan accordingly.

Language That Attracts Instead of Repels

The words you choose in a job description directly influence who applies. Research consistently shows that certain language patterns discourage qualified candidates while attracting overconfident ones - exactly the opposite of what most organizations want.

Gendered language is the most studied example. Words like "dominant," "competitive," and "aggressive" reduce female applications by 20-30% without improving male applicant quality. Neutral alternatives like "collaborative," "driven," and "results-oriented" attract equally qualified candidates from a broader pool.

Jargon and acronyms create a similar filtering effect. Internal terminology that makes sense to your team can exclude qualified external candidates who use different terms for the same skills. Write job descriptions in the language your target candidates use, not the language your organization uses internally. AI recruiting tools can analyze your posting language for these patterns and suggest improvements automatically.

• Replace gendered language with neutral alternatives - use tools to audit automatically
• Write in second person ("you will") rather than third person ("the candidate will")
• Use active voice and concrete verbs instead of passive constructions
• Avoid superlatives like "world-class" and "best-in-class" - they signal nothing
• Spell out acronyms at least once, even common industry ones
• Cut filler phrases: "responsible for" can almost always be removed without changing meaning

The Requirements Problem: Less Is More

The single highest-impact change most organizations can make to their job descriptions is reducing the number of listed requirements. The research on this is unambiguous: inflated requirement lists reduce application volume from qualified candidates, disproportionately exclude underrepresented groups, and do not improve hire quality.

The mechanism is straightforward. Studies have shown that men typically apply to jobs when they meet about 60% of the listed qualifications. Women tend to apply only when they meet 100%. By listing 15 requirements when the role truly needs 6, you systematically exclude candidates who would perform well in the role but self-select out of the application process.

The fix is discipline. For each requirement, ask three questions: Has a successful hire in this role ever lacked this skill? Could someone learn this within their first 90 days? Would you pass on an otherwise excellent candidate who did not have it? If the answer to any of these is yes, the item is a preference, not a requirement.

Salary Transparency: The Competitive Advantage

Including compensation information in job descriptions is no longer optional in many jurisdictions, but even where it is not legally required, it is strategically advantageous. Postings with salary ranges receive significantly more applications, attract candidates with aligned expectations, and reduce time-to-fill by eliminating late-stage compensation mismatches.

The objection most hiring leaders raise - "we will overpay for roles where we could have negotiated lower" - does not hold up in practice. When candidates know the range upfront, negotiations focus on where within the range is appropriate given their experience, not on establishing the range itself. This produces faster, less adversarial offer conversations and higher acceptance rates.

For roles with wide compensation bands, provide context. "$90K-$150K depending on experience" is less helpful than "$90K-$110K for candidates with 3-5 years of experience; $120K-$150K for candidates with 6+ years and leadership background." The specificity helps candidates self-select into the right part of the range. When paired with AI matching systems, salary alignment becomes an automatic part of the screening process.

Testing and Iterating on Job Descriptions

Job descriptions should be treated like any other piece of performance-sensitive content - tested, measured, and iterated. Most organizations publish a posting once and never revisit it, even when the results are poor. A simple testing framework can dramatically improve outcomes.

1. Track application-to-interview ratio: If fewer than 15-20% of applicants are worth interviewing, the description is attracting the wrong people. Revise the requirements and language.
2. Measure time-to-first-qualified-applicant: Strong descriptions attract qualified candidates within the first 48 hours. If it takes two weeks to see a viable applicant, the posting is not reaching or resonating with the right audience.
3. A/B test when possible: If you are posting on multiple boards, vary the description slightly and track which version produces better applicants. Even small changes to the opening paragraph can shift results.
4. Collect candidate feedback: Ask new hires what attracted them to the posting and what almost made them skip it. This qualitative data is invaluable for refining future descriptions.
5. Review competitor postings: For high-competition roles, read how other companies describe similar positions. Identify opportunities to differentiate your posting on specificity, transparency, or tone.

Common Mistakes to Avoid

Copying and pasting from previous postings. Roles evolve. The job description from two years ago probably does not reflect the current team, tools, or priorities. Start fresh for each new hire, using previous descriptions as reference rather than template.

Writing for compliance instead of candidates. Legal disclaimers and equal opportunity statements are necessary, but they should not dominate the posting. Place compliance language at the end, not the beginning.

Listing every tool in your stack. Requiring proficiency in 12 specific software tools tells candidates you want someone who already does this exact job at another company. Focus on capabilities and aptitudes - a strong candidate can learn your specific toolchain. For more on how to think about skills-based hiring, see our platform overview.

Frequently Asked Questions

How long should a job description be?

The optimal job description length is 300-700 words. Postings in this range receive 30% more applications than those over 1,000 words. Focus on the information candidates need to decide whether to apply: what the role involves, what success looks like, who they will work with, and what the compensation range is. Cut everything else.

Should job descriptions include salary ranges?

Yes. Job postings with salary ranges receive 30-40% more applications and attract more qualified candidates. Beyond the legal requirements expanding across jurisdictions, salary transparency signals respect for candidates' time and filters out misaligned expectations early in the process. Companies that post ranges also report faster time-to-fill and higher offer acceptance rates.

How many requirements should a job description list?

List 5-7 core requirements maximum. Research shows that women and underrepresented candidates are less likely to apply if they do not meet every listed requirement, while men typically apply meeting only 60%. Limiting requirements to genuine must-haves broadens your qualified applicant pool without lowering the bar. Separate true requirements from preferences, and label them clearly.