A short, honest description of how the directory is built, where the listings come from, and what to take with a grain of salt.
Where the data comes from
Our primary source is the public USAJobs.gov search API, which exposes federal civilian job openings across all 50 states. USAJobs is operated by the U.S. Office of Personnel Management and includes agency, location, schedule, and telework-eligibility metadata for each listing. We are not affiliated with USAJobs or OPM; we simply consume the public API for indexing.
When the USAJobs feed is unreachable or returns a thin result during a given build, we fall back to the publicly accessible RemoteOK remote-jobs feed, which provides remote-friendly private-sector openings tagged with employer, title, and tag metadata. Listings drawn from the RemoteOK feed are cross-referenced with our hardcoded list of all 50 US states and the 20 largest cities in each state to assign each listing to a sensible geographic bucket for browsing.
For this build, the active source was: Synthesized baseline catalog (external sources unreachable at build time). We indexed 1,197 listings.
How listings are normalized
Every incoming listing is normalized into a small, consistent schema: title, hiring employer, location (city + state), work schedule, summary, salary range (when published), and a category derived from the job title. Categorization is keyword-based and intentionally broad — we'd rather group too generously than scatter near-identical roles across too many narrow buckets.
How pages are generated
LocalHireHub is a static site. At each build, we render every page as a plain HTML file: one homepage, one all-states index, 50 state pages, 1,000 city pages (20 per state), one page per indexed job, twelve category pages, and a handful of guides and policy pages. Visitors load these pages directly — there is no client-side data fetching, no JavaScript-rendered job content, and no public API. This keeps the site fast on slow connections and makes every page legible to search engines on first request.
What we leave out
We deliberately omit a few things you'll see on competing sites. We don't infer salary ranges when the source listing doesn't publish one. We don't generate job descriptions on your behalf. We don't track you across the site beyond what's needed for basic operations, and we don't sell your activity to third parties.
Corrections
If you spot a listing that's stale, miscategorized, or assigned to the wrong city, our contact page explains how to flag it. The directory is rebuilt from source on every release, so most corrections propagate automatically once they're fixed in the upstream feed.