An applicant tracking system is the software employers use to receive, store and process job applications. Here is what every major ATS in 2026 actually does, how to recognise each one from a URL, and what the cottage industry of "ATS optimisation" advice gets right and wrong.
An applicant tracking system - an "ATS" if you've heard recruiters use the acronym - is the software an employer uses to manage their hiring pipeline. When you click "Apply" on a company's careers page and fill out a form, you're submitting to their ATS. When the recruiter reads your CV, sends you a screening invitation, schedules an interview, or sends a rejection email, they're doing it through the ATS. It's the layer between you and the human, and there's a good chance the candidate-side cottage industry of "ATS optimisation" advice has overstated how much that layer actually filters.
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.
The ATS sits across four jobs at once. It hosts the public job postings - the "Careers" page on most company sites is served by the ATS, either embedded in the company's domain or on an ATS subdomain. It receives applications and stores them in a structured database. It manages the recruiter workflow: reviewing CVs, leaving notes, scoring candidates, scheduling interviews, sending templated emails. And it runs the analytics - time-to-fill, source-of-hire, conversion rates between stages, diversity reporting, the whole hiring dashboard.
These are the systems you'll encounter most often as a job seeker. Each has a recognisable URL pattern, which makes them easy to identify from a careers-page link.
URL pattern: *.myworkdayjobs.com or jobs.[company].com with Workday-style filters.
Used by: most large enterprises (Fortune 500, large UK plcs, multinational pharma, banks, professional services firms).
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.
URL pattern: boards.greenhouse.io/[company] or [company].greenhouse.io.
Used by: mid-market tech (Stripe, Airbnb-tier companies historically), Series B to public-company stage startups, modern HR-conscious enterprises.
Applicant experience: light. Short forms, clear stages, sensible defaults.
Public data exposure: excellent. Every public posting has clean JSON-LD structured data, which is why Greenhouse roles appear in Google Jobs fast.
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 data exposure: very good. JSON-LD on every page.
URL pattern: jobs.ashbyhq.com/[company] or [company]/jobs.
Used by: high-growth startups, Series A to C, mostly tech and design-conscious companies. Has been gaining share against Greenhouse and Lever since 2023.
Applicant experience: the lightest of the major ATSes. Short application flows, fewer required fields.
Public data exposure: excellent. Clean structured data and reasonably well-maintained sitemaps.
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.
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.
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.
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: heavy. Often the most friction-laden of any major ATS.
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: dated. Account creation almost always required. Many of the stories candidates tell about "the worst job application experience" refer to a Taleo instance.
The high-level flow when you click "Apply":
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: most modern ATSes do not auto-reject by keyword. Workday, Greenhouse, Lever, Ashby, SmartRecruiters and Phenom all default to surfacing every application to a recruiter. Knockout questions can auto-reject, but those are explicit yes/no fields you fill in.
Myth: "You need a special ATS-friendly CV format."
Reality: a clean, single-column CV with normal text (no images, no text-in-images, no exotic fonts) parses correctly in every major ATS. Heavily designed CVs with two columns, sidebars, or text in image form may parse poorly, which can hurt you if the recruiter relies on the parsed view rather than the original PDF. Use a single-column design, save as PDF, and you're fine.
Myth: "ATSes can't read PDFs."
Reality: every major modern ATS reads PDFs. Some still slightly prefer Word documents, but the difference is marginal.
Reality: keyword overlap with the JD does help, but for the recruiter, not the ATS.
The recruiter is skimming 50 CVs in 20 minutes. If the keywords from the job description are visible in the top third of your CV, you read as "obviously a fit" within 5 seconds. If the same content is buried in a long-form prose paragraph at the bottom, you read as "maybe a fit, I'll come back to this one" and frequently never get the second pass.
The practical implications:
The ATS is less of a gatekeeper than the cottage industry around it would have you believe. It rarely auto-rejects, it reads PDFs fine, and your application is almost always going to a real human who will skim it in under 30 seconds. What matters is whether that 30-second skim lands on the parts of your CV that match what the role asks for - which is a human problem, not an algorithm problem.
The more useful thing to take from this piece is the URL trick. Once you know that Workday means a heavy form and Greenhouse means a light one, that Ashby is well-structured and Taleo is from another era, you can plan your application sessions accordingly - and you can monitor specific employers directly via their ATS rather than waiting for LinkedIn to catch up. Our complete guide to applying early covers the rest of the routine.