Job Description vs Job Posting vs Job Specification: The Differences
A job description is an internal record of what a role involves, a job posting is the public advert built from it to attract applicants, and a job specification lists the skills, qualifications and traits a person needs to do it. One job description template can feed all three if you keep each document's purpose clear.
Why the three terms get mixed up
People use job description, job posting, job ad and job specification as if they were one thing, and in a small company that is mostly harmless. One person writes one document, pastes it on a careers page and calls it the job description. The trouble shows up later. The text that works as an internal record is too long and too dry to attract applicants. The text that works as an advert leaves out details your manager needs when they review performance. And a specification written as a list of qualifications, used on its own, tends to screen out capable people. Separating the three documents gives each a clear reader, a clear purpose and a sensible length. It also makes your hiring easier to scale, because you maintain one source of truth for the role and produce the others from it. This guide defines each document, compares them side by side, shows a worked example of one role turned into all three, and explains where a job description template or generator helps and where it does not. For role-specific starting points, see /job-description-template, and for how the documents feed the rest of the process, see /recruitment-software. Terms vary by country and company, so treat the definitions here as common usage, not law.
What a job description is
A job description is a structured record of a role. It says why the role exists, who it reports to, what the person does, what outcomes matter, and what the job needs in terms of skills and conditions. Its main readers are the hiring manager, HR or whoever handles employment paperwork, and the employee once hired. It is also the source document for later uses such as performance reviews, pay comparisons and internal moves. Because it is a record, it can be fuller and more formal than an advert. It should still be accurate and current, since an old description that no longer matches the work causes confusion in reviews and disputes. Typical sections are title, purpose, reporting line, key responsibilities, qualifications and skills, and working conditions. Some employers add a statement on physical requirements or travel. Whether a written description has any legal weight, and what it must contain, differs by country, so check local rules and take advice where the stakes are high. The description is the master version, and everything else should be traceable to it.
What a job posting is
A job posting, also called a job ad or vacancy, is a public message whose purpose is to get the right people to apply. Its readers are strangers who are comparing it with many others, usually on a phone, usually with little time. So it must open with what makes the role worth considering, state the essentials quickly, and make applying simple. A good posting includes the title, location and working arrangement, pay where you can share it, a short summary of the work, the handful of requirements that really gate the job, a few things that make the employer a fair place to work, the hiring process, and a clear way to apply. It leaves out internal detail, long lists of duties and anything that does not help a candidate decide. Because it is marketing as well as information, tone matters, but honesty matters more: a posting that promises what the job does not deliver produces drop-outs and early resignations. Postings also have a life on job boards and your own site, where search wording and layout affect who sees them. That is a separate craft from the internal record.
What a job specification is
A job specification, sometimes called a person specification, describes the person rather than the job. It lists the knowledge, skills, experience, qualifications and sometimes personal qualities that someone needs to perform the role well. It is usually divided into essential and desirable criteria. Its main use is to give the hiring team a shared yardstick, so that everyone screens and interviews against the same list and can explain why someone was or was not progressed. Used well, it is the most valuable of the three for fairness, because it turns a vague sense of fit into named criteria. Used badly, it becomes a list of credentials and years that excludes people who could do the work. Each essential criterion should be tied to a duty in the description and should be something you can assess from a CV, a test or an interview answer. Some organisations merge the specification into the description under a heading such as requirements. That is fine for a small team, as long as the essential items stay short and each can be evidenced.
The three documents side by side
The table summarises how they differ. Use it to decide which document you need at a given moment.
| Aspect | Job description | Job posting | Job specification |
|---|---|---|---|
| Main purpose | Record what the role is | Attract applicants | Define the person needed |
| Main readers | Manager, HR, the employee | Candidates | Hiring team |
| Where it lives | Internal files and HR records | Job boards and careers page | Screening and interview guides |
| Typical length | One to two pages | Short, often 300 to 600 words | Half a page to one page |
| Tone | Neutral and precise | Clear and persuasive but honest | Criteria-based |
| Update trigger | Role changes | Each vacancy | Each vacancy or role change |
Notice that the posting is the only one candidates normally see, and it is the shortest. A common mistake is to publish the full internal description as the advert, which buries the reason to apply under tasks. The opposite mistake is to write only an advert and then have no record to hold the new hire's performance against. Keep the master description, and cut a fresh posting from it each time you recruit, with updated pay, dates and process.
Worked example: one role, three documents
Take an invented example: a customer support lead at a twenty-person software company. Job description (extract): Purpose: make sure customers get accurate answers quickly and that recurring problems reach the product team. Reports to the head of operations. Responsibilities: manage a team of three agents, handle escalations, maintain the help centre, report monthly on response times and common issues. Skills: coaching, clear writing, comfort with support tools. Job posting (extract): Support Lead, hybrid, salary range stated. Our customers are small businesses who write to us when something blocks their work. You will lead three support agents, own escalations and make sure what we learn reaches the people building the product. You will need experience handling customer cases at volume, good written communication and some experience coaching others. Here is how we hire: a short call, a written exercise and a team meeting. Job specification (extract): Essential: two examples of resolving complex customer cases; clear written English shown in a sample; experience guiding a colleague. Desirable: help centre writing, reporting from support data. Notice the same facts are reused, but each document selects and shapes them for its reader.
How a template or generator helps with each
A job description template is most useful for the master record, because the structure is standard and the main work is filling it with true facts. A job description generator can draft sections quickly from a few inputs, which suits both the description and the first pass at a posting. For the specification, the better approach is to extract it from the description's requirements, then sort them into essential and desirable by asking whether you would reject a candidate for lacking each. Do not expect any tool to know your pay, location rules or hiring process, and review every generated line for claims you cannot support. Generated text also tends toward bland phrasing that makes all postings look alike, so add specifics that only you know. A practical workflow is to write the description once, generate or draft the posting from it, copy the essential requirements into a one-page specification for interviewers, and then review all three side by side for contradictions. Contradictions, such as a posting that asks for three years of experience while the specification says two, are a frequent source of confusion and complaints.
Score your set of documents
Use this checklist when you have all three drafts. Score each item 0 for no, 1 for partly, 2 for yes. A total of 14 or more out of 18 is good.
| Check | Score 0 to 2 |
|---|---|
| The description explains why the role exists | |
| The posting opens with a reason to apply, not a task list | |
| The posting states pay or a range where allowed | |
| Essential requirements are the same in all three documents | |
| Every essential item links to a duty | |
| Each essential item can be shown on a CV or in an interview | |
| The posting is short enough to read on a phone | |
| The description is dated and has an owner | |
| The process and timeline are stated for candidates |
If you score low on the third row, you probably have drift between documents. Fix it by editing the description first, then regenerating or rewriting the others from it, rather than patching each separately. Patching three files by hand is how contradictions return within a month.
Common mistakes
Teams most often publish the internal description as the advert, which makes it long and tells candidates little about why to apply. Another common error is writing an advert that makes promises the real description does not support, such as autonomy or flexibility. A third is treating the specification as a credentials list, with degree and years of experience, rather than evidence of capability. A fourth is letting the three documents drift apart after the posting is edited in a job board and nobody updates the master. A fifth is using the same posting for months after the role has changed. A sixth is copying a competitor's posting, including its requirements, and thereby committing to a standard you did not choose. A seventh is leaving out pay, which makes your advert less useful than others on the same search. Last, some teams skip the specification entirely and then discover that interviewers are using personal checklists that conflict. A shared half page fixes this, and it is also the evidence you will want if a decision is ever questioned.
Where Rezumz fits
Rezumz is an AI hiring workspace for small and mid-size hiring teams. In terms of the three documents, it works mainly with the description and the specification: you paste the job description when you create a job, Rezumz lists the must-have and nice-to-have skills it found so you can check them, and CVs are scored against that list. The JD Enhancer at /jd-enhancer can tighten a draft first, and it is decision support that you review. Rezumz does not publish postings to job boards with one click, and it is not an HRIS for storing employment contracts or payroll. It suits small and mid-size teams, with the Team plan for four or more recruiters, and it does not suit large enterprises needing deep HRIS or payroll integrations. Prices: free plan with 2 free candidate analyses; $29 a month, $199 a year or $499 lifetime (limited); Team is $79 a month or $699 a year for up to 10 teammates. See /demo for the live demo, /pricing for plans and /applicant-tracking-system for the wider picture.
When you do not need all three
You do not always need three separate documents. For a one-off hire in a very small team, a single page that works as the description and a short posting cut from it may be enough, with the essential requirements kept in one list for interviewers. If you hire only occasionally, the cost of maintaining a master record may exceed the benefit, so write a clean description at the time of hire and keep it with the employee file. If your country or sector requires specific wording in adverts or contracts, such as pay disclosure or equal opportunity statements, follow local rules, which differ and change, and take advice rather than relying on a template. And if you are hiring through an agency, ask what they will produce so you do not pay for duplicated work. Use as many documents as give each reader what they need and no more.
Frequently asked questions
What is the difference between a job description and a job posting?
A job description is an internal record of what the role involves, who it reports to and what skills it needs. A job posting is the shorter public advert built from it to attract applicants. The posting should open with a reason to apply, state pay and process, and omit internal detail.
What is a job specification?
A job specification, or person specification, lists the knowledge, skills, experience and qualities someone needs to do the role. It is usually split into essential and desirable criteria and gives interviewers one shared yardstick. Each essential item should link to a duty and be something you can assess.
Can I use one document for all three?
In a very small team you can, if you keep a master description and cut a shorter posting from it, with essential requirements listed for interviewers. Publishing the full internal description as the advert usually performs worse because it is long and buries the reason to apply.
Can a job description generator write a job posting?
It can draft one from your description, but it will not know your pay, location rules or hiring process, and its wording tends to be generic. Supply the essentials, then edit for honesty and specifics. Check any legal wording against local rules, which differ by country.
How often should each document be updated?
Update the description whenever the role materially changes, and review it at least yearly. Refresh the posting every time you recruit, with current pay, dates and process. Revisit the specification for each vacancy so that essential criteria still match the real duties.