Job posting versus job description

A job description is the internal specification of a role: purpose, reporting line, must-have skills, and how you will judge success. A job posting is the advertisement — internal or public — that invites applications. They usually share a title. They do not share an audience, a tone, or a complete field list. Mixing them produces ads that read like org-chart footnotes and internal specs that read like slogans. This page is that distinction. Stage-by-stage hiring operations stay on the recruitment hiring checklist. Pipeline columns as candidate states stay on hiring pipeline stages. Product context is Dayzen recruitment.

Dayzen recruitment includes an internal job board and public application portals, and jobs you can create, edit, close, and archive. That is not a claim that Dayzen posts every opening to every external job marketplace. You may still copy a posting to a board you use; the HRMS job object is not that marketplace.

Same title, two documents

The title is the shared key so a candidate, a hiring manager, and payroll eventually mean the same opening. Under the title, the documents split.

The job description (JD) is for people who already work with the role: hiring manager, HR, compensation, and later the employee. It should be specific enough that you can screen against it and write an offer without inventing duties. Typical internal content:

• Why the role exists (outcome, not a stack of tools).
• Department, designation, grade or band if you use them, reporting manager.
• Employment type and location or roster pattern as you actually run them.
• Must-have skills versus skills you will train.
• Decision rights and collaborators (who this person will unblock).
• Success signals for the first six months, written as work, not as adjectives.
• Compensation band or CTC range the approver already accepted, if your policy stores that internally and not on the public ad.

The posting is for people who do not work there yet (or employees browsing an internal board). It should be readable on a phone, honest about location and type, and long enough to attract the right applications without pasting the entire JD. Typical posting content:

• Title and a short purpose paragraph in plain language.
• Location, remote or hybrid pattern, employment type.
• A short list of what the person will do, selected from the JD, not a new invention.
• A short list of what you need them to bring, aligned to the JD must-haves.
• How to apply (portal, internal board, or the process you actually honour).
• What you will not put on a public page if policy says so (exact CTC, internal grade, named client).

If you can delete the JD and still hire from the posting alone, your internal spec was never written. If you post the JD unchanged, you are advertising to strangers in intranet dialect.

Why teams glue them together

Speed: someone pastes last year’s JD into a careers page. Fear: legal or HR wants every public sentence to match the internal file. Vanity: founders want the ad to sound like a manifesto. All three produce the same operational mess. Screeners argue with a posting that promised “ownership of growth” while the JD listed inside-sales calls. Candidates arrive expecting the manifesto. Offer letters then invent a third title so payroll can code a designation.

The fix is not a longer posting. It is a rule: the JD is source for duties and must-haves; the posting is a derivative with a named owner who may shorten but not contradict. When the work changes, edit the JD first, then refresh the posting, then tell anyone already in Interview if the change is material.

Contradiction is the expensive failure, not tone

Tone can differ. Contradiction should not. Examples that should never happen:

• Posting says remote; JD says five days in a named office.
• Posting says three years’ experience; JD’s must-haves are impossible at three years.
• Posting says “competitive pay”; internal band is already approved and interviewers quote a different number.
• Posting title is “Account executive”; JD and offer designation is “Business development associate” with no mapping.

Interviewers should screen against the JD. Candidates should have applied against the posting. If those two documents disagree, every interview is an accidental negotiation. Align them before the job goes live on the internal board or public portal.

Where each document lives in a recruitment system

Create the job as an object you can edit, close, and archive. Attach or paste the JD as the internal spec (or link to the handbook section that owns it). Compose the posting as the text that appears on the internal job board and on public application portals you actually run. Applications then hang on that job. When you hire, close or archive the job so the posting stops collecting people you will not read. Leaving a live posting on a closed requisition is how you get a polite ghost-town of Applied cards.

Dayzen recruitment supports that job lifecycle and those two surfaces (internal board, public application portals). It does not, as a product claim, syndicate to every third-party job board. If you still use an external board, treat it as a copy of the posting you already approved — same title, same location, same must-haves — and point apply-links back to the portal that writes into your ATS. Multiple slightly different ads is how you get multiple slightly different candidate expectations.

Do not build a second “jobs” spreadsheet for public wording while the HRMS holds another title. That is spreadsheet hiring’s cousin. The tracker comparison is a sibling; here the point is one job object, two texts.

Internal board versus public portal — still postings, still not JDs

An internal posting can be shorter and can name the team more freely. It is still an ad to employees, not the JD. Do not assume employees have read the internal spec. Public portals need extra care on location, entity name, and what you collect on the form. Neither surface replaces the JD that compensation and the manager signed off.

If only executives may see CTC bands, keep bands on the JD (access-controlled) and keep the posting qualitative or ranged as policy allows. Do not hide a fake band on the posting that the JD contradicts.

What the hiring checklist and pipeline article still own

The checklist is how you open a requisition, source, screen, interview, offer, and hire — the ops steps. It is not a writing guide for JD versus ad. Do not expand that checklist with this distinction; link here when someone pastes the spec onto the careers page.

Pipeline stages are applied, screen, interview, offer, hired or rejected — states of an application, not project tasks. They assume a job exists. They do not tell you how to write the posting that created the application. Keep PMS (Project Management System) out of this; delivery boards are not job ads.

A practical split you can run in a small team

1. Hiring manager drafts or updates the JD (internal spec) and gets the band and headcount approval your policy requires.
2. TA or HR writes the posting from that JD: shorter, public-safe, same title and location facts.
3. A second pair of eyes checks for contradiction (especially location, type, and must-haves).
4. Create or edit the job in recruitment; publish to the internal board and/or public application portal you use.
5. Screen using the JD; quote the posting if a candidate’s expectation came from the ad.
6. When filled or cancelled, close or archive the job so both surfaces stop advertising.

If you have no TA, the same person may do steps 1 and 2. Still produce two artefacts. A single blob that tries to be both will be too vague for interviews and too dense for applicants.

Fields that belong on one side more than the other

Field	JD (internal)	Posting (ad)
Title	Yes — matches designation if you can	Yes — same title
Reporting line	Yes	Optional; team name is often enough
Must-have skills	Full, including what you will test	Short list; no secret extras
Success metrics	Yes	Usually truncated
CTC / band	As policy stores internally	Only if you choose to publish
How to apply	No	Yes
Legal entity / grade codes	Yes if payroll needs them	Usually no

Offer letters should follow the JD and the approved band, not a poetic line from the posting. Onboarding handoff then carries the internal role and CTC — a later seam, not this article’s job.

Close and archive are part of the distinction

A JD can remain in a library after the opening is filled; you may reuse it next year with a revision date. A posting should not remain live. Create, edit, close, archive on the job object so the ad dies with the requisition. Reusing a JD without refreshing the posting is how last year’s “hybrid, two days office” becomes this year’s accidental remote campaign.

Archive is not delete. You still want the job id on old applications. You do not want the public paragraph still generating Applied stages you will never screen.

Write the spec for insiders. Write the ad for applicants. Share the title and the facts that must not contradict. Use Dayzen’s internal board and public portals to publish the ad, and close the job when you stop hiring. Keep external marketplace syndication out of the product story. Keep the checklist on hiring steps and the pipeline article on candidate states. This page only exists so those two texts stop being one neglected document.