The GTM MCP Directory
Directory / The job board / Verification
The verification pass, 2026-09-14

What was removed, and why.

A job board is a claim about the world at a moment, and the moment passes. This page is the receipt. 158 tracked reqs were checked on 2026-09-14. 129 are published. 29 are not, and every one of them is named below with the reason it failed.

The method

  • Every GTM-engineering req found on the public ATS feeds of 152 watched employers, plus every req on the previous board, fetched at the exact URL the board publishes.
  • GET, real browser user agent, 10s timeout, 4 concurrent, 1 retry.
  • Where the employer runs a public Greenhouse, Lever or Ashby board feed, the req id is also checked against that feed. A req the employer's own feed has dropped is dead even if the page still loads.
  • Only status=live reaches the board. dead and unverified are published here and nowhere else.
  • changed=true is a live req whose title, location, remote flag or salary moved since it was recorded. The board publishes the new value.
  • $0. Free public HTTP only. No paid API, no LinkedIn, no scraping of anything behind a login.

The three answers, and what each one means

AnswerWhat it meansPublished?
liveThe apply link answered and the posting was on it. Where the employer runs a public board feed, the req id was still in that feed too.Yes
dead404, a closed-posting message, a redirect to a careers index with no trace of the req, an empty ATS shell, or the employer's own feed has dropped it.No
unverifiedThe check could not settle it. A JavaScript-only page that renders nothing to a plain fetch, or the page and the employer's feed disagreeing with each other. Unverified is not a softer word for live.No

How the filters are derived

FieldHow it is derived
days_trackedDays between the first time this lane saw the req and the verification date. It is not a posted date and it is not claimed to be.
regionSubstring match over the employer's own location string. A req naming several cities appears under each of them.
salaryPrinted only where the employer publishes it: the machine readable pay field of their own board feed first, else the first range printed in their own posting text. Never estimated, never inferred from a range seen elsewhere.
seniorityOrdered substring match over the title only. A title that says nothing about level is filed as not stated rather than guessed.
title_familyOrdered substring match over the employer's own job title. First rule that matches wins. It is a filing decision, not a judgement about the work.

What is not on this board

Job descriptions. Salary estimates. A count of applicants. A recruiter contact. Anything we would have had to guess. A salary appears only where the employer publishes it in the machine readable field of their own board feed, which is why 95 of 129 rows carry one and the rest are blank rather than estimated.

The removal ledger, 2026-09-14

29 listings. These URLs are printed as text, not as links, because they no longer work. That is the point of printing them.