3,438,125 jobs from 171,421 employer career pages

What a verified badge has to earn

Most job platforms call a listing verified because it has a date on it. We check three separate things — the portal it came from, the employer behind that portal, and the req itself — and a badge only appears when all three hold. On the candidate side, the anchor is a real interview, wherever it happened.

Hosts classified
35,485
behind 171,421 portals
On a tier-A tenant
94.1%
of every listing we hold
Listings stamped
1,886,998
55% of the pool, re-stamping hourly
Re-verified every
90d
a stamp with no expiry is a lie

Three questions, asked separately

Each can fail on its own, so each is answered on its own. A trustworthy portal does not make an unreadable listing trustworthy, and a real employer does not make a stale req current.

01 · PORTAL

Where did this come from?

Every listing carries the host it was scraped from. We classify the host once and every listing from it inherits the result — the only way a pool this size gets checked at all.

Answered byATS tenancy, domain history, our own scrape record
02 · EMPLOYER

Is this a real company?

A host is tied to a legal entity through the registry for its market — GLEIF, Companies House, MCA, ABN. On a vendor-hosted board the tenant slug already is the identity.

Answered byCompany registers, payroll records, tenancy
03 · THE REQ

Is this job actually open?

The listing has to be readable, recently seen, present on the employer’s own board, and not a copy of something posted elsewhere.

Answered byDescription, freshness, canonical match, duplicates

How a portal gets verified

Every distinct host in the pool resolves into one of four tiers. Tier A is the strong one and it costs nothing: on a vendor-hosted applicant tracking system the tenant slug was issued by the vendor to that employer. usbank.wd1.myworkdayjobs.com cannot be stood up by somebody else.

TierWhat it meansHow it is establishedHostsListings
AVendor-hosted ATS tenantTenant slug issued by Workday, Greenhouse, Oracle, iCIMS and 30 others29,6683,236,308
BOwn-domain career siteConfigured board with sustained yield across many days67466,413
COwn domain, thin historyKnown board, not yet enough record to stand behind2,15519,326
DAggregator or unplaced hostRepublisher, or a host we cannot tie to an employer2,988116,078

Why tier A carries so much. 3,236,308 listings sit on boards where the employer’s identity was established by the ATS vendor before we ever saw it — not a claim to take on trust, a fact about who was issued the tenancy.

Top vendors by volume: workday 1,275,946, iCIMS 368,812, oracle 352,159, Greenhouse 211,630, Paylocity 153,786, SmartRecruiters 130,978, Workable 118,394, JazzHR 108,503.

The five states a listing can be in

A binary badge forces every ambiguous listing into one of two wrong answers. Each state says what is actually known, and a listing takes the weakest link in its chain.

Verified

Employer established, req readable, seen this week, present on the employer's own board, not a duplicate.

Recognized

The employer is real. Something about this req could not be confirmed — usually a missing description.

Unverified

No claim in either direction. We could not place the host. Never shown as a warning.

Caution

A specific finding: no successful scrape in 90 days, heavy reposting, or the same text on another host.

Blocked

Disqualifying: a dead link, a look-alike domain, a dissolved entity, or money asked for before hire.

How a candidate gets verified

The hard problem here is not identity documents — it is proving a real, capable person is behind an application when hundreds look alike. We do not judge whether a résumé was written with AI. We look for what a fabricated candidate cannot produce cheaply.

1

A real interview is the anchor — wherever it happened

A live conversation with a real employer is the most expensive thing for a fabricated candidate to produce at scale. No candidate reaches Verified without one. The interview does not have to come through Matatah. If you interviewed somewhere you found yourself, that counts — it just has to be corroborated.

2

Four ways an off-platform interview is corroborated

A calendar invite from a corporate domain that resolves to a tier A or B employer. A scheduling email whose signature passes authentication against that domain. A direct confirmation from the employer. Or an interview held on Matatah. Any one is enough; a screenshot is not.

3

Continuity over documents

