ATS resume format: what actually parses cleanly

Most advice about applicant tracking systems is either scaremongering or folklore. Here is what these systems genuinely struggle with, and the format that avoids the problem.

What an ATS actually does

An applicant tracking system is a database with a parser attached. When you upload a resume, the parser tries to work out which lump of text is your name, which is a job title, which is a date range. It writes those into fields. A recruiter then searches or filters those fields.

Nothing in that process is magic, and nothing in it is malicious. Resumes get mishandled when the parser guesses wrong — and it guesses wrong when the document's visual structure and its underlying text structure disagree.

The things that genuinely break parsing

• Text inside images. A parser reads text, not pictures. A name rendered as a logo is invisible to it.
• Tables used for layout. Some parsers read a two-column table row by row, so "Software Engineer" and "2019–2023" from different columns get glued into nonsense.
• Text boxes and floating shapes. Common in Word templates. Content inside them is often skipped entirely.
• Headers and footers. Put your phone number only in the footer and it may never be read. Keep contact details in the body.
• Unusual section names. "Where I've Been" is charming; "Work Experience" is findable.

What does not break parsing

Plenty of feared things are fine. Colour is fine. A second page is fine. Bold and italics are fine. Bullet points are fine. A sensible sans-serif or serif font is fine. A modest amount of visual design is fine, as long as the reading order underneath is linear.

A format that works

1. Name and contact details at the top, as ordinary text: name, email, phone, city, and one link.
2. A short summary — three or four lines saying what you do and at what level.
3. Work experience, most recent first. For each role: job title, employer, location, and a date range on its own line or clearly beside the title.
4. Education, with qualification, institution and year.
5. Skills, as a comma-separated list rather than a grid of rating stars.

Two columns are not forbidden, but they are a risk you take on for the sake of appearance. If you use one, keep the main chronology in the wide column and put only short items — skills, languages, certifications — in the narrow one.

File type

Submit a PDF unless the application form says otherwise. A PDF generated from a text document keeps its text layer and parses well. The exception is a PDF exported as an image, or one produced by scanning, which contains no text at all.

Some employers still ask for .doc or .docx. If they do, send that — an instruction on the form beats general advice every time.

How to check yours

Open your PDF and try to select the text with your cursor. If you cannot select your own name, no parser can read it either. Then copy the whole document and paste it into a plain text editor: what you see is roughly what the ATS sees. If the order is scrambled, your layout is fighting the parser.

Common questions