There's a piece of advice doing the rounds that I need to correct: the idea that Applicant Tracking Systems are ruthless robots silently binning 75% of CVs before a human ever sees them. I've worked with these systems for years. That's not what they do.
The myth has become an industry in itself. Whole businesses exist to sell you "ATS-beating" templates and "keyword optimisation" services built on a picture of how these systems work that's mostly wrong. And because the picture is wrong, some of the advice actively harms your application.
So let me tell you what an ATS actually is, what it does and doesn't do, and where you should actually spend your effort.
In short: An Applicant Tracking System (ATS) is a searchable database that stores and organises job applications — not an AI gatekeeper that auto-rejects CVs. Most systems reject no one automatically. Candidates disappear when their CV parses badly or lacks the terms a recruiter searches for, so they never surface in the results. The fix is a clean, single-column layout and honest, accurate language that matches the job description.
What Is an ATS, Really?
An ATS is a database. That's the honest description. It's software recruiters and employers use to collect, store, and organise applications. When you apply through a company careers page and upload your CV, it lands in an ATS, which parses the document into structured fields — name, contact details, work history, skills — so I can search and filter across hundreds of candidates.
It is not an AI gatekeeper that reads your CV, judges your worthiness, and rejects you automatically. Most systems don't auto-reject anyone. The scary "75% of CVs are rejected by ATS before a human sees them" statistic gets repeated everywhere, and nobody can ever point me to its source. It doesn't match what happens on my side of the screen.
Here's what actually happens. I receive the applications. I run searches and filters inside the ATS to find candidates who match the role. If your CV parsed cleanly and contains the terms I'm searching for, you show up in my results. If it parsed badly, or you're missing the language I'm looking for, you don't — and that's where good candidates genuinely disappear.
The rejection isn't automated. It's that you never surfaced in the first place.
Where Do CVs Actually Fail in an ATS?
The real failure points are mundane, which is precisely why nobody sells a product to fix them. Two things go wrong.
The first is parsing. If the system can't read your document properly, the information ends up in the wrong fields or gets lost entirely. This is the same problem I described in the foundation article — contact details buried in headers that vanish, two-column layouts that scramble, tables that turn your neat work history into gibberish. When the parse fails, your CV is technically in the database, but it's a mess, and you won't come up cleanly in a search.
The second is relevance. When I search the database for a role, I'm using terms — job titles, skills, systems, qualifications. If I'm looking for someone with warranty administration experience and your CV only ever says aftersales support, you may well have exactly the right background and still not appear in my results. I'm not searching for the thing you called it. I'm searching for the thing the job needs.
Neither of these is a robot judging you. Both are fixable without buying anything.
Why Keyword Stuffing Backfires
This is where the bad advice does real damage. Told that an ATS "scans for keywords", people go one of two ruinous directions.
Some stuff their CV with every term from the job description, sometimes in white text hidden at the bottom of the page — an old trick that recruiters spot instantly and that most systems now flag anyway. When I catch it, the application goes straight in the bin. It reads as dishonest, and honestly, it's insulting.
Others cram keywords in so densely the CV stops making sense to a human being. Remember: even if the terms help you surface in my search, a person reads the document next. A CV that's clearly been written for a machine reads as exactly that, and it fails the moment I open it.
Keywords matter, but not the way the mythology suggests. The goal isn't density. It's accuracy — describing what you actually did using the language the industry actually uses.
How Do You Actually Optimise for an ATS?
Forget beating the system. Work with how it genuinely functions.
Use the job description as a mirror. Read it properly. Note the exact terms it uses for the skills, systems, and responsibilities the role needs. Where your genuine experience covers those things, make sure your CV uses recognisable versions of that language — not copied verbatim, but aligned. If the advert says stakeholder management and you've spent five years doing exactly that under a different label, adopt the term they'd search for.
Keep the parse clean. Single-column layout. Standard section headings — Summary, Skills, Experience, Education — because that's what the parser is built to recognise. No tables, no text boxes, no graphics carrying essential information. Contact details in the body. Save as a standard Word document or PDF, and if the application form specifies a format, follow it.
Don't invent a keyword strategy for things you haven't done. If the role needs a skill you lack, no amount of optimisation fixes that, and you don't want the interview you'd get by faking it. Aim your applications where your genuine experience matches the language of the role.
Fill the obvious fields. Job titles, dates, employers, a clear skills section. The parser is looking for these. Give it what it expects and it does its job.
A Quick Reality Check
Take a job description for a role you'd genuinely be suited to. Read it beside your CV.
Do the core skills it names appear somewhere in your CV, in language a recruiter would actually search? Are your job titles clear and standard, or have you got a creative internal title like Customer Happiness Ninja that nobody will ever type into a search box? Is the document clean enough to parse without scrambling?
If your titles are opaque, add a plain-language equivalent in brackets. If the core terms are missing and your experience genuinely covers them, put them in. If the layout is fighting the parser, simplify it.
That's the whole job. Not defeating an algorithm — just making sure the database can read you and find you.
Frequently Asked Questions
Do ATS systems automatically reject CVs?
No. The vast majority of Applicant Tracking Systems don't auto-reject anyone. They store and organise applications so recruiters can search and filter them. Candidates get missed when their CV parses badly or doesn't contain the terms a recruiter searches for — not because software rejected them.
Is it true that 75% of CVs never reach a human?
This widely-repeated figure has no credible source, and it doesn't match how recruiters actually work. A recruiter still reviews the candidates who surface in a search. The real risk isn't automated rejection — it's failing to surface in the search at all because of a bad parse or missing keywords.
Should I hide keywords in white text to beat the ATS?
No, never. Recruiters spot this instantly and most systems flag it. It reads as dishonest and gets applications binned on sight. Use accurate, visible language that reflects what you've genuinely done.
What CV format is safest for an ATS?
A single-column layout with standard section headings (Summary, Skills, Experience, Education), contact details in the body rather than the header, and no tables, text boxes, or graphics carrying essential information. Save as a standard Word document or PDF unless the application specifies otherwise.
How many keywords should I put in my CV?
There's no target number, and density is the wrong goal. Aim for accuracy: use the terms the job description uses for skills you genuinely have. If the advert says "stakeholder management" and you've done exactly that under another label, adopt the term a recruiter would search for.
The ATS isn't your enemy, and it isn't a wall between you and the job. It's a filing system. Most of the advice that treats it as a sentient gatekeeper is selling you a solution to a problem that doesn't exist, while the real issues — clean parsing and honest, accurate language — go unmentioned because there's no product in them.
If you want to know whether your CV reads cleanly and uses the right language for the roles you're targeting, the CV Optimiser review service checks exactly that — how your CV parses, and whether it surfaces for the roles you actually want.