Job Description vs Job PostingTwo documents, two jobs, one common mix-up
Most hiring teams use the words interchangeably, then wonder why their careers page reads like an insurance policy. A job description and a job posting are not the same thing. One is an internal record. The other is a public ad. Confusing them costs you applications and, in a growing number of states, exposes you to compliance risk.
Same role, two documents, two jobs to do
Job Description
Internal HR document
- Defines duties, requirements, reporting line
- Third-person, formal, exhaustive
- Lives in your HR system year-round
- Used for comp, leveling, ADA, disputes
- Audience: HR, managers, legal
Job Posting
External advertisement
- Sells the role and the company
- Second-person, punchy, selective
- Lives on job boards while the req is open
- Used to attract and convert applicants
- Audience: candidates
Here is the one-line version. A job description defines the role. A job posting advertises it. The description answers "what is this job and who is accountable for what," and it exists in your files whether or not you are actively hiring. The posting answers "why should a great person apply here," and it only exists while a requisition is open.
The reason this matters is money and time. A weak posting that reads like a copied description gets ignored. According to LinkedIn Talent Solutions research, job posts with clear, scannable structure and a stated salary draw meaningfully more qualified applicants than dense, jargon-heavy ones. Meanwhile a missing or sloppy description creates a different problem later, when a manager wants to fire, promote, or accommodate someone and there is no written record of what the job required.
I have watched teams spend a full week arguing about a candidate who never belonged in the funnel, all because the posting was vague and the description did not exist. Getting these two documents right is boring work that quietly fixes half of your pipeline problems. If you want the upstream step, our guide on the job requisition form covers how a role gets approved before either document is written.
The internal document
What a job description actually is
A job description is the formal record of a role. It documents the title and level, the reporting line, the department, the essential functions of the job, the required and preferred qualifications, working conditions, and the internal pay band. It reads like a specification because that is what it is. The audience is HR, hiring managers, compensation planners, and, if things ever go wrong, lawyers.
The part people underrate is the phrase "essential functions." The EEOC guidance under the Americans with Disabilities Act leans on written job descriptions when an employer evaluates a reasonable accommodation request. If your description clearly lists which functions are essential and which are marginal, you have a defensible basis for hiring decisions. If it does not exist, you are arguing from memory. That is a bad place to be.
A description also drives internal consistency. When every "Senior Product Manager" role in the company maps to the same documented scope and pay band, leveling stays fair and comp stays sane. Break that link and you get pay compression, title inflation, and the awkward conversation where two people doing the same work discover they are paid very differently. The SHRM guide to developing job descriptions is a solid reference for the standard sections.
The public ad
What a job posting actually is
A job posting is marketing. It is the version of the role that goes on Indeed, LinkedIn, a niche board, or your own careers page, and its only job is to make the right person stop scrolling and hit apply. It is shorter than the description, written in the second person, and built around what the candidate gets, not just what the company demands.
Good postings share a shape. They open with a hook about the mission and the impact of the role. They describe the actual day-to-day in plain language. They list the handful of requirements that genuinely gate the job, usually 5 to 7, not the 15-item wishlist that scared off half your qualified applicants. They state the salary range. They close with the culture, the perks that matter, and a clear call to apply.
The distribution channel shapes the copy too. A posting on a general board competes with thousands of others, so the first two lines carry the weight. A posting on a specialist board can assume more context and get technical faster. If you are choosing where to advertise, our roundup of niche job boards and the Indeed for employers guide both cover how channel changes the way you write.
Side by side, section by section
The two documents overlap on the facts of the role and diverge on everything else. The description keeps the compliance and comp material a candidate never needs to see. The posting keeps the persuasion a compliance file has no use for. Here is what lands in each.
What actually goes in each one
Description contains
Posting contains
Notice that the internal pay band and the public salary range are related but not identical. The band might run from $120k to $165k across the whole level. The posting might advertise $130k to $150k, the slice you actually expect to pay for this specific hire. Keeping the band internal and the range public is deliberate, not sloppy.
The distinctions that matter
Six differences worth remembering
Purpose
The description documents accountability and pay. The posting attracts applicants. One is a record, the other is a pitch.
Audience
The description is read by HR, managers, and legal. The posting is read by candidates who will decide in about ten seconds whether to keep reading.
Voice
The description is third person and formal: 'The role is responsible for.' The posting is second person and direct: 'You'll own.'
Length and detail
The description is exhaustive because completeness protects you. The posting is selective because every extra requirement shrinks your applicant pool.
Lifespan
The description lives in your HR system indefinitely and gets updated as the role evolves. The posting goes live when the req opens and comes down when it closes.
Compliance weight
The description carries ADA and EEO significance. The posting carries pay transparency obligations. Different laws touch each document.
Where the law shows up
Salary, EEO, and the compliance line
This is the part that has changed the most in the last few years, and it is where teams get caught. Pay transparency laws have spread fast. California, Colorado, New York, Washington, and a growing set of cities now require employers to include a good-faith salary range in the job posting itself, not just in an internal file the candidate never sees. If you post a role that reaches applicants in those jurisdictions and leave the range out, you are exposed.
The internal description is where you keep the full pay band and the reasoning behind it. The public posting is where you show the range you are willing to advertise. Both need to be honest and consistent with each other, because a candidate who is offered less than the posted range has a real complaint, and in transparency states, a legal one.
EEO language works the opposite way. Your equal opportunity statement and any required accommodation notice belong in the public posting so every applicant sees them. The essential-functions detail that the EEOC cares about lives in the description. If you want to be sure your criteria are job-related and consistently applied, pair a tight description with a structured interview process so the whole chain lines up.
Turn a clean job description into a posting that converts
Prepzo helps you draft the internal spec, generate a candidate-ready posting from it, and publish to your careers page without copy-paste chaos.
Try Prepzo freeThe practical workflow
How to turn a description into a posting
The order matters. You write the description first because you cannot advertise a role you have not defined. Then you translate it into an ad. Skipping the description and writing the posting straight from a vague idea is how you end up with a funnel full of people who do not fit.
The description feeds the posting, not the other way around
Draft description
Manager defines the real work
Trim to essentials
Cut nice-to-haves and jargon
Rewrite as an ad
Second person, lead with pay
Publish and track
Post, then measure apply rate
Start with the finished description. Strip the internal-only material: the reporting hierarchy, the full pay band, the working-conditions boilerplate, and any HR codes. Take the requirement list and be honest about which items truly gate the role. A "10 years of experience" line that you would happily waive for a strong candidate is not a requirement, it is a filter that removes good people. Cut it or soften it.
Now rewrite what remains in the second person. "The candidate will manage a team of five" becomes "You'll lead a team of five engineers shipping our billing platform." Lead with the mission and the salary range, because those two things decide whether a strong candidate reads the rest. Keep the whole posting scannable with short paragraphs and clear headers.
Then publish and measure. If your apply rate is low, the posting is usually too long or too demanding, not the market. For the full craft of writing the ad itself, our guide on how to write job descriptions that work walks through the copy line by line, and the hiring plan guide covers how the role fits your broader headcount strategy.
What goes wrong
Common mistakes that blur the two
Posting the raw description
The most frequent one. A copy-pasted description reads like a contract, buries the salary, and lists every duty as equally important. Candidates skim and bounce.
Skipping the description entirely
Writing a posting with no underlying record means no ADA paper trail, no comp band, and no leveling consistency. It saves ten minutes now and costs you in an audit or a dispute later.
Hiding the salary
Leaving the range out of the posting suppresses applications and, in transparency states, breaks the law. The internal band stays private, the public range does not.
Requirement inflation
A wishlist of 15 must-haves in the posting is really a description that never got trimmed. Every extra line quietly filters out good people, especially those who self-select out.
Frequently Asked Questions
Is a job description the same as a job posting?
No. A job description is an internal document that defines the role's duties, requirements, reporting line, and pay range. It exists whether or not you are hiring. A job posting is the external advertisement you publish on a job board or your careers page to attract applicants. The posting is built from the description, but it is written to sell the role, not just document it.
Do I legally need a job description?
Federal law does not require one, but you want one anyway. Under the ADA, a written job description that lists essential functions is strong evidence when you evaluate reasonable accommodation requests or defend a hiring decision. The EEOC treats consistent, job-related criteria as the baseline for fair selection. A good description is your paper trail.
Should salary go in the job description or the job posting?
Both, but for different reasons. The description records the internal pay band for compensation planning and equity. The posting shows the range publicly because a growing list of states and cities now require pay transparency in the ad itself. If you hire in California, Colorado, New York, or Washington, leaving the range out of the posting is a compliance risk.
Can I just copy my job description into a job posting?
You can, and it is one of the most common mistakes I see. A pasted description reads like a legal memo: dense duty lists, third-person voice, and internal jargon. Candidates skim, do not see themselves in it, and move on. Rewrite it into second person, lead with the mission and the pay, cut the boilerplate, and keep it to the 5 to 7 requirements that actually gate the role.
Who writes the job description versus the job posting?
The hiring manager usually owns the job description because they know the actual work. Recruiting or HR owns the job posting because they know what converts on a job board. In practice the description gets drafted in a kickoff, HR turns it into the posting, and both parties sign off before it goes live. Keeping the two roles separate is why the documents stay distinct.
Resources & Further Reading
Related Guides
- How to Write Job Descriptions That Actually Work
Turn the internal spec into copy that converts
- Job Requisition Form: What to Include and Why
The approval step that comes before either document
- Niche Job Boards: Where to Post for Better Candidates
Channel changes how you write the posting
- Indeed for Employers: The Complete Guide
Publishing and optimizing a high-volume posting
External Sources
- SHRM: How to Develop Job Descriptions
Standard sections and formatting for the internal doc
- EEOC: ADA and Essential Functions
Why written descriptions matter for compliance
- LinkedIn Talent Solutions: Hiring Resources
What drives applications on job postings
- BLS: Occupational Outlook Handbook
Reference for role duties and typical qualifications
