How Job Postings Get Written and Approved

A job posting is the public face of a hiring decision that has already moved through several internal stages. By the time a listing appears on a job board, it has typically been shaped by at least one hiring manager, a human resources team, a compensation analyst, and sometimes a legal reviewer. The words a candidate reads are rarely the first draft of anything.

This piece covers the machinery behind that process — how a role gets scoped, how the posting language is assembled, and what approvals must clear before the listing goes live. The process varies considerably by organization size, industry, and the seniority of the open role, but the structural steps follow a recognizable pattern across most formal hiring pipelines.

From Headcount Request to Published Listing: The Steps in Order

The process begins before any writing occurs. A hiring manager identifies a staffing need — a backfill for a departing employee, a new role created by a budget expansion, or a project-driven addition to a team. That need is formalized as a headcount request, sometimes called a requisition or "req." The request is routed to finance or a budget owner for approval, because most organizations tie open roles to approved headcount in their operating plan. A role that has not cleared this gate does not move forward, regardless of how urgent the manager considers the need.

Once headcount is approved, the hiring manager typically completes a job intake form or meets with an HR business partner to define the role. This intake process captures the core responsibilities, the reporting structure, the required and preferred qualifications, and the target compensation range. The compensation range is not set arbitrarily — it is usually anchored to an internal pay band or grade that the compensation team maintains, often benchmarked against external survey data published by labor market research organizations.

With the intake complete, an HR generalist, recruiter, or talent acquisition specialist drafts the posting. The draft draws on the intake information but is also filtered through a set of organizational constraints: equal employment opportunity language requirements, job title conventions that match the internal grade structure, and sometimes a legal review to ensure no language creates unintended obligations or exclusions. The Equal Employment Opportunity Commission's guidelines on job advertising affect what qualifications can be listed as requirements versus preferences, particularly where certain criteria could screen out protected classes disproportionately.

The draft then circulates for approval. In smaller organizations this may be a single sign-off from the hiring manager. In larger ones, the chain can include the HR business partner, a compensation analyst confirming the posted range matches the approved band, a legal or compliance reviewer, and the hiring manager's own manager. Each reviewer may request revisions, which can extend the timeline by days or weeks. Only after all approvals are collected does the posting move to publication.

Publication itself involves a separate set of decisions: which internal systems get the listing first (many organizations post internally for a required period before opening the role externally), which external channels receive it, and whether the compensation range is displayed. Salary transparency laws in a growing number of jurisdictions now require that ranges appear in the posting itself, which has added a compliance checkpoint to what was previously a discretionary choice. Once the listing is live, how job board algorithms rank it against competing postings determines how much organic visibility it receives.

Who Touches a Posting Before It Goes Live

The hiring manager initiates the process and owns the definition of the role. This person determines what the job actually requires day to day, which qualifications are genuinely necessary, and what success in the role looks like. Their input drives the substance of the posting, but they rarely control its final language.

The HR business partner or talent acquisition team translates the manager's intake into compliant, structured posting language. This team also manages the approval workflow and is typically the party that loads the finalized posting into the organization's applicant tracking system and distributes it to external channels. When a recruiter later scans incoming applications, the framing they use to evaluate candidates traces back directly to the language this team produced.

The compensation and total rewards team validates that the posted salary range — where one appears — matches the approved internal pay band. This team's involvement is why a posting sometimes lists a range that feels broad: the band is designed to accommodate multiple levels of experience within a single job title, and the organization may not have decided in advance exactly where a hire will land within it.

Legal and compliance reviewers check the posting for language that could create liability. This includes ensuring that stated requirements do not constitute unlawful discrimination under Title VII of the Civil Rights Act, the Americans with Disabilities Act, the Age Discrimination in Employment Act, or applicable state laws. The EEOC enforces these provisions and publishes guidance that HR teams use as a reference when drafting qualification language.

Finance and budget owners sit at the beginning of the chain, not the end. Their approval of the headcount request is a prerequisite for everything that follows. In organizations with hiring freezes or mid-year budget cuts, approved requisitions can be paused or cancelled at this level even after the posting has been drafted.

Where the Posting Process Breaks Down or Misleads

The most common source of friction is misalignment between what the hiring manager wants and what the posting actually says. Because the intake form is a compression of a complex role, and because the HR drafter may not have deep familiarity with the technical domain, the published posting can omit critical responsibilities or overstate requirements. A role that genuinely requires three years of experience may list five because the manager copied language from a previous posting without revisiting whether it still fit.

Compensation ranges present a related problem. When a range is displayed, it reflects the full band approved for the role — not necessarily the range the organization intends to pay a new hire. The lower bound of a posted range may be reserved for internal transfers or promotions, while external candidates are evaluated against the midpoint or above. This gap between the posted range and the operating range is not disclosed in the listing itself. The eventual offer letter creates the formal record of what was actually agreed, which may differ from what the posting implied.

Postings also sometimes remain live after a role has been filled, paused, or cancelled. An applicant tracking system does not automatically close a listing when a hire is made informally; someone must manually update the status. In organizations with limited administrative capacity, listings can persist for weeks or months past their actual relevance. Conversely, a posting may be pulled before a hire is made simply because the approved headcount was reallocated — leaving candidates mid-process with no explanation.

The internal posting period creates another layer of opacity. Many organizations are required by policy or collective bargaining agreement to post roles internally before opening them externally. An external candidate applying on day one of a public listing may be competing against an internal candidate who has already had a week of visibility and informal conversations with the hiring manager. The external posting gives no indication that this internal process has already begun.

Finally, the "how to get a job referral" question intersects directly with the posting process in a structural way: many organizations have an employee referral program that operates in parallel with the posted listing. A referred candidate may enter the applicant tracking system through a separate queue that surfaces their application to the recruiter ahead of the general pool — not because of any rule violation, but because the referral program is designed to do exactly that. The posting itself contains no signal that this parallel channel exists.

What the Posting and Its Approval Trail Actually Document

The approved job posting, together with the requisition and intake documentation, forms part of the hiring record that organizations are required to retain under federal recordkeeping rules. The Equal Employment Opportunity Commission requires that employers preserve records relevant to hiring decisions, including job postings, for at least one year from the date of the posting or the date of the personnel action, whichever is later. For federal contractors, the Office of Federal Contract Compliance Programs imposes additional retention requirements.

What the posting record shows: the job title, the stated qualifications, the compensation range if one was disclosed, the date the listing was opened and closed, and the approval chain. In litigation or an EEOC investigation, this record can be used to assess whether the stated requirements were applied consistently across all applicants, or whether they were adjusted mid-process in ways that disadvantaged a protected group.

What the posting record does not show: the informal conversations that shaped the role before the intake form was completed, the internal candidates who were considered before the external listing went live, the manager's unstated preferences, or the budget constraints that determined the compensation ceiling. It also does not capture subsequent changes to the role's scope that occurred after the posting was written — a common occurrence in fast-moving organizations where a team's needs evolve faster than the formal process can track.

The applicant tracking system log will record when each application was received, how it was dispositioned, and sometimes a reason code for rejection. But the log reflects the categories the system was configured to capture, not the full texture of recruiter judgment. When a recruiter later reviews a résumé, that evaluation happens in a context set by the posting's language — a dynamic described in more detail in how recruiters scan a résumé in seconds against the criteria the posting established.

A job posting is a compressed, approved artifact that emerges from a process most candidates never see. Its language reflects budget decisions, legal constraints, internal grade structures, and the compression of a complex role into a standard form — not simply what the hiring manager would say if asked to describe the job in conversation.

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.