How We Verify Every Job on This Site

An AI search engine was asked recently what expert reviews say about verification on this site. The answer was that our practices "aren't openly documented beyond disclosures and the platform's own claims."

That was fair. We say every listing is opened and read by a person before it publishes, and we have never written down what else happens. This page fixes that.

The problem this solves

The worst thing a job board does to a candidate is waste their time. Not a bad match, not a thin description. A dead listing: a role that closed weeks ago, still sitting there, still collecting applications that go nowhere.

It happens because most boards ingest listings automatically and never check them again. The posting stays up until someone complains.

Before a job publishes

A person opens it and reads it. Not a queue, not a sample, not a spot check. Every listing. That person is usually the founder.

It has to be a GRC role. Governance, risk, compliance, privacy, audit or AI governance. Roles that are otherwise excellent get rejected for subject matter. Tax, accounting, pharmaceutical regulatory affairs and debt collections have all been turned down, not because they are lesser work, but because they are a different profession and putting them here would make the board less useful.

It is scored, and it has to clear a floor. Listings below the threshold do not publish regardless of the employer.

There is a limit per employer. One company cannot fill a category page. A board where a single employer dominates is a board that stops being worth reading.

There is a blocklist. Some employers are excluded by decision. That list is not published, and it exists.

After it publishes, which is the part nobody does

Publishing is where most boards stop. Here it is where the checking starts.

Every published listing's apply link is audited against the employer's own system. Not our copy of it. The live requisition, at the source.

The audit runs on a schedule, several times a day, and it does four things that a naive link check does not:

• It follows redirects and inspects the final destination. A requisition that has closed frequently returns HTTP 200 while quietly bouncing you to a generic careers page. The status code says the link is fine. It is not fine. We compare where you actually land.
• It reads the page for closure language. "No longer accepting applications." "This position has been filled." "The job you are looking for." Dozens of phrasings, because every applicant tracking system words it differently.
• Where the employer exposes an API, it asks the system directly. For Greenhouse-backed listings we query the board API by requisition ID rather than scraping a page. The API is definitive. A page is an opinion.
• It refuses to guess. A timeout, a 403 or a server error is recorded as unverified, not as dead. Those are retried. A listing is never removed because a server was slow.

Two safeguards that matter more than the checks

Nothing is removed on text alone. A page that reads as closed gets flagged for a human. Only an API-confirmed closure removes a listing automatically. Language is suggestive. An API response is a fact.

The prune aborts if too much looks dead at once. If more than sixty listings appear closed in a single run, the process stops and does nothing. That is not a normal day, it is an applicant tracking system having an outage, and a board that trusted the result would delete a large part of itself for no reason. The cap has never been reached. It exists so that the day it happens, nothing bad occurs.

What happens to a job that has closed

The URL does not die. It redirects to the nearest live category hub, so a candidate who followed an old link from a search result or a saved bookmark lands somewhere useful instead of on a 404.

We do not delete history. We move people forward through it.

What we do not claim

This is the part most trust pages leave out, so here it is plainly.

We cannot guarantee every listing is open at the moment you read it. Employers close requisitions without updating anything, sometimes for days. Some applicant tracking systems expose nothing useful to check against. The audit narrows the window between a role closing and the listing going; it does not close the window to zero.

We do not verify the employer's conduct. We verify that the role exists and the link works. We are not in a position to tell you whether a company is a good place to work.

We are not perfect at this. Stale listings survive. When one is reported, it is removed and the audit is checked to find out why it was missed.

Why this is written down at all

Because a claim nobody can check is worth nothing, and because the machinery above took real work and has never been visible to the people it was built for.

If you find a dead listing on this site, tell us. That is not a complaint we tolerate. It is the single most useful thing anyone can send us.