How to verify a remote posting is real: the six checks we run on every listing
A remote job posting is a promise made by a stranger, on a page you did not go looking for, about a job you cannot see. Most advice about spotting fake postings is advice about grammar and emoji, and it is bad advice: a well written scam reads exactly like a well written job. The checks that work are structural. They ask where the posting came from, who read it, when we last saw it alive, and whether the employer published a figure anybody could compare against. We run six of those checks on every listing we publish, and as of the 2026-11-16 refresh 15,664 listings were sitting in the catalogue. Here is what each check is actually worth, including the part it cannot tell you.
The six checks, and what each one is worth #
| Check | What it proves | What it does not prove | Listings passing |
|---|---|---|---|
| The posting came from the employer's own board | the row was read from a career page the employer controls | that the employer still wants the role filled | 15,664 of 15,664 |
| The posting carried a remote scope we could read | the employer's own words said remote, remote first or remote allowed | that the scope is as wide as the reader needs | 15,664 of 15,664 |
| A model re-read the posting and kept it as remote | a second reader checked the posting against the remote claim | that the employer will pay, or that the salary is negotiable | 15,522 of 15,664 |
| The posting was confirmed alive within 7 days | the role was still on the employer board when we last looked | that it is still open now, only that it was | 9,987 of 15,664 |
| The posting carried a pay range a reader can compare | a figure was readable in the employer's own posting | that the figure is the whole package or the final offer | 2,804 of 15,664 |
| The posting carried a date from the employer's own board | the posting can be aged against the board own clock | that the date is the day the role was first advertised | 15,664 of 15,664 |
The first check is the one that removes the most risk, and it is a sourcing decision rather than a filter: we read every listing from the employer's own career page, through the public interface that page publishes, and we never publish a row that arrived from another board. That is why 0 of our 15,664 listings came from an aggregator. The second is the remote scope, which is our reading of the employer's own words rather than a field any board publishes: we look at the posting's location line and its description and classify what it says as fully remote, remote first or remote allowed. 15,664 of 15,664 listings carried a scope we could read. The third is a model re-reading the posting against the remote claim, and the fourth is the one readers underestimate: a listing is only called open if we confirmed it alive on the employer's board within 7 days of the refresh. The last two are the employer's own numbers: a pay range, which 2,804 of 15,664 listings carried somewhere a reader can read it, and a date from the board, which 15,664 of 15,664 carry.
Where the catalogue is weakest #
Two of the six checks never fail, because they are ours to keep rather than the employer's to decide: the source of the listing and the remote policy. The other four depend on what an employer actually did, and the numbers are not flattering.
- 5,677 listings were still listed but were not confirmed alive inside the 7 day window. They are published as aged, never as open.
- 12,860 listings carry no readable pay range. We publish the absence rather than inventing a figure.
- 142 listings were screened by rules rather than re-read by a model. Those listings are labelled as rule screened, not as verified.
- 67 listings are remote first or remote allowed rather than fully remote, so we publish the employer's own narrower wording instead of a promise of full remoteness.
The order to run them in #
- Open the employer's own career page, not the page that sent you the listing. If the role is not on the company's own site, stop there.
- Read the posting for a date the employer wrote. A listing with no date, or one that shows a date from the board rather than the employer, tells you nothing about its age.
- Look for the employer's own location and remote language, and treat a single city with the word remote in it as a warning rather than a promise.
- Check whether the posting names the pay. A role with no figure is not a scam, but it is a role where you are the one doing the market research.
- Apply through the employer's page. If a board asks you to apply there, you are being tracked, and the copy of the posting you are reading is not the employer's.
Why the numbers on this page carry a date #
Every figure above was computed from the catalogue, not typed by hand, and it describes the 2026-11-16 refresh. The catalogue is rebuilt from the employers' boards by a daily sweep, so these counts move. That is the point of publishing the date: the claim is scoped to the refresh it describes. If you want the same figures rather than this page's reading of them, the board itself is generated from the same catalogue and carries the same numbers.