A government ID proves a document exists; it does not prove the person applying will do the work. What is hard to fake is history with depth — an account with years behind it, a commit graph, published work, a domain registered long before today.

4

Artifacts over assertions

A link to something you made is checkable. A paragraph describing it is not. This costs an honest candidate nothing and a manufactured one everything.

5

What gets flagged, and what deliberately does not

We flag concealment — text hidden from human reviewers but fed to screening models — because invisible text has no innocent explanation. We flag identical claimed accomplishments across supposedly unrelated candidates. We do not flag polished writing, AI assistance, or an application that reads like the others.

Why not just check IDs? Identity verification catches the wrong failure. The people causing real harm are not using fake names — they are real people misrepresenting capability, or operations running many plausible personas at once. An interview requirement and a demand for checkable work defeat both, without asking honest candidates for a passport.

Verification only ever raises confidence. An unverified candidate is not marked down. Plenty of real people worked at companies that no longer exist, freelanced, or are re-entering the workforce — the moment a missing badge becomes a penalty, the system stops protecting people and starts gatekeeping them.

Warm Intro: how we find people

Warm Intro suggests people at a company who could refer you for a job already in your pipeline. It uses no paid people-data broker, and it never touches LinkedIn from our servers.

  • Where names come from. Only the job posting’s own text, the company’s own public team, about, leadership and blog pages, the title and snippet of web search results, your own Gmail headers if you connect it, and profiles you open yourself and save with the extension.
  • What we never do. We never log into, automate or fetch linkedin.com, never scrape profile pages, never read LinkedIn exports, and never send a message for you. Matatah drafts; you send.
  • No emails or phone numbers. We never collect, store, guess or show contact details of people we find. You reach them through their profile, or by Gmail only if they are already in your own inbox.
  • Polite crawling. Company pages are fetched as MatatahBot, obeying robots.txt and crawl delays, one request per second per site at most, and only for companies users are actually applying to.
  • Minimal, fresh, capped. The shared cache holds name, title, public profile link, company, team, function, seniority, location if shown, source and dates — nothing about any user. Anyone not confirmed in 60 days is rechecked before being shown, people not confirmed in 180 days with no active job are deleted, and no one is suggested to more than five Matatah users a week.
  • Searches only when you ask. Matatah searches only when you choose “Warm intro first” on a job, or a job moves to Applied (unless you turned that off). Jobs you’re just browsing never trigger a search, and a search one person ran is reused for everyone applying to the same team.
  • People for each step, checked. Under “Who to reach”, each step (alumni on the team, alumni at the company, the team in the job’s city, recruiters, the team lead) runs one web search, and only people whose result shows that step are listed — your school, the team, the city, the title. Your school comes from your résumé; the other person’s school is checked in the search result and never stored.
  • Honest labels. “Knows you”, “Shared background” or “Cold”. A cold contact is never called a referral.
  • Removal. Anyone can ask to be removed at matatah.com/remove. We honor it within 72 hours — in practice immediately — and that person is never suggested again.

What we do not claim

  • A verified employer can still send a bad offer. If someone takes over a real recruiter’s mailbox, every domain-level check passes. Never send money, bank details or identity documents before a written offer you confirmed through a number you found yourself.
  • Small and new employers score lower through no fault of their own. A ten-person company with a year-old domain has less to check. We report that as thin coverage, not suspicion.
  • We do not detect AI-written applications, and we will not try. Every tool claiming to produces false accusations against non-native speakers and career changers. What our own agent does with AI, and how a candidate should answer “did you use AI?”, is written down at /trust/ai.
  • Takedowns are slower than registrations. A domain costs about ten dollars; removing one takes days. We shorten the gap between a fake appearing and you being warned — we cannot close it.

Portal tiers, listing counts and vendor volumes are read from the live pool at page load — 3,438,125 listings across 35,485 distinct hosts, last stamped 13 October 2026. Employer registry coverage reflects sources publicly available in each market. Check a specific posting, offer or application on the verification tools.