How these figures are counted.

Where the data comes from

Every listing is drawn from the USAJOBS Search API, published by the U.S. Office of Personnel Management. The register was last read on 29 September 2026 at 1:13 a.m. Eastern. Job titles, pay ranges, grades, closing dates and locations are reproduced as OPM publishes them. Where this desk and the announcement disagree, the announcement is right. USAJOBS data are a work of the United States government and not subject to copyright (17 U.S.C. §105); they are read through the Search API under the terms of use it publishes at developer.usajobs.gov.

Why the national total is not 10,000

Asked for every open position at once, the API answers 10000 exactly. That is a paging cap, not a count: in this read the fourteen largest states alone advertise 14,447, the largest, California, 1,531. So the register is gathered in pieces small enough to count, and the national figure is the number of distinct announcements actually held: 12,705 open, of the 13,151 read.

Why the register is gathered four ways

Reading it one state at a time is not enough, and the way that fails is quiet: a fully remote announcement is filed at Anywhere in the U.S. (remote job) with no state at all, so no query for a state can return it. So the harvest asks four times over, one query per value on each of four axes — the location (every state and territory), the hiring path, the organization and the position offering type — and merges the answers by announcement id. Each axis reports how many announcements it saw first: in this read location 12,677, hiring path 474, organization 0, position offering type 0. One value could not be enumerated at all: PositionOfferingTypeCode=15317 answered exactly 10,000, the cap, which is why no single axis is trusted alone. A new hole shows up as a later axis suddenly seeing announcements first. The announcements with no fixed place are listed at Remote.

What “jobs in this town” means

USAJOBS publishes two quite different things through one feed. Most announcements name one or two real places. A few hundred are nationwide public notices, open to applicants almost anywhere: 550 of them in this read, between them 72,208 location mentions, one naming 1,143 separate places.

Counted together, they distort every place page. Phoenix would read as 498 open positions when 424 of those are blanket notices that merely accept applicants from Phoenix; 74 are based there. New Haven, Connecticut, has no position based there at all in this read, yet 64 nationwide notices name it: counted together, it would appear to have 64 federal openings.

So an announcement naming more than 15 towns is not filed under any of them. It is counted separately and listed at Nationwide. Every place page states the two figures apart: positions based there, and announcements also open there. Both are true. Neither is the other.

Where the cutoff came from

It is not a round number chosen for tidiness. The location counts are lumpy: in this read, sixteen to nineteen locations account for 30 announcements between them — and then twenty accounts for 235. 234 of the 235 twenty-place announcements share one twenty-metro roster (Phoenix, Albuquerque, Atlanta, Austin, Boston, Chicago, Denver, Indianapolis and 12 more); its largest user is Department of the Air Force Headquarters, with 113 of them. A roster like that says any of our twenty hubs, not this job is in Phoenix: counting the twenty-town notices per city would take Phoenix from 74 positions to 308.

So the cutoff sits in the gap below that cliff. Below it, announcements naming a handful of hospitals or field offices stay filed under each — that is a real multi-site vacancy. Above it, the location list has stopped describing where the work is. It is the only judgement on this desk that changes a headline number, which is why it is written down here.

Closing dates

Unlike most registers, this one describes something that expires. A federal announcement closes on a fixed date, most within a month, and cannot be applied to afterwards. USAJOBS publishes each closing date with a time of 23:59:59 and no time zone; this desk counts the day in Eastern time, the zone OPM works in, so an announcement stays listed until midnight Eastern at the end of its closing day. The announcement’s own “How to apply” section states its deadline exactly: read it before you rely on a closing date here.

Anything past its closing date is dropped when the register is built and again whenever a page is served, so a stale read can go quiet but cannot show a job that has closed. In this read the closing dates run from 29 September 2026 to 27 September 2027; 8,277 of the 12,705 announcements read are still open today. A closed announcement’s address answers 410 Gone with the day it closed; this desk remembers 13,483 of them, and 4,306 towns ever listed, so an old link lands on something true.

What is not here

• 446 positions outside the United States, in 25 countries (by location mentions, Japan 264, Germany 241, South Korea 129). Federal agencies advertise them; this desk covers the fifty states, the District of Columbia and the U.S. territories. Positions with no fixed place at all are kept, at Remote.
• Announcements internal to an agency that OPM does not publish.
• Anything past its closing date.
• Any listing not in the federal register — no employer pays to appear here, because there is nothing to pay for.

Applying

Applications are made on USAJOBS and nowhere else. This desk collects nothing from you, asks for no account, and has no part in any hiring decision. It is not affiliated with, or endorsed by, OPM or any federal agency.

What was here before

This register was jobs.com.im (with job.com.im as a mirror) from 7 September 2026; since labs 547 both addresses answer one permanent redirect per page to the same page here. On the way in, the forty-seven of its fifty-seven occupational group pages that had shown “0 open announcements” since launch were fixed, the counts that had been printed from the read date were replaced by counts made at the moment a page loads, and search paging, the time zone and the sitemap dates were corrected.