A job page loaded in 1.2 seconds, returned 200, rendered a full careers layout, and said the role was no longer open.
That was one of six links published as a reproducible sample on a page about how long job postings stay live — a page updated five days ago. Two of the six were dead. Both returned 200.
The pull
Fourteen URLs from the sitemap, fetched one at a time over a residential connection on 20 November 2026. All 200. I then parsed the <main> block only, because pulling <a> tags from the whole document gets you navigation and footer noise and inflates every count.
import re, html
main = re.search(r'<main[^>]*>(.*?)</main>', page, re.S).group(1)
links = re.findall(r'<a\s[^>]*href="(https?://[^"]+)"', main)
ext = [u for u in links if 'jobradarly.com' not in u]
Eleven outbound links on the entire site. Nine of fourteen pages have zero. Ten go to individual job postings, one to a USCIS page about the H-1B cap.
That last number is the interesting one for a site whose guides are full of statistics: 13,354 words of guide copy, and no citation to any labour-market dataset. Not the BLS, not a hiring survey, nothing. The only externally verifiable claim chain on the site runs through ten job URLs.
Re-checking the six
| Company | Role | First published | Days live on 28 Oct | 20 Nov |
|---|---|---|---|---|
| Stripe | Managing Editor, Stripe Press | 27 Oct 2026 | 0.5 | dead — "Role no longer open" |
| GitLab | Manager, Customer Success | 17 Oct 2026 | 11 |
dead — redirect to ?error=true
|
| Datadog | Senior Sales Engineer, AI Accounts | 29 Sep 2026 | 29 | live |
| Cloudflare | Senior Majors Account Executive, Chicago | 31 Jul 2026 | 89 | live |
| Supabase | Multigres Deployment Engineer | 15 Apr 2026 | 196 | live |
| Ashby | Engineering Manager, EU | 4 Mar 2024 | 968 | live |
Both failures are 200s. Stripe serves a 148 KB page with "no longer accepting applications" in the body. GitLab serves 77 KB and drops you on the board's error state.
I ran a status checker before reading any body text and got 11/11 green. That was my error, and it's the reason this post exists: a HEAD request tells you a server is alive, not that a job is.
Pulling the boards myself
The page claims 3,272 live postings across 16 boards with medians of 49 days (Greenhouse) and 64 (Ashby). It names six boards, not sixteen, so the population isn't reproducible. I pulled the eight I could identify from the vendors' own public APIs — no key, no account.
# Greenhouse
curl "https://boards-api.greenhouse.io/v1/boards/gitlab/jobs?content=false"
# Ashby (schannel on Windows needs the no-revoke flag)
curl --ssl-no-revoke "https://api.ashbyhq.com/posting-api/job-board/ashby"
| Board | ATS | Live roles | Median age | > 30 days | New in 7 days |
|---|---|---|---|---|---|
| Cloudflare | Greenhouse | 497 | 52 | 67.0% | 44 |
| Datadog | Greenhouse | 382 | 80 | 79.1% | 18 |
| GitLab | Greenhouse | 246 | 34 | 52.4% | 38 |
| Stripe | Greenhouse | 773 | 52 | 66.4% | 70 |
| Ashby | Ashby | 79 | 72 | 58.2% | 15 |
| Ramp | Ashby | 185 | 50 | 61.1% | 23 |
| Sierra | Ashby | 194 | 80 | 73.7% | 3 |
| Supabase | Ashby | 79 | 37 | 54.4% | 7 |
2,435 roles. 67.3% of the Greenhouse sample is over a month old, against their claimed 68%. Different day, different subset, same shape — so the "postings last one to two weeks" folklore really is wrong.
Three surprises
The two dead roles were the two youngest. Half a day old and eleven days old at pull time. The survivors were 29, 89, 196 and 968 days old. Age anti-predicted death here. A three-week-old listing that's still up is usually a genuinely unfilled req; a one-day-old listing is one someone just opened and can close the moment they fill it.
200 is the standard way a job link dies. Neither ATS returns 404 for a closed posting. Greenhouse serves the error state on the board URL, Stripe swaps the body. Any link checker you own will report these as healthy forever.
968 days and still open. One Ashby role has been listed since March 2024. Fifteen of the 79 roles on that board are over 30 days old. Whatever a "posting lifespan" is, it isn't a property of the posting.
What I couldn't get
When Stripe's role closed. It was alive on 6 November and dead on 20 November, which brackets it to somewhere between day 10 and day 24 after publication. Narrowing that needs daily polling and I started on the 20th.
And the 3,272 figure stays unverified. Their closed postings are gone from the API, so a surviving-set median is biased downward by construction — mine would be measuring survivors against their full set and calling the gap a finding. It isn't one.
Disclosure: JobRadarly is one of our own sites, and the two dead links are still live on it as of publication. Everything above came from its own pages and from public ATS endpoints.
Open six outbound job links on your own site and read the body, not the status code.
Top comments (0)