How to identify a company's ATS from its careers page
Follow the employer's careers links, inspect the application destination, and record a bounded ATS observation. Includes hosted, custom-site, and inconclusive examples.
The company scenarios are fictional; the provider documentation is real. This is a public-evidence research method, not a new customer dataset or proof of an employer's contract, spending, or complete recruiting stack.
Start from the employer, not a guessed board address
An applicant tracking system observation should begin with a company identity you can verify. Open the employer's official website and follow its careers link to a current job listing. Record the starting page and the route to the application destination. That link chain is stronger evidence of an employer relationship than a board token that merely resembles the company name.
Define the unit you are researching: the parent company, a subsidiary, a regional operation, or one brand. A careers page for one subsidiary may not describe the parent's other businesses. Keep that scope in the record instead of widening the claim later.
Case 1: the official careers page links to a hosted board
In a fictional review, Northline Studio's official careers page links to a Greenhouse-hosted board. The board identifies the same employer, and a current listing leads to a matching application page. The analyst saves the source URLs, the observed employer name, and the review date.
A suitable conclusion is: Northline Studio's public recruiting journey used a Greenhouse-hosted board when checked. That does not establish the contract date, paid plan, recruiter seat count, or whether every region uses the same system. A board can establish a public workflow without revealing the full procurement relationship.
Case 2: the careers page stays on the employer's domain
Fictional Cedar Labs keeps its careers page on its own domain. A researcher initially marks the provider unknown. On a current listing, the visible Apply link leads to an Ashby-hosted application page bearing the same company and job title. The researcher records both pages and narrows the observation to that application flow.
A custom careers domain does not rule out a third-party ATS. Greenhouse documents an API for building custom careers pages from its job-board data. Ashby documents a public posting API with job and application URLs. Those integration options explain why the initial page's hostname alone is insufficient.
When inspecting page source is appropriate, record the particular provider reference and what it does. A live application link is different from an unused script, an analytics tag, or a historical text mention. Do not turn a generic JavaScript filename into a confident vendor claim.
Case 3: the available evidence is inconclusive
Fictional Pebble Studio has a careers page that says to email a resume. A search result also shows an old provider-hosted listing, but the official site no longer links to it and its current status is unclear. The defensible result is unknown for the current public ATS, with the older listing retained as a separate historical lead.
A broken board, no open roles, or a failed request does not prove the employer stopped using an ATS. Nor does a recruiting agency's application form necessarily identify the client employer's system. Record the failure or intermediary and the next verification step rather than filling the gap with an inferred switch.
Use a claim ladder
Write the observation before the conclusion. Keep the evidence narrow enough that another researcher can inspect it and disagree with the interpretation.
| What was observed | Reasonable wording | Unsupported extension |
|---|---|---|
| Official employer link to a matching hosted board | Provider observed in this public recruiting flow on the review date | Company-wide exclusive ATS contract |
| Custom page links to a matching provider application | Provider observed for this application flow | Every internal recruiting function uses that provider |
| Old listing or unexplained script reference | Historical or unresolved provider lead | Current customer, new adoption, or completed migration |
| No confirmed provider in checked sources | Not identified in the reviewed public sources | Employer has no ATS |
Save a reproducible record
At minimum, save the employer and domain, entity scope, official starting URL, board or application URL, provider, review time, supporting observation, and limitations. Keep a source publication date separate from the date you checked it. If you retain a screenshot or excerpt, capture only the public evidence needed to support the claim.
A second reviewer should be able to follow the same public route without submitting an application, entering candidate information, or signing into a recruiting account. If access is restricted, leave that step unresolved. This method does not require collecting applicants' personal data.
Use VendorCensus's ATS directory to inspect its covered sample and source records. Its company lookup searches reviewed observations; it is not a live scan of every employer. The worksheet below helps document your own research without adding an unreviewed company to that dataset.