Skip to content
Contact Explore resources
Resources Tools About Contact

How to Write Job Descriptions

A clear job description is the foundation of a good hire — it filters the right applicants in and sets the bar for evaluation. This guide covers structure, language and review.

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

  1. Define the role’s purpose. Two or three sentences on why the role exists and how it contributes.
  2. Write responsibilities as outcomes. Describe what success looks like, not a long task dump.
  3. Separate must-have from nice-to-have requirements. Keep essentials to what the role genuinely needs; move the rest to nice-to-have.
  4. Add compensation transparency where appropriate. A salary range builds trust and reduces wasted conversations; follow local pay-transparency rules where they apply.
  5. Use inclusive, plain language. Avoid jargon, inflated titles and culture-coded terms; focus on outcomes over years of experience.
  6. State the application process. What to submit, the stages, and a realistic timeline.
  7. 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.

How to Write Job DescriptionsPractical checklist
☐ Role purpose stated in 2–3 sentences ☐ Responsibilities written as outcomes ☐ Must-have vs. nice-to-have separated ☐ Compensation approach decided (and compliant) ☐ Inclusive, plain language reviewed by a second person ☐ Application steps and timeline stated ☐ Every requirement maps to an assessment
For informational purposes only. Hiring and employment rules — including questions you may and may not ask, screening, and record-keeping — vary by jurisdiction and industry. Review local requirements and consult qualified HR or legal professionals before relying on any guidance here.
FAQ

Frequently asked questions

How long should a job description be?

Long enough to be clear and no longer. A concise summary, five to eight outcome-based responsibilities and an honest requirements list usually suffice — density beats length.

Should I include salary in a job description?

Including a range builds trust and reduces wasted conversations, and is required where pay-transparency rules apply. Otherwise a band is still good practice.

How do I make a job description inclusive?

Focus on outcomes rather than years of experience, separate essentials from nice-to-haves, use plain neutral language, and have someone outside the hiring team review it.

Who should approve the final job description?

The hiring manager owns the content; a second reviewer (HR or a peer) checks clarity, requirements and inclusive language before publishing.