What is an ATS? Applicant tracking systems explained
An applicant tracking system is software an employer uses to receive and manage applications. Features and settings vary, so this guide separates common functions from claims that every ATS filters candidates in the same way.
An applicant tracking system, or ATS, helps an employer manage job adverts, applications and hiring stages. When you click "Apply" on many company careers pages, the form and later messages are handled through one of these systems. The employer decides which features to enable, so the platform name alone does not reveal exactly how your application will be reviewed.
Worth knowing what your application is actually going through, because the design of the ATS affects two things: how long the application form takes to fill out, and how the recruiter sees your CV on the other side.
What the software actually does
An ATS can host public job postings, receive applications, store candidate records and support recruiter workflows such as notes, stage changes, interview scheduling and messages. It may also provide reporting or optional matching and assessment features. Not every employer buys or configures the same set.
Common applicant tracking systems
These are common systems a job seeker may encounter. Some have recognisable URL patterns, while branded or embedded careers pages can hide the underlying product.
Workday
URL pattern: *.myworkdayjobs.com or jobs.[company].com with Workday-style filters.
Often seen at: large and multinational employers across several sectors.
Applicant experience: heavy. Long forms, frequent "create an account" requirements, multi-step application processes. Workday is built for the recruiter, not the applicant.
Public data exposure: patchy. Some Workday tenants expose JSON-LD structured data; many don't. Our piece on JSON-LD JobPosting covers the implications for monitoring.
Greenhouse
URL pattern: boards.greenhouse.io/[company] or [company].greenhouse.io.
Often seen at: technology companies and other growing employers.
Applicant experience: light. Short forms, clear stages, sensible defaults.
Public job data: public pages commonly expose structured fields that make the vacancy easier for search services to read.
Lever
URL pattern: jobs.lever.co/[company].
Used by: mid-market tech, similar profile to Greenhouse customers. Slightly more design-conscious companies historically.
Applicant experience: light, with cleaner public job pages than Greenhouse.
Public job data: public pages commonly expose structured vacancy fields.
Ashby
URL pattern: jobs.ashbyhq.com/[company] or [company]/jobs.
Often seen at: startups and technology companies.
Applicant experience: often a relatively short application flow, although the employer controls required fields.
Public data exposure: excellent. Clean structured data and reasonably well-maintained sitemaps.
Phenom
URL pattern: often embedded in employer domain (no obvious "phenom" in URL), but visible in the page source.
Used by: large enterprises, especially those who want a branded careers experience layered on top of a recruiter back-end.
Applicant experience: varies wildly by employer customisation. Some are excellent; some are worse than raw Workday.
Public data exposure: good. Phenom often emits richer JSON-LD than the average system.
iCIMS
URL pattern: careers-[company].icims.com or embedded in employer domain.
Used by: traditional large enterprise, especially in healthcare, retail and manufacturing.
Applicant experience: heavy. Often requires account creation.
SmartRecruiters
URL pattern: jobs.smartrecruiters.com/[company] or careers.[company].com.
Used by: mid-to-large enterprises, particularly with European HQs (the company was originally European).
Applicant experience: medium. Clean enough, not as light as Greenhouse or Ashby.
SAP SuccessFactors
URL pattern: career[X].successfactors.com or embedded in employer domain.
Used by: large traditional enterprises, especially those running SAP for the broader HR stack.
Applicant experience: can involve account creation and several steps, depending on the employer.
Oracle Taleo
URL pattern: URLs containing taleo in some form.
Used by: a decreasing share of large enterprises, mostly those running Oracle HCM. Considered legacy by 2026 but still widely deployed.
Applicant experience: can feel dated and may require account creation, depending on the employer's setup.
How an ATS actually processes your application
The high-level flow when you click "Apply":
- Form ingestion. Your input goes into a structured database. CV gets parsed (with varying accuracy) into structured fields: name, contact, work history, education.
- Knockout questions. If the role has knockout questions ("Are you eligible to work in the UK?", "Do you have 5+ years of Java experience?"), applicants who answer "no" can be auto-disqualified. This is the closest thing to "the ATS rejecting you", and it's based on your explicit yes/no answers, not on CV parsing.
- Optional matching or scoring. Some employers enable tools that help search, summarise, match or rank applications. Their use and effect vary by vendor and employer.
- Recruiter review. The application lands in the recruiter's queue. They review in order (with the exceptions covered in our piece on review order).
- Stage progression. If shortlisted, the application moves through stages (screen, technical, on-site, offer). Each stage has its own status, communication templates, and timeline.
The myths and realities of "ATS optimisation"
There's a cottage industry of "ATS-friendly CV" advice that overstates how much the ATS itself filters. Here's what's true and what isn't.
Myth: "The ATS will reject your CV if it doesn't match keywords."
Reality: a missing keyword does not prove that software rejected you. Employers can use explicit screening questions, recruiter searches, matching tools or manual review, and the configuration is rarely visible to applicants.
Myth: "You need a special ATS-friendly CV format."
Reality: a clear, single-column CV with selectable text reduces avoidable parsing problems. Complex columns, sidebars or text stored in images can be harder for some systems to interpret. Follow the employer's requested file type rather than assuming one format works everywhere.
Myth: "ATSes can't read PDFs."
Reality: many systems accept PDFs, but the vacancy form is the authority. Use the requested file type and check that the uploaded preview or extracted fields make sense.
Reality: keyword overlap with the JD does help, but for the recruiter, not the ATS.
A recruiter needs to find the relevant evidence quickly. Use the language of the job description where it truthfully describes your work, and put the strongest matching evidence where it will not be buried in a long paragraph.
What this means for your application strategy
The practical implications:
- Verify and apply through the employer's source page where possible. It gives you the current requirements and avoids assuming how an external platform routes the application. Our comparison of LinkedIn, Indeed and direct applications covers the friction trade-off.
- Don't dread the heavy ATSes (Workday, Taleo, SuccessFactors). Yes, the forms are long. The application is still going to a real recruiter who will read it. Get through the form once, save your account, and reuse it for future applications at the same company.
- Use the URL to identify the ATS in advance. If you're applying to many roles, knowing whether you're about to fill in a 5-field Greenhouse form or a 40-field Workday form lets you batch the latter into a single session.
- Watch the canonical ATS for new roles directly. Direct careers-page monitoring beats aggregator alerts on freshness; for early-stage and YC companies, our piece on early-stage startup jobs covers the channels that surface roles even faster.
What matters in practice
An ATS is not one universal robot gatekeeper. It is configurable hiring software, and the employer's process determines whether your application meets an explicit screen, appears in a search or reaches a recruiter in time. Make the relevant evidence easy to find and do not build a CV around guessing an invisible score.
Recognising the careers platform can help you estimate the application steps and find the employer's source page again. Monitoring that source matters because a suitable role found before the wider applicant queue builds has a real visibility advantage. Our guide to applying early covers the rest of the routine.