Skip to content

Hiring radar

The AI-training job market, role by role, every day.

Every role the AI-training platforms post on their own job boards: what it pays, which experts it wants, where it is open, when it opened and when it closed. Read every hour, delivered to your team as files.

$25,000 a year, every file below, rebuilt every day.

Who it is for

Read the demand behind AI training before it reaches a report

Investors in the listed AI-data vendors

Contractor hiring at Appen, Innodata, TELUS and RWS is a read on the demand their customers place with them, weeks before it reaches a quarterly report.

Private-market investors and secondary buyers

Mercor, micro1, Invisible, Alignerr, Handshake AI, Mindrift, Surge and Scale's programs: how much expert work each is buying, in which fields, at what pay, and how fast it fills.

Strategy and corporate development teams

Who is hiring which experts for AI training, where, and at what price, measured the same way across every platform.

Data points

Exactly what we hold, and how much of it

The counts cannot be read right this moment; the sample's dictionary file carries them for every column.

What you receive

Everything in one subscription

$25,000 a year for your firm: every file below, rebuilt every day, at addresses that are yours for the year.

  1. Role records

    roles.csv

    One row per AI-training role we have recorded since our first read, open or closed: platform, the platform's own posting id, title, kind of work, the platform's own field, advertised pay as written and as an hourly range, where it is open, remote or on site, contract type, when the platform posted it, when we first and last saw it, and whether it is still open. The whole file is rebuilt every day.

  2. Change log

    changes.csv

    Every change our reads see on a role, with the time of the read: it closed, it reopened, its advertised pay moved (old and new, as written and as an hourly range), its title changed.

  3. Platform by day

    platform-days.csv

    For every platform and every day since we first read it: roles open, roles that appeared, roles that closed, and the median advertised hourly pay of the open roles. When we changed how we read a platform's board, the roles that came into or left view with it have columns of their own, with what we changed, and are never counted as opened or closed.

  4. Market by day, as recorded

    market-days.csv

    The market as we recorded it that day: open roles, roles new in the week, platforms hiring, and per kind of work the open roles, the median and typical advertised hourly pay and how many rates they rest on.

  5. Coverage by platform

    platforms.csv

    For each platform: the day we first read it, how many roles we hold, how many are open, and how complete each field is.

  6. Reconstructed history

    history-postings.csv, history-captures.csv

    The platforms' own job boards as the Internet Archive captured them, from 2024 where captures exist, rebuilt posting by posting and kept apart from what we observed ourselves, so a reader always knows which is which.

    Being rebuilt now; delivered platform by platform as it lands.

  7. Data dictionary and method

    dictionary.csv

    Every field of every file: what it means, how it is measured, how many rows carry it and since when.

  • Files as CSV, or JSON with ?format=json, at addresses that are yours for the year: open them in a spreadsheet or fetch them from code every day.
  • The files are rebuilt from the job boards we read every hour; each file states when it was built.
  • Licensed to the one firm that subscribes, for its own internal use, for twelve months: never to be resold, shared or published outside it. See the Hiring radar licence.

Method

How it is measured

  • We read each platform's own public job board, its applicant tracking system's feed or its own listings, every hour. Each platform's first day in our data is in the coverage table.
  • Only roles read from job boards anyone can open without signing in and without passing a check against automated reading are sold, role by role. A platform read any other way stays on our own site and in the market's daily totals as recorded, never in the role files. That is why the open roles on our job board, 0 today, are more than the role files hold open: the board also lists 0 on Turing and 0 on AfterQuery.
  • One row is one role. A role a platform posts once per country, or reworded several times at the same pay, is kept once, with all its countries.
  • The files hold job postings, not people: no column names or identifies a person, and nothing about the visitors, users or applicants of our job board is in them.
  • Pay is the platform's own advertised line, kept as written. Hourly rates and ranges are also read into USD figures; salaries and per-task pay stay as written.
  • A platform's roles in its first week with us were already listed when we started reading it, so they are never counted as newly opened (the first_week column of the platform-by-day file).
  • A role closes on the first read that no longer lists it; last_seen_at is the last read that did.
  • Until 26 Oct 2026 a role kept only its latest state: its pay before a change, and the days a reopened role was away, were not kept. From then on the change log has every one of them.
  • Kinds of work are our own classification, the same for every platform: AI Evaluation & Rating (RLHF), Coding & Software Evaluation, Math & STEM, Law, Medicine & Finance, Agentic Tasks & RL Environments, Data Annotation & Labeling, Robotics & Physical-AI Data, Multilingual & Localization, Transcription, Audio & Speech, Writing & Content, Red-Teaming & AI Safety, Research Studies & Surveys.

Free to read

What stays free

Our research reports and a monthly aggregate snapshot stay free to read and cite. Hiring radar is what they are built from: each role, each day, each change.

Subscription

$25,000

a year, for your firm only, under the Hiring radar licence

Every role open on any day of September 2026 with all its fields, every platform's days in September, the market's days in September, and the first week of the change log. The same files and fields a subscriber receives, sent to your work email.