Where the data comes from, and what we refuse to collect

Every posting comes from an employer's own public careers page or from the applicant tracking system endpoint that page is built on. Those are pages the employer published in order to be read, and RoleDemand reads them the way a person with a browser would, on a schedule and politely.

The 34 applicant tracking adapters are listed in full on how it works. Each one calls a documented public endpoint belonging to the employer, at a rate limited by a single shared network policy, with a per-domain delay and an identifying user agent.

RoleDemand collects job postings, not people. There is no candidate database, no CV store, no contact scraping and no profile matching anywhere in the pipeline, and nothing behind a login is ever fetched. One qualification worth stating plainly: employers sometimes write a recruiter's email address or a direct phone number into the body of an advert. RoleDemand strips those as the posting is read, before the row is written, so they are not in the database, the export or the dashboard.

Never collected

• Candidate names, contact details, CVs or applications
• Anything behind a login, a paywall or an authenticated API
• Data from a job board that aggregates other people's postings
• Salary figures invented to fill a gap in a posting

Only from structured salary fields the employer published. A salary that is written in prose is parsed later where it can be sanity-checked, and a posting with no salary is reported as having no salary. RoleDemand never estimates a number and presents it as an observation.

A missing salary stays missing. The honest gap is more useful to a consultant than a plausible number, because a consultant who repeats an invented figure in a client meeting is the one who pays for it.

Scoping happens when the dashboard is built rather than when it is requested. Each client's grant is expanded into an explicit list of employers, sectors and modules, and everything outside it is removed before the bundle exists, so there is no filtered view to defeat.

A client grant is an explicit list rather than a wildcard, so adding an employer to the platform later cannot silently widen an existing client's access. An individual account can be narrowed below its agency's grant, never above it.

Every run writes a quality report covering classification coverage, per-employer collection status, circuit-breaker cooldowns, sudden drops to zero and company-name hygiene. A schema mismatch fails the run outright rather than shipping a dashboard with a missing column.

Data health sits on the dashboard itself, where the person quoting the numbers will see it. If an employer's source has been failing for three days, that shows on screen, so you find out before a client does.

Eleven demonstration market packs are seeded in the platform, carrying 250 employers between them, and 34 applicant tracking adapters are available to read them. Those are counts from the repository on 6 August 2026, not a customer base.

The eleven seeded packs carry 250 employers between them, every one of them a real business with a public applicant tracking endpoint that was checked by hand. You can see the list of markets and their sizes on the markets page.

No. RoleDemand is pre-launch and no agency has started a subscription yet. There are no case studies, testimonials or customer logos on this site because there is nothing honest to put in them.

What exists today is the platform: 34 live adapters, 11 seeded markets, a daily automated run, build-time entitlement scoping and a control plane for grants and invitations. What does not exist yet is a customer list. Both statements will stay accurate on this page.