RoleDawn

Methodology: where the data comes from and how signals are defined

Everything RoleDawn shows is derived from job postings that companies publish on their own public careers boards. This page explains how we collect them, how we classify them, how each signal is defined, how to report a mistake, and what the data cannot tell you. A reason to reach out this week — not proof of budget.

4,481
career pages checked daily
~24h
between re-checks of each board
6
supported ATS platforms
43
role families

Data sources

  • Public applicant-tracking-system (ATS) job boards only: Greenhouse, Lever, Ashby, Workable, Recruitee and Workday. We read the same public job-board endpoints and pages that candidates see.
  • We check 4,481 company career pages every day. On the latest check, 4,417 of them had at least one open role (138,116 open roles in total). The others had no openings posted at the time, or their board could not be read that day; we keep checking them all.
  • We do not scrape LinkedIn or other social networks, and we do not collect or sell personal contact details. Postings are stored at company level: title, department, location, dates and a link to the original posting.
  • Company names come from the organisation name the ATS publishes for the board where available; otherwise from a cleaned-up board name.
  • Our crawler identifies itself as RoleDawnBot and links to its own page. It reads each host's robots.txt before anything else and follows it, sends at most 1 request per second to Lever and at most 2 per second to any other domain, and never crawls sources whose robots.txt disallows it (for that reason we do not use SmartRecruiters).

Crawl frequency

A scheduler runs every 15 minutes and checks the boards that were checked longest ago, so each tracked board is re-read about once a day (at most every 20 hours). Boards that fail five times in a row are retried weekly. Postings that disappear from a board are marked closed. Digests are sent once a day at 13:00 UTC, so an observed signal usually reaches you within one to two days of the posting appearing.

Role-family classification

Each job title (plus its department, when the board provides one) is mapped to one of 43 role families — RevOps, Security, Data Engineering, Hardware and so on — by a deterministic, rule-based classifier. The leading role noun wins over domain words ("Product Manager - AI Finance" is Product Management, not Finance), physical engineering titles (aerospace, mechanical, structural, electrical, civil, manufacturing) are kept out of software families, and titles that do not clearly fit stay in "Other" rather than being guessed.

How the rules are kept honest

  • The classifier is deterministic: the same title always lands in the same family, and the rules are versioned with our code.
  • A set of labelled job titles is part of our automated tests, so a rule change that breaks an earlier case does not ship.
  • Some titles are genuinely ambiguous (for example "Technical Program Manager, Infra" or "Forward Deployed Engineer") and can land in the wrong family. Every signal links to its source posting so you can check it in seconds.

Signal definitions

RoleDawn has read these job boards since 2026-10-05. "New on their board" means the role family had not appeared on that company's board since we started tracking it — not proof the company never hired for it.

New on their board

A role family appears on a board where we had already recorded postings and had never seen that family. It means "first we have seen since we started tracking this board" (our tracking began on 2026-10-05) — not that the company never had such a role. It may have hired before we started tracking it, hired without a public posting, or used a different board.

New on their board · inferred on first read

On a company's first crawl we have no history, so we can only estimate. We infer a new function when the board is established (it has postings older than 60 days, 6–40 open roles across at least 3 families) and the family has only 1–2 roles, all posted in the last 21 days. We do not infer when:

  • the family matches the company's own field (for example security roles at a security company);
  • the family is technical (engineering, data, design, product, IT…) and the board has 15 or more open roles;
  • the posting uses a level such as "II" or "L5", which implies an existing ladder;
  • another posting already sits in a department named after that function, or several other postings mention its domain;
  • the family is general software engineering.

Inferred signals are labelled everywhere. While our tracking history builds, trials include them by default; you can switch them off on any monitor.

Hiring surge

A role family's new postings in the last 30 days are at least double the previous 30 days and at least 3 (or at least 5 when the previous 30 days had none). It counts postings, not hires.

Founding labels. "Job title says "Founding"" and "Job post says "our first …"" quote the company's own words in the job post; RoleDawn does not verify them. A job title that says "Founding" is the stronger of the two; a line such as "our first …" in the description is often generic wording.

A reason to reach out this week — not proof of budget. A posting tells you a company plans to hire for a function. Whether it will buy tools or services, and when, is something you still need to qualify.

Known limitations

  • Coverage: only companies whose boards we track, on the six supported ATS platforms. Companies that hire through LinkedIn, agencies, other ATS platforms or their own careers site are invisible to us. The tracked list leans towards technology companies.
  • History starts when we start: "New on their board" is relative to our own history of that board.
  • Classification errors: some titles land in the wrong family. Unusual, non-English or very short titles are the most error-prone.
  • Posting dates: we use the publish date the ATS provides, or the date we first saw the posting. Some boards re-date reposted roles, and Workday only shows relative dates ("Posted 3 days ago").
  • Postings are not hires: roles can be evergreen, duplicated across locations, paused or never filled. Surges can be inflated by reposts.
  • No financial data: we do not know a company's budget, funding or buying plans.

Corrections

If you see a wrong role family, a wrong signal or a wrong company name, please tell us through the contact form with the company and posting. We fix the rule rather than the single row, re-classify all stored postings, recompute affected signals and add the case to our test set.