What an ATS actually does to your resume

Last updated August 17, 2026

There is a lot of folklore about applicant tracking systems — that they auto-reject anything under a score, that certain fonts fail, that you need a special "ATS-friendly template". Most of it is wrong, and some of it is sold by people with a product to move. Here is what these systems actually do.

What an ATS is

An applicant tracking system is a database. It receives applications, extracts text from the files, stores the results, and lets a recruiter search and filter. Workday, Greenhouse, Lever, iCIMS and Taleo are the common ones.

The important thing: at most companies, a human still decides. The system surfaces and sorts candidates; it very rarely rejects on its own. Where automatic filtering does happen, it is usually on explicit knockout questions — work authorisation, a required licence, minimum years — not on a mysterious score.

What genuinely breaks parsing

The real failure mode is not rejection. It is your text arriving garbled or incomplete, so a recruiter searching for a skill you have does not find you.

• Tables. Cells are frequently read left-to-right across the row rather than down the column, which turns a two-column skills list into one scrambled line.
• Text boxes. Often skipped entirely. Anything inside one may simply not exist as far as the system is concerned.
• Headers and footers. Several major platforms skip them. Contact details placed there can be the one part of your resume that never arrives.
• Multi-column layouts. The visually appealing sidebar templates are the worst offenders — text is often interleaved between columns.
• Images and icons. A skills bar chart parses as nothing at all.
• Scanned or image-based PDFs. No extractable text. This one really can result in an empty application.

What is myth

• "Certain fonts get rejected." No. Use a standard, readable font because humans read it. Any common font parses fine.
• "You need a score above X." There is no universal score. Third-party tools that give you one — ours included — are estimating, not reading the employer's system.
• "PDFs get rejected." A text-based PDF is fine almost everywhere and preserves your layout. Some older systems prefer .docx; if a posting asks for one, send it.
• "75% of resumes are never seen by a human." A widely repeated statistic with no solid source behind it.

A resume that parses cleanly

1. Single column. No sidebar.
2. Contact details in the body of the document, at the top — never only in the header.
3. Standard section headings: Experience, Education, Skills. Clever names like "Where I have made an impact" are not recognised as section markers.
4. Real bullet characters, not decorative glyphs.
5. No tables, text boxes, images or icons.
6. Text-based PDF, or .docx if the posting asks for it.
7. Dates in a consistent format throughout.

That is the entire technical checklist. It is short because the technical part is not where most resumes fail — the writing is.

How to check your own file in ten seconds

Open your resume, select all, copy, and paste into a plain text editor. What you see is approximately what a parser sees.

If your skills come out scrambled, your contact details are missing, or whole sections have vanished, you have found a real problem. If it reads in a sensible order, your file is fine and your attention belongs on the content.