Built on Bright Data Scraper Studio

The date says two days ago.
The role was filled in March.

Companies re-post roles and the clock resets, so the listings that waste your time look like the freshest ones on the board. Revenant checks each posting against the company’s own careers page, and tells you which ones they have already taken down.

Currently tracking

5,348
postings collected
96
company boards resolved
945
showing measurable decay
1,403/5,348
advertise pay in the structured feed

That last number is the argument for scraping rendered pages rather than consuming an API. The ATS feed carries no compensation field at all, while pay-transparency law puts salary ranges in the description prose of many of those same postings — reachable only by extracting it from the page. Scraper Studio recovers it on 86%.

01 — The listing

A role is posted.

It appears on the company’s own board, then on three aggregators. Everything agrees, and for a while everything is true.

Northwind Roboticstracking

Company board

Senior Robotics Engineer

listed

Aggregator

Senior Robotics Engineer

listed

Salary extraction86%
− .job-card .job-pay
+ .posting-row .compensation .amount

✕ Removed from the company’s own board, but still listed elsewhere.

A heal is graded before it is accepted.

Scraper Studio proposes a fix and parks it at an approval gate. The obvious move is to auto-approve. We deliberately don’t.

A heal that re-binds to the wrong element restores the fill rate perfectly while returning a job’s department where its location used to be — and fill-rate monitoring calls that a success. So Revenant re-runs the collector, grades the output against the platform’s own JSON feed, and only then approves.

Anyone can call self-heal. This is what lets us say why we rejected one.

Self-healing, end to end

Healthy

salary extracted on 86% of postings

salary field fill rate86%
baseline 86%
− .job-card .job-pay
+ .posting-row .compensation .amount

How it works

Proof, not inference

A listing is only called a ghost when the company’s own board contradicts it. Age and re-post churn can suggest decay, but they never earn that word — telling someone a real job is dead costs them an opportunity.

Drift against a baseline

Most postings advertise no salary, so alerting on nulls fires constantly and gets muted. Revenant compares each field against what that collector historically produced, separating “never advertised” from “extraction broke”.

It never applies for you

Public listings in, human decision out. The CV matching names the exact skills a posting asks for that you did not mention, and stops there. No account, no stored personal data.

Stop applying to jobs that no longer exist.

Paste your CV and get roles ranked by fit — with the dead ones already filtered out.