Why Posted Band
Public job postings contain more than openings. Over time, they reveal movement.
Posted Band preserves that movement while keeping source, time, uncertainty, and publication limits attached to every claim.
The name
“Posted” refers to information publicly disclosed in a job posting. “Band” refers to the salary band an employer chooses or is required to publish. Together, Posted Band describes the evidence itself rather than an estimated market salary.
The useful gap
Large salary databases already compete heavily on broad company-salary searches. Posted Band is not trying to rebuild that directory. Its primary wedge is the time-series view: how the number and composition of open roles change from one dated snapshot to the next.
Employer-posted salary evidence remains part of the same dataset, but it stays attributable to the original posting, currency, pay interval, location scope, and observation time.
The editorial standard
Version 1.0, reviewed Aug 7, 2026. These principles apply to public data pages, reports, machine-readable summaries, and corrections.
- 01
Evidence before reach
An indexed data page must contain a source-backed observation that a generic company profile does not; history-gated pages remain noindex until that evidence exists.
- 02
Observations, not inference
Advertised job counts describe public hiring demand signals, not completed hires, headcount growth, business performance, or employer motives.
- 03
Source and time stay attached
Published observations retain their named public ATS source, collection time, coverage window, and method boundary.
- 04
Exact comparisons only
Trend language requires real successful snapshots at both exact boundaries; missing dates are not interpolated and first-day unknowns are not written as zero.
- 05
Corrections preserve context
A material correction identifies the affected observation, preserves its original collection context, and updates or removes publication when the evidence no longer supports it.
The current stage
The static research and methodology layer reads from a reviewed artifact generated by local collection and publication tools. A configured source is not automatically a public historical dataset, and a current snapshot is not automatically a trend.
- verified source configurations
- 26
- companies in the reviewed artifact
- 12
- current advertised roles
- 2,069
- roles with posted salary evidence
- 1,132
Latest successful source observation: Aug 7, 2026. Company trend pages remain noindex until they pass the versioned history, freshness, activity, and exact-comparison gates.
Corrections and source review
Source identity, attribution, stale endpoints, derived counts, salary evidence, and publication eligibility are reviewed against stored source records and the versioned methodology.
Material errors update the affected static observation or remove it from publication while retaining the local audit trail.
This static build has no visitor submission channel, contact form, project email, or collection of correction-request identity. A public correction channel is a deployment-stage decision.
The public editorial-policy anchor is /about#editorial-principles.