RevivaCatch

Job-postings data, read nightly at the source

Job postings, with proof of which boards are complete.

Every night, open roles are read straight from each employer’s own job board. Where the hiring platform publishes its own job total, the read is tied to that number, board by board. Where it doesn’t, the board is marked, never guessed, and a board that could not be read is never passed off as one with no openings.

The sample is five CSV files and a manifest, re-cut every night. No signup, no NDA.

Schedule of boardsRead of 1 Oct 2026
Employer job boards read15,614
Platform publishes its own job total8,317
Tied to that total8,159
of which provably hiring nobody252
Disagreed with it, kept and flagged17
Not reached that night86
No total published for that board55
Platform publishes no total7,297
  • tied to the platform’s own published count
  • reached, empty, and the platform agrees: zero
  • counts disagree; the board is kept and flagged
  • not reached; labelled, never shown as empty
  • nothing published to tie to; labelled unverified

As of the read of 1 October 2026. Live figures update after each nightly run.

Where the data comes from

Each employer’s careers page runs on a hiring platform, and the platform serves a public feed of that employer’s openings. That feed is read directly: no aggregators, no logins, no bought data.

Three of the nine platforms publish their own job total. That total is what the night’s read is tied to.

PlatformBoardsOwn total
Greenhouse3,574published
BambooHR3,492published
Ashby2,486none
Workable1,875none
Workday1,251published
Recruitee1,043none
Personio866none
Rippling864none
Lever163none
Nine platforms15,6143 of 9

What happens every night

  1. Read

    Each board’s public job feed is fetched under an identified user agent. robots.txt is obeyed, and every exclusion is written into the code. No logins, no proxies.

  2. Tie

    Where the platform publishes its own job total, the night’s count is compared with it, board by board.

  3. Mark

    Each board gets one mark: tied, disagreed, not reached, or unverified. Nothing is guessed, and a failed read never looks like an empty board.

  4. Append

    New and removed postings are added to the record with the night they were first and last seen. Nothing is back-filled.

What a row holds

Employers and vacancies only: no candidates, applicants or contacts.

Delivered nightly as JSON and CSV.

ats, tokenThe platform and the employer’s own public board. Every row is keyed to it.
companyThe employer’s name, on 10.5% of boards so far. Never guessed.
title, location, department, urlAs the employer posted them.
first_seen, last_seenThe nights the posting was first and last seen.
extraSince 25 September 2026: pay, seniority, years of experience, employment type, workplace, industry and country, wherever the platform publishes them.
609

listed companies, on 610 boards. Measured 24 September 2026.

155 / 503

S&P 500 constituents with their own board here, and 12 more through a subsidiary.

Known exceptions

History is short

Recording began 29 August 2026. There is nothing earlier in the data.

S&P 500 coverage is partial

155 of 503 constituents have their own board here. Boards on Oracle Taleo, SAP SuccessFactors, iCIMS, Phenom and SmartRecruiters are not collected.

Most boards carry no name

Only 10.5% of boards carry the employer’s name. Every row still carries its board key, and names are never guessed.

One person runs it

If the nightly run stops, the files stop updating, and their dates show it.

Ask for the DDQ

The due-diligence answers cover sourcing, robots.txt exclusions, data rights and every known exception. Monthly or annual licence, or a paid 30-day pilot. Pricing on request.