How applicant tracking systems really work (and what actually gets you filtered)
An ATS is a database, not a robot judge. Understanding what it actually stores explains every real formatting rule.
There is more folklore about applicant tracking systems than about any other part of job hunting. White text stuffed with keywords, secret rejection algorithms, magic file names. Almost none of it is true. What is true is duller and more useful.
What an ATS actually is
An ATS is a database with a parser attached. When you upload a resume it extracts text, guesses which chunk is a job title, which is an employer, and which is a date, then files those fields against your candidate record. Recruiters later search that database the way you would search a spreadsheet.
That is the whole mechanism. There is rarely an automatic reject. What there is instead: a recruiter typing 'VMware' into a search box and never seeing the 200 candidates whose resumes did not contain the word.
The failures that actually happen
- Multi-column layouts that interleave text from two columns into one unreadable stream.
- Job titles or dates inside text boxes, headers or footers that the parser skips entirely.
- Skills rendered as an image, a chart, or a five-dot proficiency rating.
- Tables used for layout, which can scramble reading order.
- Non-standard section names — 'Where I've Been' instead of 'Experience'.
The rules that follow from that
- Single column. Always. Design flourishes cost you more than they gain.
- Standard headings: Summary, Skills, Experience, Education, Certifications.
- Reverse chronological order with consistent MM/YYYY date formats.
- Real text, never images of text. Export a text-based PDF, not a scan.
- Spell out an acronym once and pair it with the abbreviation: 'Active Directory (AD)'.
Keyword stuffing does not work
Hidden white-text keyword blocks are trivially visible when the parser dumps text into the database, and they read as fraud to the human who eventually looks. Worse, they get you surfaced for searches you cannot survive a phone screen on. Put keywords where they are true: in the bullet describing the work you did with that tool.
File format
A text-based PDF is safe with every mainstream system in use today. If a specific application portal explicitly asks for .docx, give it .docx. Never send a scanned or exported-as-image PDF — that is the one format that genuinely produces an empty candidate record.
The practical takeaway
Design for the parser, write for the human. A boring single-column resume with the posting's exact terminology beats a beautiful two-column one that gets stored as gibberish.