Apr 5, 2026
How an ATS actually reads your resume (2026 edition)
A technical walkthrough of how modern Applicant Tracking Systems parse resumes — and what it means for your formatting.
Most resume advice repeats the same myths: "use plain fonts", "avoid tables", "don't include images". All true. But why? Understanding the parser changes how you write.
What an ATS actually does
An ATS pipeline looks roughly like this:
- Ingest: the file arrives as a PDF, DOCX, or RTF.
- Extract text: PDFs are run through a PDF-to-text engine (usually Apache PDFBox or pdfjs); DOCX files are unzipped and XML-parsed.
- Structure: named-entity recognition pulls out dates, companies, titles, education, and skills.
- Match: your extracted fields are scored against the JD's required skills.
The classic failure modes
- Two-column layouts → the extractor reads across columns, interleaving nonsense.
- Images → silently ignored. If your phone number is in a logo, it's gone.
- Custom glyph fonts → icons render as unicode private-use garbage.
- Headers in a text box → many parsers skip text boxes entirely.
What to do instead
- Single-column. One font. Standard section headings.
- Plain-text phone + email in the header.
- Bullet points, not tables.
- Save as PDF from a text-first editor (Google Docs, Word), not an image tool like Figma or Canva.
Run the free JobFitAI ATS checker to see exactly which of these issues your current resume hits.