Job Description Template
A job description is the first thing a strong candidate reads and the last thing a weak process fixes. This template — and the structure behind it — turns a list of duties into a role that attracts operators, not keyword-matchers.
- Section-by-section
- Outcome-led
- Print or fill on screen
A sharper JD does the first round of filtering for you
Written well, the description attracts the right people and quietly turns away the wrong ones — before a single CV lands.
Why good job descriptions matter
Most job descriptions are written in an afternoon, borrowed from the last one, and never read critically again. Yet the JD is doing more work than any other document in the hire: it decides who applies, sets the bar the panel scores against, and becomes the promise the new hire measures you by. Get it wrong and you pay for it at every later stage.
A strong description is not longer — it is more honest. It says what the role exists to change, what the person will own, and what evidence you actually need. That precision is what separates the candidates who could do the job from the ones who merely match the words.
Common mistakes
Six ways a job description quietly costs you the candidates you wanted.
Structure of a professional JD
Seven sections, each doing one job. The template gives you the frame; this is what belongs in each.
| Section | What goes in it | Watch out for |
|---|---|---|
| Role summary | One or two sentences on why the role exists and what it changes | Describing the team instead of the role |
| Responsibilities | Five to seven ownership statements, each led by a verb | Listing tasks rather than outcomes |
| Must-have | Evidence the candidate must already have — things done, not traits | Padding the list until real applicants drop out |
| Nice-to-have | Genuinely optional strengths that would help | Slipping must-haves in here, or vice versa |
| KPIs | How success is measured in the first year | Vanity metrics no one can influence |
| Reporting line | Who the role reports to, and the shape of the team | Hiding a complex or dotted-line structure |
| Benefits | Compensation band and the honest reasons people stay | Generic perks lists with no numbers |
Get the Job Description Template
Work through it top to bottom — by the end you have a description you can post with confidence. Fill it on screen and save as PDF, or print it. Free, English and Persian.
Job Description Template
A role profile built around outcomes and evidence. Work through it top to bottom — by the end you have a job description that attracts operators, not keyword-matchers.
Role summary
Use the market's name for the role, not an internal invention
State the range — transparency filters in, not out
One or two sentences: why this role exists and what it changes. If you cannot write this, the role is not ready to be posted.
Outcomes in the first 12 months
Three or four concrete results that define success — "reduce time-to-close from 60 to 40 days", not "improve processes". Strong candidates choose roles by these lines.
Responsibilities
Five to seven ownership statements, each starting with a verb: owns, leads, decides, delivers. Cut anything that reads like a task list.
What we look for
Things the candidate has already done — not traits. Keep it to five lines; every extra line costs you real applicants.
Genuinely optional. If losing it would kill the hire, move it up.
Offer and process
Compensation, benefits and the honest reasons people stay
Stages, who the candidate meets, and how long a decision takes
Questions hiring teams ask
How long should a job description be?
As short as the role allows — usually one page. Length isn't the goal; precision is. If a line doesn't help the right person self-select in or out, it's costing you attention, not earning it.
Should we include the salary?
Yes. Stating a band shortens the process, builds trust, and filters for people who fit the level rather than wasting finalists on a number that was never going to work. Withholding it mostly protects your discomfort, not your leverage.
How many must-haves should we list?
Three to five. Every additional must-have removes qualified applicants, and the ones you lose are often the strong, selective candidates who won't apply to a wish list. Be ruthless about what is genuinely non-negotiable.
What's the difference between responsibilities and KPIs?
Responsibilities are what the person owns; KPIs are how you'll know they've done it well. A JD needs both — ownership attracts, measurable outcomes qualify — and they should point at the same handful of priorities.
Can we reuse an old job description?
As a starting point for format, yes — but rewrite the substance from the current mandate. Reused JDs quietly carry forward requirements and framing no one believes any more, which is how a role drifts away from what the team actually needs.
Templates that pair with this
Hiring for a role that has to land?
Our consultants write the brief, the description and the assessment as one system — so the JD you post is the role you actually get.