How Applicant Tracking Systems actually work

What an ATS actually is

An Applicant Tracking System is software that employers use to collect, store and search job applications. Once a company gets more than a handful of applicants for a role — which is almost every role that gets advertised publicly — someone needs a way to keep track of who applied, when, for what, and with what CV attached. That's the whole job of an ATS: a database and search tool for applications, built for recruiters and hiring managers, not a robot making hiring decisions on its own.

Common platforms include Workday, Taleo, Greenhouse, Lever, iCIMS and SmartRecruiters, among many others. Every one of them works slightly differently, which is exactly why "just beat the ATS" advice that treats them as one single system is usually too vague to act on.

How recruiters actually use it

The popular image is a robot instantly binning most CVs before a human ever sees them. The reality is more mundane and, in a way, more useful to know: a recruiter with 200 applications for one role typically searches and filters and sorts. They might search for a specific qualification, filter by years of experience, or sort by how many of the advert's stated requirements each CV appears to match. Some systems do support fully automatic rejection based on hard knockout questions ("Do you have the right to work in the UK?"), but the keyword-matching and ranking most people mean when they say "the ATS" is a search tool a person is driving, not a fully autonomous gatekeeper.

What that means practically: a CV doesn't need to trick an algorithm, it needs to surface clearly and correctly when a real person searches and skims. That's a solvable, concrete problem — very different from trying to outwit a black box.

How the parsing itself works

When you submit a CV, most systems try to extract the text and map it into fields: name, contact details, work history, education, skills. This is where formatting quietly does the most damage. A parser reads roughly in document order, looking for patterns it recognises — standard section headers, consistent date formats, plain running text. It has no concept of a nicely designed two-column layout, a text box, or a decorative header holding your most recent job title. Visually, a human reads that layout easily. Structurally, to a parser, it can come out as fragments in the wrong order, or vanish entirely.

Myth vs reality

The fundamentals, in practice

• Use standard section headers. Experience, Education, Skills — not "My Journey" or "What I Bring". Creative headers stop a parser mapping your content to the right field.
• Avoid tables, columns and text boxes for anything essential. A skills sidebar or a two-column layout is the single most common cause of a CV reading as scrambled or blank to a parser.
• Keep dates consistent. Pick one format ("Jun 2020 – Mar 2024") and use it throughout — mixed formats confuse date parsing and can make a role look shorter than it was.
• Mirror the job description's real language. If the advert says "stakeholder management" and your CV says "cross-functional relationships", say both — once naturally, in context, where it's actually true.
• Quantify your achievements. Numbers do double duty: they're what a recruiter's eye catches when skimming, and they're evidence a system's relevance ranking can weight.
• Don't hide anything essential in an image, header or footer. Logos and photos are invisible to a parser, and content placed in a running header or footer is often skipped entirely.