What the dataset is.

How it is built

The machine reads each company's own applicant tracking system directly, every night: the same feed a candidate would meet by going to that company's own careers page. Nothing here is bought from an aggregator and nothing is copied from a board that copied someone else. A posting earns a row by surviving a published set of rules; one that fails a rule is killed the same night, dated, and kept rather than deleted. That is the shape of the pipeline. The detail, feed by feed and rule by rule, is on the methodology page.

Read the method in full, including the published kill rules a posting is judged against before it is ever counted below.

What this sweep covers

A sweep reads two different sizes of thing, and keeping them apart is this page's whole job. One count is everything sitting on the boards the machine reads. A smaller count is the postings that passed this product's own title and location filters and therefore reached a verdict: verified live, or killed. Every other number on this site, the row count on the index, the kill list, the report, describes that second, smaller population. This page states both, by name, so neither is mistaken for the other.

Boards read direct

45

Postings sitting on those boards

3786

Reached a verdict (passed the title and location filters)

85

Verified live

82

Killed this sweep

3

The gap between the first two rows and the last three is not loss and it is not an error: it is everything on those same boards that this product's own filters set aside without a verdict, still sitting on the board it came from, never claimed as measured by anything on this site.

What one sweep means

This build carries one sweep: the one stamped at the top of this page. The archive holds this sweep and nothing else. There is no trend line here, no week-over-week change, no repost history, because none of those is a real measurement from a single night's read; a trend is a shape made of several readings, and a page that implied one from one would be implying a depth the archive does not hold.

The machine that produces these files runs nightly, and every sweep replaces them wholesale rather than appending to them. The history this page could eventually state honestly, how long a posting really lives end to end, how often a role gets reposted, how the count of boards read has grown, is built one file at a time starting now. It is not built yet. This section states a number the day it is.

The free monthly analysis

The report publishes what a sweep finds, the same night the data is: the arrival window, how long postings live, what died and under which rule. It runs from the same two files this page does, so nothing in it is stated twice with two different numbers. One issue exists today because one sweep exists behind it; the cadence becomes monthly the day there is a month of sweeps to write one from.

Two ways in, before either is a product

Neither of the two things below is built. Both collect interest, never money and never payment details: mail an address, nothing else.