An applicant tracking system is a database with a hiring workflow attached. That is genuinely all it is. It stores applications, moves them between stages, and lets recruiters search. It is closer to a CRM than to anything that could be described as artificial intelligence.
Almost every large employer uses one, Workday, Greenhouse, Lever, Taleo, iCIMS, SuccessFactors and a long tail of others. Understanding what they do, and more importantly what they do not, saves a great deal of wasted effort.
What actually happens to your application
1. Your file is parsed. The system extracts text from your PDF or Word document and tries to fill in structured fields: name, email, phone, employers, job titles, dates, education, skills. This is the step that fails, and it fails silently.
2. A candidate record is created. Whatever the parser managed to extract becomes your record. Fields it could not fill are simply empty. Nobody reviews this.
3. A recruiter searches. Faced with several hundred applications, they search for the two or three things that matter, a skill, a title, a location. You appear in those results or you do not.
4. A human reads the shortlist. Everything you have ever read about resume writing applies from here. But only from here.
The myths, ranked by how much damage they do
"The ATS scores you and auto-rejects below a threshold"
Mostly false, and the single most misleading idea in this whole area. Most systems do not score resumes at all. Some offer a match percentage as an optional aid; recruiters routinely ignore it. What removes you is not scoring badly, it is not appearing in a search.
This matters because the myth sends people to optimise the wrong thing. They rewrite their summary to be more impressive when the actual problem is that their employment dates never parsed.
"75% of resumes are rejected by ATS before a human sees them"
This number is everywhere and has no credible source. It is usually traced to a vendor selling resume optimisation. The real figure is unknowable and varies enormously by employer, role and volume.
What is true, and quite bad enough, is that resumes with parsing failures are far less findable. You do not need an invented statistic to justify fixing that.
"You must use a plain .docx, never a PDF"
Out of date. Modern systems handle PDFs well, and a PDF renders identically everywhere, which is a real advantage. The rule that survives is narrower and more important: never send an image. A scanned or flattened PDF contains no text and parses to nothing at all. See PDF or Word for the full picture.
"Put keywords in white text to beat the filter"
Do not. Parsers read the text layer, not the rendering, so hidden text is plainly visible to the system and to anyone who copies your resume into a text editor. It reads as an attempt to deceive, and gets people permanently blocked at companies they wanted to work for.
"Fancy formatting is always fatal"
Overstated. Bold, italics, bullet points, a sensible font and a horizontal rule are all fine and always have been. What breaks parsing is structural: columns, tables holding work history, text in the page margins, and text rendered as an image. A resume can look good and parse cleanly. It just cannot use columns to do it.
What genuinely matters, in order
- Real text, not an image. If you cannot select a sentence with your mouse, the software sees nothing at all. Nothing else matters until this is true.
- One column. The biggest single cause of scrambled parsing.
- Contact details in the body. Not in a header or footer, which many parsers crop before reading.
- Conventional section headings. "Experience", "Education", "Skills". The parser matches on these to file your history.
- Readable dates. "Mar 2021 – Jun 2024". Recruiters filter on years of experience, and a resume with no parseable timeline is excluded from those filters.
- The employer's vocabulary. Search matches words, not meanings.
The first five are binary and cost you nothing to get right. The sixth is the one worth spending real time on, per application, and it is worth nothing until the first five hold.
A useful reframe
Stop thinking of the ATS as a gatekeeper judging you, and start thinking of it as a filing system that has to be able to read your handwriting.
It is not deciding whether you are good. It is deciding whether it can tell what you did and when. Every rule above follows from that, and so does every failure. The ATS checker shows you the filing it produced from your own resume.