What an ATS actually rejects
What really breaks resume parsing, and what is just folklore.
ResumeOn TeamResume craft
Most advice about applicant tracking systems is written by people who have never seen one reject a file. The result is a folklore of rules that cost candidates real formatting quality for no benefit.
What genuinely breaks parsing
A handful of things reliably confuse a parser:
- Text inside images. A parser reads text, not pixels. A name rendered as a logo is a name the system never sees.
- Multi-column layouts that are actually tables. Reading order comes from the document structure, not from what your eye does. A two-column layout built from a table can interleave your job titles with your skills list.
- Headers and footers. Some parsers skip them entirely, which is a poor place for your phone number.
- Non-standard section names. "Where I have worked" is charming, but "Experience" is what gets matched.
What does not matter
Plenty of the usual warnings are simply out of date:
| Claim | Reality |
|---|---|
| PDFs get rejected | Text-based PDFs parse fine and are the safest format |
| Any use of colour fails | Colour is ignored by the parser |
| You need exactly one page | Length is a human preference, not a parsing constraint |
The system is not looking for a reason to reject you. It is looking for structured text it can index.
The practical test
Copy your resume, paste it into a plain text file, and read the result. If the reading order still makes sense and nothing has vanished, a parser will manage. If your job titles have detached from their dates, fix the structure rather than the wording.