ATS-direct detection latency: median 2.1 hours (measured 2026-08-08)

Median 2.1 hours from an employer publishing a requisition to Reqbeat detecting it, across postings read directly from an employer's applicant-tracking system, over the 14-day ingest window the whole latency cut was taken from. Measured 2026-08-08; this reading expires 2026-11-06.

Method version 1.12.0 · Page rebuilt September 14, 2026 · Full methodology

What is being measured

One quantity: the elapsed time between the timestamp a posting carries as its publication date and the timestamp at which it entered this corpus. It is a property of how fast we read the sources, not a property of the sources themselves, and it varies by an order of magnitude between them — which is why every figure below states the population it was cut over rather than being pooled into a single number.

Nothing recomputes these. Each is one cut of a moving corpus taken on a stated day, so each carries that day, its derivation, where the cut was run, and the day it stops being quotable — 90 days later. Past that date this page withdraws the reading rather than restating it.

Detection latency by source

2.1 hours

Population: postings read directly from an employer's applicant-tracking system, over the 14-day ingest window the whole latency cut was taken from.

Derivation: Median of `created_at - posted_at` over the ATS-direct cohort of a 14-day ingest window (n=2,441,587 across all cohorts). p95 on the same cohort is 5.7 days. 7.94% of corpus rows carry `posted_at` stamped equal to `created_at` at ingest (signalsapi-4450), which reads as zero latency; the cut is not filtered for them, so this is a floor rather than a point estimate.

Computed by: The 2026-08-08 measurement pack (`docs/gtm-cofounder/founder-brief.md`, §Measured facts, finding 2), cut directly against the corpus database upstream. This repo holds no read path that can reproduce it.

Expires 2026-11-06.

Lever detection latency (p50)

measured 2026-08-08

12 min

Population: postings whose source is Lever, in the same 14-day ingest window.

Derivation: Median of `created_at - posted_at` restricted to the Lever source; 12.1 minutes unrounded. 7.94% of corpus rows carry `posted_at` stamped equal to `created_at` at ingest (signalsapi-4450), which reads as zero latency; the cut is not filtered for them, so this is a floor rather than a point estimate.

Computed by: The 2026-08-08 measurement pack (`docs/gtm-cofounder/founder-brief.md`, §Measured facts, finding 2), cut directly against the corpus database upstream. This repo holds no read path that can reproduce it.

Expires 2026-11-06.

1.7 h

Population: postings whose source is Greenhouse, in the same 14-day ingest window.

Derivation: Median of `created_at - posted_at` restricted to the Greenhouse source. The unrounded figure is 99.3 minutes; the published form is its rounding to hours. 7.94% of corpus rows carry `posted_at` stamped equal to `created_at` at ingest (signalsapi-4450), which reads as zero latency; the cut is not filtered for them, so this is a floor rather than a point estimate.

Computed by: The 2026-08-08 measurement pack (`docs/gtm-cofounder/founder-brief.md`, §Measured facts, finding 2), cut directly against the corpus database upstream. This repo holds no read path that can reproduce it.

Expires 2026-11-06.

Workday detection latency (p50)

measured 2026-08-08

3.07 days

Population: postings whose source is Workday, in the same 14-day ingest window.

Derivation: Median of `created_at - posted_at` restricted to the Workday source, with 0.05% of that cohort inside an hour. Registered although no page quotes it: it is two orders of magnitude off the two vendors that are quoted, so it is what makes a pooled median under a sentence naming only the fast vendors a mixing error rather than a simplification. 7.94% of corpus rows carry `posted_at` stamped equal to `created_at` at ingest (signalsapi-4450), which reads as zero latency; the cut is not filtered for them, so this is a floor rather than a point estimate.

Computed by: The 2026-08-08 measurement pack (`docs/gtm-cofounder/founder-brief.md`, §Measured facts, finding 2), cut directly against the corpus database upstream. This repo holds no read path that can reproduce it.

Expires 2026-11-06.

9 hours

Population: every non-synthetic posting in the same 14-day ingest window.

Derivation: Median of `created_at - posted_at` over the whole window (n=2,441,587); 9.0 hours unrounded. The class of rows with a trustworthy timestamp is 92.3% `li_jobs`, so this figure is substantially a statement about one source. 7.94% of corpus rows carry `posted_at` stamped equal to `created_at` at ingest (signalsapi-4450), which reads as zero latency; the cut is not filtered for them, so this is a floor rather than a point estimate.

Computed by: The 2026-08-08 measurement pack (`docs/gtm-cofounder/founder-brief.md`, §Measured facts, finding 2), cut directly against the corpus database upstream. This repo holds no read path that can reproduce it.

Expires 2026-11-06.

48 hours

Population: every non-synthetic posting in the same 14-day ingest window.

Derivation: 95th percentile of `created_at - posted_at` over the same population as the corpus-wide median above; 48.0 hours unrounded. 7.94% of corpus rows carry `posted_at` stamped equal to `created_at` at ingest (signalsapi-4450), which reads as zero latency; the cut is not filtered for them, so this is a floor rather than a point estimate.

Computed by: The 2026-08-08 measurement pack (`docs/gtm-cofounder/founder-brief.md`, §Measured facts, finding 2), cut directly against the corpus database upstream. This repo holds no read path that can reproduce it.

Expires 2026-11-06.

How to cite this

Quote the figure with the population it was cut over and the day it was taken — a latency number without a cohort is not a claim anyone can check, and the spread between the fastest and the slowest source here is more than two orders of magnitude. Each reading above is addressable on its own: https://reqbeat.com/detection-latency#ats-direct-detection-latency-p50.

The sample definition, the deduplication rule, the known biases and the pre-registered metric definitions behind these readings are published in full on the method page, alongside every other dated figure this site quotes.