TL;DR

A job description is an internal HR document that defines a role for organizational and legal purposes. A job posting is external advertising copy designed to attract qualified candidates. They serve different audiences, different purposes, and should be written differently. Most organizations use the job description as the job posting and pay for it in application quality.

The Two Documents and Why They Are Different

A job description and a job posting are not two names for the same thing. The job description is an internal reference document maintained by HR. It establishes what a role does, what it reports to, what competencies it requires, and how it fits into the organization's structure and pay bands. It is written for HR compliance, compensation benchmarking, legal defensibility, and performance management. The audience is internal: HR professionals, hiring managers, legal counsel, and compensation analysts.

A job posting is external advertising. Its audience is the job seeker who has three seconds to decide whether to keep reading. Its purpose is conversion: turning someone who was passively scrolling into someone who submits a qualified application. It must answer the candidate's primary questions within the first paragraph: what is the role, where is it located, what does it pay, and why should I care? The writing style should be direct, specific, and human rather than comprehensive and formal.

The confusion between the two documents is structural in most organizations. An ATS system typically holds the job description in a field labeled "job description." When a recruiter posts a role, they paste the job description into the same field and publish. The candidate sees the internal HR document. The result is a posting that opens with boilerplate about the company's mission, follows with seventeen lines of "responsibilities" written in passive voice, requires ten years of experience for a role that mid-level candidates perform every day, and omits salary information because the job description does not contain it.

Why It Matters for Recruitment

The cost of conflating these documents shows up in application volume, quality, and [time-to-fill](/glossary/time-to-fill). A posting that is actually a job description has a higher reading burden, a longer qualification list than necessary, and language optimized for defensibility rather than appeal. The candidates who persevere through that experience are either highly motivated (often because they are unemployed and have fewer options) or unusually high-tolerance. The passive candidates with good options who skim the first paragraph and leave are not captured in any metric that gets reviewed.

For staffing agencies presenting roles to candidates, the distinction is operationally important. A recruiter briefing a candidate on a role is delivering a posting, not a job description. The briefing should lead with why the role is compelling, what the work actually involves day-to-day, what success looks like, and what the candidate needs to decide. Reading the job description to the candidate is not a briefing; it is a waste of the candidate's time and the recruiter's credibility.

Maintaining the distinction also improves legal hygiene. A job posting that accurately represents the actual role (not a padded job description with aspirational requirements) is less likely to generate discrimination claims from rejected candidates. If the posting says "must have a master's degree" because that language was in the job description from 2015 and no one removed it, and the company has been hiring candidates without master's degrees for that role for five years, there is a defensibility problem.

In Practice

A technology company reviews its application funnel for 28 open software engineering roles. The average posting is 687 words, requires a degree and 8 years of experience, and receives an average of 14 applications per posting over 30 days, of which 3 advance to the phone screen. A copywriter with recruiting context rewrites 14 of those postings specifically as job postings rather than job descriptions: 350 words, written in second person, leading with the tech stack and team size, including a salary range, and listing 5 clear qualifications rather than 12 padded ones. Over the next 30 days, those 14 rewritten postings average 31 applications each, with 8 advancing to the phone screen. The other 14 unchanged postings show no change. The company rolls out the revised format to all postings.

Key Facts