Back to Resources
Hiring 7 min read

How to write a job description that attracts the right people

The job description is the internal definition of the role. Get it right and every decision after it becomes easier. Get it wrong and you will interview well against the wrong specification.

Learning how to write a job description properly is worth more than it sounds, because the description is not marketing. It is the specification. It decides what you screen for, what you ask at interview, what you score against, and what the person is actually accountable for once they start. The advert is a separate thing, written later, to sell the role. Confusing the two is the most common mistake, and it produces documents that neither define the job nor attract anyone.

Start with what the role has to deliver

Most job descriptions open with a list of tasks. Tasks are the wrong starting point because they describe activity, not the reason the role exists.

Write down what this role has to have delivered twelve months from now. Three or four outcomes, in plain language. "Own onboarding and cut first-month drop-off." "Run the finance close and get it down from fifteen days to eight." "Take the support queue off the founders."

Once the outcomes are written, the capabilities that matter become obvious, and so do the ones that do not. That is the whole point. A job description built from outcomes gives you a defensible list of what to assess. A job description built from tasks gives you a wish list that every interviewer interprets differently.

The structure that works

Six sections, in this order.

Role purpose. Two sentences. Why this job exists and what it owns.

What you will own. The three or four outcomes. Not a task list.

What you will bring. The genuine must-haves. Three or four. This is the section to be ruthless in, for reasons covered below.

Nice to have. Everything that would be useful but is not a reason to reject someone.

How we work. Team size, reporting line, where the role sits, hybrid or on-site, the honest version.

Pay. A range. Not "competitive".

That structure holds for almost any role and takes about forty minutes to do properly. HRM8 publishes job description templates built on it.

Be ruthless about must-haves

The requirements section is where job descriptions quietly do their damage.

A list of ten requirements is not a higher bar, it is an unexamined one. It is what happens when three people each add their own and nobody removes anything. The effect is measurable and well documented: strong candidates who meet most of the list but not all of it decline to apply, and the effect is stronger among candidates from under-represented groups. You narrow the field without raising the standard.

Apply one test to every line: would you genuinely reject an otherwise excellent candidate for missing this? If the answer is no, it belongs under nice to have. Most lists lose half their length.

The same applies to degree requirements and to years of experience. "Five years experience" is a proxy, and usually a lazy one. If what you mean is "has owned a close cycle end to end", write that instead. It is more accurate, it is easier to assess, and it does not exclude the person who did it in three years.

Write it so a human recognises the job

Some habits repel exactly the people you want.

Inflated titles. Calling a coordinator role a manager attracts people who want to manage and disappoints them in month two.

Corporate filler. "Fast-paced dynamic environment" tells a candidate nothing except that nobody spent long on this. If the pace is genuinely high, say what that means: on-call rotation, quarterly release cycle, whatever is true.

Everything and nothing. A description that lists twenty responsibilities across three disciplines reads as a role nobody has defined, and good candidates read it correctly.

Hidden pay. Omitting a range does not preserve negotiating room, it costs you applicants and wastes your time on candidates whose expectations were never going to match. In a growing number of jurisdictions it is also becoming a legal requirement rather than a choice.

Write it with the hiring manager, not for them

A job description written by HR alone describes a generic role. One written by the hiring manager alone usually describes the last person who held it, or an idealised replacement for them.

Forty minutes together is enough. HR brings structure, consistency, and the discipline to cut the must-have list. The hiring manager brings what the job actually involves on a Wednesday afternoon. Both are necessary.

If someone has held the role before, ask them what they actually spent their time on. It is regularly not what the previous description said.

From description to advert

The description is the internal source of truth. The advert is the candidate-facing version: same substance, restructured to sell rather than to specify. It leads with the work and the pay rather than the requirements, it is shorter, and it sounds like a person wrote it.

Keep the two in step. When the role genuinely changes, update the description, then the advert. Otherwise you end up advertising a job that no longer exists and assessing against a specification nobody has read since the role was created.

The advert is covered separately in write a job ad that actually converts.

Common questions

What is the difference between a job description and a job advert?

The description is the internal definition of the role: outcomes, requirements, reporting line, pay band. The advert is the public version written to attract applicants. Same substance, different purpose and different structure.

How long should a job description be?

Long enough to define the role and no longer. Most sit between 400 and 700 words. Length is not the measure. A 400-word description built on outcomes beats a 1,200-word task list.

Should a job description include salary?

Yes, as a range. It improves applicant quality, saves time on both sides, and is increasingly required by law in several jurisdictions.

Who should write the job description?

The hiring manager and HR together. Separately, each produces a predictable failure: a generic role, or a description of the last person who held it.

The takeaway

Write outcomes before tasks, cut the must-have list until every line would genuinely reject a good candidate, publish a pay range, and keep the internal description and the public advert as two documents that stay in step.