Extended definition
The job specification is the document candidates encounter when they consider a role. It appears on the careers site, in job ads, in recruiter outreach, and across job boards.
Its job is to attract qualified candidates — accurately enough that unqualified ones self-select out, compellingly enough that qualified ones apply or respond. Most JDs do the first part badly (vague requirements, generic responsibilities) and the second part worse (corporate boilerplate that signals nothing distinctive).
Strong JDs are specific, honest, and written for the candidate’s perspective rather than HR’s compliance needs. They convert better, attract more relevant applicants, and reduce wasted screening time.
Key elements of a job specification
A working JD covers seven sections:
- Role title and team context — Job title, team, manager, location, work model. Basic orientation that lets candidates self-assess fit at a glance.
- What the role does — Responsibilities written as outcomes, not activities — “own the customer onboarding experience for enterprise accounts” beats “manage onboarding processes.” Outcome framing helps candidates picture themselves in the role.
- What success looks like — Specific, measurable expectations for the first 6-12 months. Helps candidates assess whether the role matches their ambitions and capabilities.
- Required qualifications — The minimum threshold to apply credibly — skills, experience, certifications. Should genuinely be required; long lists of “required” items that aren’t really required reduce diverse application volume without improving hire quality.
- Preferred qualifications — Nice-to-haves that strengthen the application but aren’t disqualifying. Important to separate from required so candidates don’t self-select out unnecessarily.
- Compensation and benefits — Salary range (where regulation requires it, and increasingly as best practice elsewhere), equity, key benefits, leave policies. Transparency lifts response rates and reduces late-stage withdrawal.
- EVP and culture content — Why work here — the team, the mission, the working environment. Distinct, honest framing. Generic culture claims signal nothing.
The strongest JDs read like they were written by someone who has done the role, not by HR or compliance. They speak to candidates as professionals, surface honest trade-offs, and leave the candidate with enough information to self-assess fit before applying.
Why job specifications matter
JDs shape the top of the funnel. Strong JDs attract relevant applicants and screen out wrong-fit ones before they apply.
Weak JDs do the opposite — generic content attracts generic applicants, vague requirements produce uncertainty about who should apply, and missing compensation surfaces deal-breakers late in the process. JD quality also signals brand quality.
Candidates judge the company partly by how well it describes its own roles. Sloppy JDs signal sloppy operations; thoughtful JDs signal thoughtful organisations.
Common mistakes and misconceptions about job specifications
- Long lists of “required” qualifications — Most “requirements” lists include items that aren’t really required. The longer the required list, the more qualified candidates self-select out, particularly women and underrepresented groups who tend to apply only when they meet most-to-all requirements. Tighter required lists improve diverse application volume.
- Generic responsibilities. “Manage projects to delivery” describes thousands of roles. Specific, outcome-framed responsibilities (“ship the new customer onboarding flow by Q2 in partnership with Engineering and Product”) describe one role and let candidates assess fit.
- Boilerplate culture content — Every JD claiming “great culture, smart people, growth opportunities” sounds identical and signals nothing. Specific culture content — actual rituals, decision-making norms, working environment details — differentiates.
- Missing compensation — Posting JDs without compensation forces candidates to invest in the application process before discovering whether the role is even financially viable. Where regulation doesn’t require disclosure, transparency still lifts application quality and reduces late-stage withdrawal.
- Treating JDs as compliance documents — JDs written by legal or HR for compliance reasons usually fail at attracting candidates. Strong JDs are written by people closer to the role, with HR and legal review for compliance rather than authorship.
Frequently asked questions
What is a job specification?
A job specification — often called a job description or JD — is the candidate-facing document describing a role. It covers responsibilities, required qualifications, preferred qualifications, and what the company offers. It's the public face of the role. It appears on the careers site, in job ads, in recruiter outreach, and across job boards.
What's the difference between a job specification and a job description?
The terms are often used interchangeably. Some style guides distinguish them — "job description" for the candidate-facing recruitment document, "job specification" for an internal HR document covering grade, band, and detailed competencies. In modern recruiting practice, both labels usually refer to the same candidate-facing artefact.
What's the difference between a job specification and a job brief?
A job specification is candidate-facing and designed to attract applications. A job brief is recruiter-facing and operational — target companies, internal compensation bands, sourcing strategy. They serve different audiences with different content. Most companies need both; they're not interchangeable.
Should job specifications include salary?
Increasingly yes — both because of regulation in many jurisdictions and because transparency lifts application quality and reduces late-stage withdrawal. Where regulation doesn't require it, posting salary ranges still produces stronger response rates and screens out compensation-misaligned candidates earlier in the process.
How long should a job specification be?
Long enough to give candidates the information they need to self-assess fit, short enough to be readable. Most strong JDs run 400-700 words. JDs over 1,000 words usually contain padding or compliance content that could be trimmed without losing useful information.