A job description is both a candidate-facing document and an internal agreement. Done well it attracts the right people and aligns the hiring team before interviews begin.
Who this guide is for
- Hiring managers writing or approving a role
- Recruiters and HR partners standardising descriptions
- Founders making early hires without a formal HR function
Step-by-step guidance
- Define the role’s purpose. Two or three sentences on why the role exists and how it contributes.
- Write responsibilities as outcomes. Describe what success looks like, not a long task dump.
- Separate must-have from nice-to-have requirements. Keep essentials to what the role genuinely needs; move the rest to nice-to-have.
- Add compensation transparency where appropriate. A salary range builds trust and reduces wasted conversations; follow local pay-transparency rules where they apply.
- Use inclusive, plain language. Avoid jargon, inflated titles and culture-coded terms; focus on outcomes over years of experience.
- State the application process. What to submit, the stages, and a realistic timeline.
- Review before publishing. Each requirement should map to something you will actually assess.
Common mistakes
- Long "essential" lists that shrink and skew the applicant pool
- Vague responsibilities that make evaluation inconsistent
- Inflated titles or internal jargon candidates can’t parse
- No process or timeline, leaving candidates guessing
- Requirements you will never actually assess
Practical checklist
A copy-friendly checklist you can reuse for every hire.