13 ATS portals · one canonical ontology · applicant-first

Every job. One ontology.
Answer once.

Fetch 10,000 jobs and something surprising happens: every screening form in the world collapses into a small mapping. Postings grabs everything, normalizes it into one canonical ontology, and keeps that ontology honest with you — one redo callback at a time.

13ATS portals
9,400+Postings fetched
541Company boards
21,196Screening questions
→ 1,053Canonical mappings
The product flow

Grab → normalize → cross-maintain

21,196 screening questions from the wild reduce to just 1,053 canonical mappings. That 20:1 collapse is the whole product: past ~10k jobs, the space of possible field options is finite — and ownable.

01 — GRAB

All postings, direct from the ATS

Adapters hit the public APIs of 13 ATS portals and pull every posting and every application form — fields, options, required flags — into one common shape.

02 — NORMALIZE

Everything maps to the ontology

Every question is classified against priority-ordered mappings into a canonical profile key. Twenty ways of asking "are you authorized to work?" become one field.

03 — REDO CALLBACKS

You keep the ontology honest

Hit something unmapped? Answer it once. The system learns a new mapping, fires a redo pass over everything already crawled, and that question resolves everywhere, forever.

The AI layer

Ontologies, leads, and prep-books — generated for you

Claude-powered classification runs over every form we crawl. But the model isn't just filling fields — it's building applicant-side intelligence.

  • Custom screening ontologies — your own canonical field set, generated from the questions you actually face and refined by your redo callbacks
  • Lead mapping — recruiter threads from LinkedIn and Gmail parsed into structured leads: contacts, companies, and upcoming calls flagged automatically
  • Pre-interview prep-books — before every call, a generated brief: the role, the form you filled, the thread history, and what to say next
"Are you legally authorized to work in the US?"
Greenhouse · seen 214×
→ work_auth
"What are your pronouns?"
Ashby · seen 96×
→ pronouns
"Desired compensation range?"
Lever · seen 143×
→ comp_expectation
"Describe your sommelier certification"
Workable · unseen
redo → learned
Recruiter reply · call Thu 2:30pm
Gmail thread · prep-book ready
lead
Applicant-first, not company-first

Engagement recommendations built around you

Every other tool in this space organizes the world by company. Postings organizes it around the applicant: leads emerge across every surface — ATS portals, company boards, LinkedIn threads, Gmail — and get routed to you as one prioritized queue of what to engage next.

Lead emergence, all surfaces

A recruiter DM, a reply buried in Gmail, a fresh posting on a board you starred — the moment a lead surfaces anywhere, it lands in your queue with full context attached.

Recommendations, not dashboards

Not "here are 500 companies" — but "these three threads are warm, this call is Thursday, this application is one answer from ready." Ranked by your momentum, not their org chart.

Your profile compounds

Every answer, document, and redo callback enriches one applicant profile. The more you engage, the less the system ever asks of you again.

Deep discovery

BFS/DFS over the whole hiring graph

Job boards decay. Links rot. Companies switch ATSes mid-search. Postings runs deep breadth-first and depth-first topology searches across ATS portals and company boards, so discoverability never silently degrades.

  • Full-topology crawls fan out across all 13 ATS portals and 541 company boards
  • Liveness probes tell live postings from ghosts — expired roles clear themselves out
  • Board migrations tracked: when a company moves ATS, the trail follows
  • Schema drift absorbed: new fields register instead of breaking the pipeline
BFS sweep · Greenhouse
208 boards · 3,914 postings
live
DFS probe · Workday tenant
nested board · 3 levels deep
found 47
Liveness check · Ashby
1,120 postings probed
31 expired
Board migration detected
Lever → Ashby · trail preserved
re-linked
Schema drift · new field
registered, sync unbroken
absorbed
Coverage

13 ATS portals, adapters for each

GreenhouseAshbyLever WorkdaySmartRecruitersiCIMS WorkableRecruiteeBambooHR BreezyPinpointPersonio Rippling
Built by people who job-hunt too

"When will you have a job?"
You'll have an answer.

The forms are finite. The ontology is small. Your time should go to interviews, not to typing your work authorization for the two-hundredth time.

Request access