How to Write a Job Description That Attracts the Right Candidates
A practical guide to writing job descriptions that accurately reflect the role, attract candidates who will actually perform, and avoid the common patterns that drive good people away.
Most job descriptions are written badly. Not maliciously - just quickly, by people with other priorities, copying from the last version of the same role or pulling from a template that was never updated. The result is a document that either attracts the wrong candidates, deters the right ones, or accurately describes a role that no longer exists.
A well-written job description is one of the highest-return investments in your hiring process. It shapes who applies, how they represent themselves, and what expectations they bring to the role. Getting it right upstream saves time, money, and misaligned hires downstream.
The Job Description Is Not an Internal Job Profile
The first thing to clarify: a job description (what you publish externally) and a job profile (the full internal document with competency frameworks, reporting structures, and performance criteria) are different documents for different audiences.
The job description's job is to help the right candidate decide to apply and to help the wrong candidate decide not to. It's not a legal document. It's not a comprehensive specification. It's a targeted communication to a specific audience.
Write for the candidate you want to attract, not for the HR file.
What Every Job Description Needs
A Specific, Honest Title
Job titles serve two purposes: they describe the role, and they help people find it in search. Both matter.
"Marketing Manager" is searchable but tells the candidate almost nothing. "Content Marketing Manager - B2B SaaS" tells them what type of marketing, what context, and roughly where they'd sit in the function. That specificity attracts the right people and signals you know what you're hiring for.
Avoid inflated titles ("Rockstar Developer", "Ninja Recruiter") - they're off-putting to experienced candidates and harm search visibility. Avoid deflated titles that undersell the seniority of the role to save salary banding headaches.
The Real Purpose of the Role
In two to three sentences: why does this role exist? What problem does it solve or what opportunity does it create? What would be different in twelve months if the person in this role is excellent?
This is typically the first thing a candidate reads after the title. It sets context for everything that follows. It should not be: "we are a dynamic, fast-growing company looking for a passionate self-starter to join our team." It should be: "We're scaling our enterprise sales team from 8 to 20 reps over the next 18 months. This role leads the enablement function responsible for getting new reps to quota in under 90 days."
What the Person Will Actually Do
List the three to five most important things the role is accountable for - not a comprehensive task inventory, and not vague responsibilities like "manage relationships with key stakeholders."
Good: "Own the monthly executive reporting pack - design, content, and delivery to the board." Bad: "Support senior leadership with reporting and communications requirements."
The test: could a candidate read this and describe a specific project they'd work on in their first month? If not, it's too vague.
What You're Looking For
This is the section that drives applications most directly - and where most job descriptions go wrong.
What to include:
- Skills and experience that are genuinely required to do the job on day one
- Any qualifications that are actually essential (not just conventional)
- One or two specific indicators of the level you're hiring at
What to cut:
- The degree requirement if you don't actually check it or if the role doesn't need it
- "Excellent communication skills" - every job description says this and it means nothing
- Credential inflation ("10 years of experience" for a role a strong 4-year person could do)
- Everything that's "preferred" unless it genuinely changes your decision
Every unnecessary requirement in a job description reduces application rates from qualified candidates, particularly from women and underrepresented groups, who are less likely to apply when they don't meet all listed criteria. If it's not a real requirement, remove it.
What You're Offering
Candidates are evaluating your opportunity the same way you're evaluating their application. Tell them what they need to know to make that assessment.
Salary range: include it. Candidates who get to final-stage interview and discover the salary is 20% below what they expected are frustrated, and you've wasted both of your time. Transparent salary ranges also improve application rates from candidates who would otherwise assume the worst.
Beyond salary: flexible working arrangements, equity (if applicable), professional development, team structure, what the career path looks like. These are real differentiators for many candidates - particularly at mid-career levels where people are making longer-term assessments of a role.
Common Patterns That Drive Good Candidates Away
The requirement list that goes to fifteen items. At a certain point, a long requirement list signals that the hiring team doesn't know what they actually need, or that the role is poorly scoped. Strong candidates with options will move on.
The culture paragraph that says nothing. "We're a team of passionate people who love what we do and celebrate wins together" describes every company's self-image and no company's actual culture. Specific details - how decisions get made, what the team dynamic is actually like, what a difficult day looks like - are more convincing and more useful.
"Competitive salary." This phrase signals that you have something to hide. Include the range.
Requirements that screen out non-traditional candidates. "Degree from a top university," "must have Big 4 experience," "5+ years in a similar role" - each of these is a proxy for something specific. Ask what that specific thing is, and whether the proxy is actually reliable. Often it isn't.
Writing in third person corporate voice. "The successful candidate will be responsible for..." reads as bureaucratic and creates distance. Write directly: "You'll own the sales pipeline and report directly to the VP."
Getting the Length Right
A job description that runs to 1,200 words is too long. Candidates are scanning, not reading. The right length is enough to answer: what is this role, what will I do, what do you need from me, what are you offering - and nothing more.
400-600 words for most roles. Senior or specialist roles where context genuinely matters can run longer, but 800 words is usually the ceiling before returns diminish.
Reviewing Before You Publish
Before posting, read the job description as a strong candidate who is currently employed and has three other opportunities on the table. Would this role appeal? Would the description give them enough to decide? Would any of it put them off unnecessarily?
Then read it as someone who is qualified but doesn't come from the conventional background - maybe they're transitioning from an adjacent field, or they have the skills but not the credentials. Are there barriers in the requirements list that aren't real barriers?
If the answer to either review is "I'd probably pass," revise before you post.
The job description is the first thing a candidate judges you on. Make it worth their time.
For the upstream work that makes a job description accurate rather than aspirational, see our guide to job task analysis. Once you're ready to screen applicants, structured interview questions ensure the selection process matches the criteria you've set.