What Is a Job Description?
A job description is a written document that defines a role: what the person does, what they own, who they report to, and what they need to bring to be successful in the seat. It sits between the internal job requisition (which authorises the role and commits budget) and the external job posting (which markets the role to candidates). Get the job description right and every downstream step, from sourcing to Round 1 screening to the final panel, gets easier. Get it wrong and you spend the next six weeks explaining to candidates why the role is not what the posting suggested.
This guide walks through what a job description is, what the job responsibilities and job roles sections should actually contain, how to write one that works for both recruiters and candidates, and includes a working job description template. If you have already read the companion post on the job title vs. the job role, this covers the document that ties them both together.
Table of contents
- Job description definition
- Why the job description matters
- Job description vs. job posting vs. job requisition
- The anatomy of a good job description
- How to write job responsibilities that hold up
- Job description template
- How the job description feeds screening
- Related posts
- FAQ
Job description definition
A job description is a written document that defines a role's purpose, duties, responsibilities, reporting relationships, and required qualifications. It is the reference document for everyone who touches the role: the hiring manager, the recruiter, the interviewer, the compensation team, and eventually the person who fills the seat.
The Society for Human Resource Management treats the job description as the foundational document for a role: it is what compensation teams benchmark against, what recruiters screen from, what interviewers structure questions around, and what performance conversations later refer back to. If a role has no clean job description, everything downstream is being done from memory.
Why the job description matters ?
Three practical reasons, all downstream of one core one.
First, the job description sets what the recruiter screens against. Every resume that lands in the pipeline is compared, formally or informally, to the responsibilities and requirements in the JD. A vague JD produces a noisy funnel.
Second, the job description shapes the interview. Structured interviews (see the related post on structured vs. situational interviews once published) work by turning JD responsibilities into interview questions. If the JD does not clearly name what the person will do, the interview drifts into generic behavioural questions that do not predict on-the-job performance.
Third, the job description holds up under legal scrutiny. In the United States, exempt vs. non-exempt classification, ADA reasonable-accommodation analyses, and adverse-impact review all reference the essential duties of the role. Those duties come from the JD. LinkedIn's Future of Recruiting research has flagged the shift toward skill-based descriptions, but the legal and operational role of the JD as the source of essential duties has not changed.
Job description vs. job posting vs. job requisition
Three documents, three audiences. Do not conflate them.
| Document | Audience | What it does |
|---|---|---|
| Job requisition | Internal (HR, finance, hiring manager) | Authorises the role and commits headcount budget |
| Job description | Internal + external | Defines duties, responsibilities, reporting line, and requirements |
| Job posting | External (candidates) | Marketing version of the JD; sells the role and drives applications |
The job description is the middle layer. Requisition comes first; posting is derived from the JD.
The anatomy of a good job description
Every strong JD has six sections. Skip any of them and you lose either recruiter clarity or candidate self-selection.
- Job title and level: The exact title from the requisition, level modifier included.
- Role summary: Two to four sentences on why the role exists and what it will change.
- Job responsibilities: The recurring duties, written as action statements.
- Job roles / areas of ownership: The outcomes the person is on the hook for, grouped by area.
- Requirements: Must-have skills and experience, separated from nice-to-have.
- Working details: Location, reporting line, employment type, compensation band if disclosed.
The single biggest structural fix on most JDs is separating must-have requirements from nice-to-have. When everything reads as mandatory, the funnel closes; when nothing is marked mandatory, the funnel opens too wide.
How to write job responsibilities that hold up ?
Job responsibilities are the recurring tasks and outcomes the person in the role will actually own. They are the working answer to the questions candidates and recruiters both ask: *what are the job responsibilities* here, and *what are the job roles* this person will play?
Three rules keep this section honest.
- Start each line with a verb. "Owns", "runs", "designs", "reviews", "reports on." A JD full of noun phrases ("responsibility for X", "ownership of Y") is harder to interview against than one full of verbs.
- Describe recurring work, not one-off projects. If a task only happens once, it belongs in the six-month plan, not the JD.
- Cap it at eight to twelve lines. Longer than that and readers stop reading. Group tightly related items rather than listing every micro-task.
Job description template
Copy this template into your ATS or HRIS and fill in the bracketed fields. Keep the section headings; they mirror what most ATS parsers expect.
| Section | Content |
|---|---|
| Job title | [Level] [Function] [Specialism], e.g. Senior Backend Engineer |
| Team and reporting line | Reports to [title]. Sits within [team]. |
| Role summary | 2 to 4 sentences: why the role exists and what it will change in the next 12 months. |
| Key responsibilities | 8 to 12 verb-led bullets describing recurring work. |
| Must-have qualifications | Skills and experience without which the person cannot do the job. |
| Nice-to-have | Skills that would help but are not required. |
| Working details | Location, remote policy, employment type, travel expectation. |
| Compensation and benefits | Pay band (if disclosed), core benefits summary. |
Use the same template across roles at the same level. Consistency is what makes JDs comparable across the company.
How the job description feeds screening ?
The job description is the artefact the screening layer actually reads. When a resume enters the pipeline, the recruiter's mental model is a comparison between the resume and the JD. The tighter and more responsibility-anchored the JD, the cleaner the screen.
Fabric's Interview Engine reads the job description directly. It screens resumes against the must-have qualifications, checks eligibility on parameters like budget, location, and years of experience, then runs the AI-led Round 1 interview against scenarios derived from the responsibilities (pair programming for engineering roles, case studies and guesstimates for product and consulting, cold-call and cold-email simulations for sales and customer success). Fabric's screening is designed to flag mismatches between what the JD calls out as required and what the resume actually shows, and surface those to your recruiter. It's a signal for your team to weigh, not an automatic reject. The recruiter or hiring panel still owns the shortlist decision.
For teams running high-volume roles, this is the difference between a Round 1 pool the recruiter can actually work through and a pool that just re-creates the top-of-funnel problem.
Related posts
- What is a job requisition?
- Job title vs. job role
- What is a job applicant?
- The recruitment process, end to end
- Employee referral program guide
FAQ
What is a job description?
A job description is a written document that defines a role's purpose, duties, responsibilities, reporting relationships, and required qualifications. It is used internally to guide hiring and externally to attract candidates.
What are the job responsibilities in a job description?
Job responsibilities are the recurring tasks and outcomes the person in the role owns, written as action-oriented statements. They should describe what the role does day to day, not what the company hopes the person will be.
What are the job roles listed in a job description?
The job roles section lists the specific functions the person will perform, grouped by area of ownership. It answers what the person is on the hook for, in plain language.
What is the difference between a job description and a job posting?
A job description is the internal document that defines the role's duties and requirements. A job posting is the marketing version written for candidates and hosted on career sites or job boards.
Who writes the job description?
The hiring manager typically drafts responsibilities and requirements, then HR reviews and finalises the document. Recruiting may adapt it into the outward-facing posting.
How long should a job description be?
Between 300 and 700 words is a good working range. Long enough to describe the role clearly, short enough that a candidate will actually read it.