The job description is the first thing most candidates see, and it does more work than companies often realise. A good one attracts the right people and filters out the wrong ones; a vague or generic one either attracts a flood of poorly-matched applicants or fails to attract the good candidates you want. Since the quality of your applicant pool starts with the job description, writing it well is worth the effort. This guide covers how.
What a job description is for
A job description serves two connected purposes: it attracts candidates, and it informs them. It needs to draw the right people in — making the role appealing enough that good candidates want to apply — while giving an accurate picture of what the role involves, so that the people who apply are genuinely suited and self-select appropriately. A job description that attracts the right candidates and deters the wrong ones is doing its job; one that is so vague it attracts everyone, or so dull it attracts no one good, is not.
The dual goal — attract and inform — is worth keeping in mind, because the two have to be balanced. Pure marketing that oversells the role attracts people who will be disappointed; a dry list of requirements that fails to convey why the role is worth wanting fails to attract good candidates who have other options.
How to structure a job description
While formats vary, an effective job description generally covers:
The role and its purpose. A clear statement of the job title and what the role is actually for — what the person will do and why it matters. Candidates want to understand the substance of the role, not just its label.
Key responsibilities. What the person will actually do day to day — the core responsibilities of the role, specifically enough that candidates understand the work. This is where specificity matters most: vague responsibilities ("various tasks as required") tell candidates nothing.
Requirements and qualifications. What the role genuinely requires — the skills, experience, and qualifications that are actually needed. Distinguishing must-haves from nice-to-haves helps candidates self-assess and avoids deterring good candidates who meet the real requirements but not an inflated wish-list.
About the company and the role's context. Enough about the company, the team, and the context to help candidates understand what they would be joining and why it is appealing. This is part of the attraction.
Practical details. Location (including whether remote or hybrid), the nature of the role, and other practical information candidates need.
How to apply. A clear, easy application process — since a confusing or burdensome application loses good candidates.
Being specific about the role
The single most important quality of a good job description is specificity about what the role actually involves. Generic job descriptions — the kind assembled from boilerplate that could describe any similar role at any company — fail because they neither attract the right people nor give candidates a real basis to assess fit. A specific description that conveys the actual work, the real requirements, and the genuine context lets the right candidates recognise themselves in it and the wrong ones realise it is not for them.
Specificity also means being honest and realistic. A description that accurately conveys the role — including its challenges, not just its appeal — attracts candidates who actually want that role, leading to better hires and better retention. Overselling or vagueness attracts mismatches. So the discipline is to describe the real role specifically and honestly, which is more effective than generic marketing copy.
What to avoid
A few things undermine job descriptions. Excessive or inflated requirements — long lists of must-haves that the role does not really need — deter good candidates who would be perfectly capable, shrinking your pool unnecessarily (this is a well-known way companies inadvertently exclude good applicants). Generic boilerplate that could describe any role conveys nothing and attracts poorly-matched applicants. Jargon and internal language that candidates outside the company will not understand creates a barrier. Vagueness about the actual work leaves candidates unable to assess fit. And a burdensome application process loses good candidates who will not jump through unnecessary hoops. Avoiding these makes a description more effective.
Writing for candidates
Finally, write with the candidate in mind. The description should be clear, readable, and engaging — conveying not just the requirements but why the role is worth wanting, in language that speaks to the candidates you want to attract. It should make a good candidate think "this sounds like something I'd want to do and could do well." Balancing the informative (what the role is and requires) with the appealing (why it is worth wanting) — clearly and honestly — is the craft of a good job description. And being mindful of inclusive, accessible language helps attract a broad and diverse pool rather than inadvertently narrowing it.
Common job description mistakes
The recurring errors include:
Generic boilerplate that could describe any role and attracts poorly-matched applicants.
Inflated requirement lists that deter capable candidates and shrink the pool.
Vagueness about the actual day-to-day work, leaving candidates unable to assess fit.
Jargon and internal language that creates a barrier to outside candidates.
Overselling the role, attracting people who will be disappointed and leave.
A burdensome application process that loses good candidates.
Why job descriptions work better in a connected hiring system
A job description is the entry point to the hiring pipeline — it generates applications that flow into your candidate tracking, and a good one shapes the quality of everything downstream. When job postings, the application process, and candidate tracking are disconnected (a description posted manually here, applications landing in an inbox there), the connection between the posting and the resulting pipeline is broken, and tracking which descriptions and channels produce good candidates is hard.
When hiring runs on a connected applicant tracking system, the job description and posting are the front of an integrated pipeline — the posting can be distributed, applications flow directly into candidate tracking, and (as our metrics guide covers) you can see which postings and sources produce good candidates and hires. This is part of how Helion's hiring works, with job postings and the careers page connected to the pipeline on one platform — so the job description leads directly into managed candidate tracking, and a hire flows on through onboarding to payroll. For a company hiring regularly, having the job description connected to the rest of the hiring system means the effort of writing a good description translates into a well-tracked pipeline rather than applications scattered in an inbox.
This guide gives general information on writing effective job descriptions and reflects practical hiring experience. It is intended to help improve your job postings, not as a prescription for any specific situation. Be mindful of applicable requirements around non-discrimination and inclusive hiring for your jurisdiction.