usajobs-scraping / README.md
abigailhaddad's picture
162,030 announcements, 2026
7257512 verified
|
Raw
History Blame Contribute Delete
3.95 kB
metadata
license: cc0-1.0
task_categories:
  - text-classification
  - feature-extraction
language:
  - en
tags:
  - usajobs
  - federal-hiring
  - government
pretty_name: USAJOBS Announcements 2026
size_categories:
  - 100K<n<1M
configs:
  - config_name: default
    data_files: data/*.parquet

USAJOBS announcements, 2026

The full text of every federal job announcement opened in 2026, scraped from usajobs.gov. 162,030 announcements, updated daily.

Why this exists

The USAJOBS API is a poor source for announcement text, in two ways.

The Search API only lists jobs that are open right now, so anything that opens and closes between two collection runs is never captured. Measured against the Historical API, which does report closed postings, that's about 3% of 2026 — 5,274 announcements — and it isn't spread evenly. OPM had text for 159 of its 724 postings. SSA for 200 of 422.

For postings the API does return, MatchedObjectDescriptor drops content the announcement page shows. Confirmed cases exist where the page says "Rule of Many" and the API record does not.

Neither gap can be backfilled from the API afterward: the Historical API returns metadata only, and Search only returns open jobs. So this scrapes the page, which usajobs.gov serves indefinitely after an announcement closes.

What's in it

One parquet file per month under data/, one row per announcement. Self contained — you don't need any other source to use it.

The scraped column:

column
text the announcement page as plain text, tags stripped and whitespace collapsed

Everything else comes from the USAJOBS Historical API: usajobsControlNumber, announcementNumber, hiringAgencyCode, hiringAgencyName, hiringDepartmentCode, hiringDepartmentName, agencyLevel, agencyLevelSort, appointmentType, workSchedule, serviceType, whoMayApply, payScale, salaryType, minimumSalary, maximumSalary, minimumGrade, maximumGrade, promotionPotential, supervisoryStatus, totalOpenings, positionOpeningStatus, announcementClosingTypeCode, announcementClosingTypeDescription, positionOpenDate, positionCloseDate, positionExpireDate, travelRequirement, teleworkEligible, relocationExpensesReimbursed, securityClearanceRequired, securityClearance, drugTestRequired, disableApplyOnline, vendor, hiringPaths, jobCategories, positionLocations, and occupationalSeries (the four-digit series pulled out of jobCategories).

hiringPaths, jobCategories, and positionLocations are JSON strings, since one posting can carry several of each.

How it's built

The posting list comes from the USAJOBS Historical API, mirrored by usajobs_historical, which reports closed announcements and is therefore the complete universe. Each usajobs.gov/job/{controlNumber} page is fetched, script/style stripped, and the remaining text collapsed to single spaces. The structured fields are joined on usajobsControlNumber from the same Historical API.

A daily job scrapes whatever is in the Historical mirror and not yet here, and re-joins metadata for the months it touches. Close dates and opening status change after a posting first appears, so a monthly job refreshes every month's metadata.

Caveats

The text is the rendered page, so it includes site chrome — the nav bar, the footer, the cookie language. Anchor your searches accordingly.

A handful of announcements are agency test postings with placeholder content ("There will be duties to perform for this position").

Announcements can be amended after posting. Each page is fetched once, so the text is whatever it said when scraped, not necessarily the final version. The structured fields are refreshed on a schedule, the text isn't.

This is not an official USAJOBS project.

License

Work of the U.S. federal government, not subject to copyright.