Job Description

A complete job description covers job title and level, department and reporting line, a concise role summary of two to three sentences, a prioritized list of core responsibilities using action verbs, required qualifications separated from preferred ones, any physical or technical requirements, the compensation band or range, work location and schedule expectations, and a brief description of the team or function. Separating required from preferred qualifications is particularly important: inflated requirements disproportionately discourage qualified candidates, especially women and underrepresented groups, from applying.

A well-maintained job description documents the essential functions of a role, which is required for compliance with disability accommodation law in many countries. It establishes the legitimate business requirements that must underpin hiring, promotion, and termination decisions. Outdated descriptions that no longer reflect actual duties create legal exposure because decisions made against criteria that do not reflect real job requirements are harder to defend. Annual reviews tied to performance cycles are a simple way to keep descriptions accurate.

A job description is an internal operational document. A job posting is the externally published version adapted for candidate attraction. The posting selectively draws from the description but is written in the second person, emphasizes employee value proposition, minimizes jargon, leads with candidate-facing benefits, and is optimized for the platform and audience where it will appear. The description and posting should be consistent in requirements but serve entirely different purposes and audiences.

A job description defines a role on paper: its title, purpose, and where it sits in the organization; the core responsibilities and day-to-day activities; the required and preferred qualifications, skills and experience; and practical details like location, employment type and reporting line. Many also state the competencies and success outcomes that distinguish a strong performer.

The best descriptions separate genuine must-haves from nice-to-haves. Overloading the requirements with every conceivable skill deters qualified applicants — especially those from under-represented groups who tend to self-select out unless they meet nearly every criterion — so disciplined prioritization widens and strengthens the applicant pool.

A job description is the internal, comprehensive definition of the role, used for hiring, leveling, compensation and performance management. A job posting is the outward-facing advertisement derived from it, written to attract and persuade candidates, and usually shorter, warmer and more focused on why the role is worth applying for.

Confusing the two produces weak results in both directions: a dry internal description published as an advert fails to attract, while a marketing-style post used as the formal role definition lacks the detail needed later. The description is the source; the posting is the pitch built from it.

Inclusive language and structure widen the funnel. Neutral, jargon-free wording, a focus on outcomes rather than a wish-list of credentials, and removing gender-coded or unnecessarily exclusive phrasing all encourage a broader range of applicants. Stating the salary range, where practical, improves trust and application rates.

Clarity sells the role honestly. Describing real responsibilities, growth opportunities and the team environment helps candidates self-assess fit, which improves the quality of applications and reduces mismatched hires. Vague, inflated or copy-pasted descriptions attract volume but not fit.

The job description is the reference point for everything downstream. The scorecard, interview questions and screening criteria should all trace back to the competencies and responsibilities it defines, which keeps the whole process aligned to what the role actually needs rather than to each interviewer's private idea of it.

It also anchors fairness and compliance. When advancement and rejection decisions map to documented, job-relevant requirements, the process is more defensible and less prone to bias. A well-built description is therefore not paperwork but the foundation that makes structured, consistent hiring possible.

Writing the description forces the hiring manager and recruiter to agree on must-have versus nice-to-have requirements, the level, and the success outcomes, resolving disagreements on paper before any candidate is evaluated against shifting expectations.

That shared, specific document then becomes the reference for screening criteria, interview scorecards, and offer level, keeping the whole process consistent and reducing the mid-pipeline scope changes that waste everyone's time and lengthen time-to-fill.

Most organisations do not have a job description problem so much as a job description sprawl problem. Each manager writes their own when a vacancy appears, copies the nearest old one, and edits the parts that feel wrong. Over a few years titles diverge, two teams describe the same work differently, and the levels stop lining up with the pay structure they were meant to support.

Managing them as a library changes three things. One person or team owns the template and the taxonomy of titles and levels. A review is triggered by an event — a requisition opening, a restructure, a pay review — rather than by good intentions. And superseded versions are kept rather than overwritten, because the description in force at the time is what a later pay or performance dispute gets read against.

The template supplies structure: purpose, reporting line, outcomes, responsibilities, requirements and the working arrangement. What makes it a specific role is the outcomes section, written as what the person is accountable for producing rather than how they will spend their time. Requirements are the part most often copied without thought, and the part that quietly narrows the applicant pool the most.

Take HR and recruiting roles as an example. An HR manager description is anchored on policy, employee relations and the HR function's own delivery. An HR business partner description is anchored on advising one business unit's leaders. A recruiter description is anchored on filling requisitions to an agreed quality and speed. Same template, three genuinely different accountability statements — and the common drafting error is to keep the template wording and change only the title.