How a Job Posting Gets Written and Approved

A job posting is not a neutral description of work. It is a document produced by a sequence of internal decisions — about budget, team structure, legal compliance, and recruitment strategy — before a single candidate ever reads it. The language that appears in a public listing is the residue of that process, not a direct transcription of what a hiring manager originally wanted.

This piece covers the machinery of how a posting moves from an internal headcount request to a live listing on a job board. It does not cover what happens after a candidate applies; it covers what happens before the role is ever visible. Understanding that sequence explains why postings are often vague, why they change mid-cycle, and why the published text sometimes diverges from what interviewers actually ask about.

From Headcount Request to Published Listing: The Drafting Sequence

The process typically begins not with a recruiter but with a manager identifying a staffing need. That need is expressed as a headcount request — a formal or informal proposal to add or backfill a role. In larger organizations, headcount requests pass through workforce planning cycles, often tied to budget periods. Finance and senior leadership review the request against headcount targets before any drafting begins. A role that is not yet approved in the budget cannot be posted, and in many organizations the approval chain is long enough that months pass between the original need and the live listing.

Once headcount is approved, a hiring manager typically produces a rough job description. This document is internal and informal: it describes the work as the manager understands it, often using team-specific language, internal tool names, and competency language drawn from performance reviews. This draft is rarely suitable for public posting without revision.

A recruiter or HR business partner then translates the internal draft into a standardized posting format. This step involves several changes: internal jargon is replaced with searchable market terminology, required qualifications are separated from preferred ones, and the role is mapped to a job family or level within the organization's compensation structure. The salary range — if one is published — is set during this stage based on internal compensation bands and market data. How that range is constructed is a distinct mechanism; the internal logic behind it determines what gets published, or whether a range appears at all.

After the recruiter drafts the posting, it typically moves through a legal or compliance review. This step checks for language that could expose the organization to discrimination claims under federal equal employment opportunity statutes. Phrases that imply age preferences, physical requirements not tied to genuine job duties, or degree requirements that cannot be justified by business necessity are flagged and removed or revised. The Equal Employment Opportunity Commission enforces these standards, and large employers are particularly attentive to this review stage.

Some organizations require a second approval from a department head or a talent acquisition manager before the posting goes live. Once all approvals are collected, the posting is published — typically to the organization's own career site first, then distributed to one or more job boards. Once live, how a job board ranks and surfaces that listing becomes its own separate system, outside the employer's direct control.

Who Touches a Posting Before It Goes Live

The hiring manager originates the need and produces the first rough description. This person understands the actual work but typically has limited knowledge of external labor market language, compensation benchmarking, or compliance requirements. Their draft sets the intent of the role; subsequent steps shape how that intent is expressed.

The recruiter or HR business partner is the primary translator. This role bridges the hiring manager's internal language and the external labor market. Recruiters apply knowledge of how candidates search for roles, what terminology is common in the relevant field, and what the organization's standard job levels look like. They also manage the approval workflow and track the posting through each stage.

Finance and workforce planning control headcount approval. Without their sign-off, no posting is created. In organizations with strict headcount controls, this function can delay or block a posting entirely, even after a manager has identified a genuine need.

Legal or compliance reviewers examine the draft for language that creates legal exposure. This is not a creative role; it is a gatekeeping function. The output of this review is typically a list of edits, not a rewrite. Reviewers apply federal and state employment law standards, including those enforced by the EEOC and the Department of Labor.

The applicant tracking system receives the approved posting and structures it for distribution. The ATS stores the posting, assigns it an identifier, and routes incoming applications against it. The way the posting is structured within the ATS also affects how the system later parses resumes submitted in response — the fields defined in the posting often become the matching criteria applied to incoming applications.

Job boards and aggregators receive the posting via direct integration or feed. They are passive recipients at the distribution stage, though their own ranking algorithms determine how prominently the listing appears to searchers.

Where the Drafting Process Breaks Down

One of the most common failure points is the gap between what the hiring manager describes and what the recruiter publishes. When a manager uses internal terminology that has no direct external equivalent, the recruiter must substitute market language — and that substitution may not accurately represent the work. A posting for a "senior analyst" may describe duties that the external market would classify as a manager-level role, or vice versa. The mismatch is invisible in the listing and only becomes apparent during interviews.

Credential inflation is a related distortion. Degree requirements, years-of-experience minimums, and lists of required tools often reflect what the hiring manager ideally wants rather than what the role genuinely requires. Research from the Department of Labor has documented persistent patterns of degree requirements appearing in postings for roles where the actual work does not require a degree. This language survives the drafting process because legal review focuses on discrimination risk, not on whether requirements are operationally justified.

Postings are also frequently written for roles that are not fully defined. When a team is growing quickly or a new function is being created, the hiring manager may not yet know precisely what the role will require. The posting is written based on an approximation, and the actual job duties are refined during the search — sometimes after interviews have already begun. Candidates who apply based on the original posting may encounter a different set of expectations by the time they reach later stages.

Approval delays create a separate class of problems. A posting that takes three months to clear finance, legal, and department approvals may describe a role whose requirements have already changed. The team may have reorganized, the budget may have shifted, or the manager who originated the request may have left. The posting goes live as written, but the underlying need it was meant to address has evolved.

Finally, the salary range — when published — may not reflect what the organization is actually willing to pay. Ranges are set during the drafting stage based on compensation bands, but those bands are sometimes wide, and the actual offer will depend on factors not visible in the posting. How a salary range is set internally is a distinct process that the posting text only partially reflects.

What the Posting as a Document Actually Shows — and What It Does Not

The published posting is a snapshot of an internal agreement reached at a specific point in time. It records the job title the organization has assigned to the role, the approved qualifications as of the drafting date, the reporting structure if disclosed, and the location or remote status. In jurisdictions with pay transparency laws, it also records a salary range. These elements are what the document affirmatively contains.

The posting does not record the internal deliberations that produced it. It does not show which qualifications were added by the hiring manager, which were added by the recruiter for searchability, and which survived legal review unchanged. It does not show whether the role was a backfill for a departed employee, a newly created position, or a role that had been approved and then frozen in a prior budget cycle. It does not show how many candidates the organization expects to interview, what the internal timeline is, or whether a preferred candidate has already been identified through referral or internal sourcing.

The posting also does not bind the organization to the terms it describes. Job duties, reporting relationships, and even titles can change between the posting date and an offer. The offer letter — a separate document created later in the process — is the record that captures what was actually agreed. The posting is an invitation to apply, not a contractual commitment, and its contents are not enforceable in the way that a signed offer letter may be.

Applicant tracking systems log the posting's metadata — when it was created, when it was published, when it was closed — but that log is internal to the employer and not visible to applicants. What applicants see is the rendered text; what the ATS stores is a structured record with fields, tags, and timestamps that drive the matching and screening process downstream.

A job posting is the public output of a process that is almost entirely internal and largely invisible to the people who read it. The language in the listing reflects budget approvals, compliance reviews, and translation decisions as much as it reflects the actual work — which is why the posting and the job often turn out to be slightly different things.

Note: This explains how hiring works as a system. It is not career coaching or legal advice, and it is not a substitute for a career professional or employment attorney. Check the cited sources for current labor-market and employment-law data.