The resume checklist that decides whether a parser can read you

Applicant tracking systems do not reject people; they lose them. A resume that parses badly is stored as fragments, and the recruiter searching for "PostgreSQL" or "charge nurse" never sees your file. Everything on this list is verifiable on your own document in a few minutes.

1. Use one column for the main content

Sidebars look efficient on screen and read as interleaved text in extraction. A two-column layout can turn "Skills" and "Experience" into alternating lines, which is unrecoverable downstream. Keep contact details, summary, experience, education, and skills in a single column and move colour and typography into the styling instead.

2. Keep headings as plain text

A section titled with an image, an icon, or letter-spaced decorative type may not extract as the word "Experience" at all. Plain headings — Experience, Education, Skills — are what parsers map for section detection.

3. State dates as month and year, consistently

Use one format for every role: "Mar 2022 – Present". Mixed formats (2022, 03/22, Spring 2022) are the most common source of a wrong tenure calculation. If your exact start month is not memorable, pick the month you signed the contract and keep it consistent.

4. Put each contact detail on its own line or in one clear block

Name, email, phone, city, and one link. Avoid putting the phone number inside a header image or a text box, and do not split the email across two lines to fit a design.

5. Use a real skills list, one item per entry

Skill bars, dot ratings, and tag clouds may extract as one unbroken string. Write "PostgreSQL" and "React" as separate list items. Ratings ("Excel — 4/5") carry no meaning to a parser and little to a human.

6. Mirror the posting’s vocabulary

If the posting says "stakeholder management" and your resume says "worked with teams", a keyword search for the former returns nothing. Use the employer’s term where it is also true of your work; do not paste the job description.

7. Avoid tables for anything that matters

Tables are the classic extraction failure: cells are often read row by row, so a two-column table of "Skill | Level" becomes a single meaningless line. If you need a table for layout, keep no content in it that a recruiter would search for.

8. Never put text in the header or footer of the page

Running headers and footers usually live outside the text frame. Contact details placed there frequently vanish. Keep every fact inside the body text.

9. Keep the file name boring

First-Last-Resume.pdf beats final_FINAL_v3.pdf. It survives upload systems that display the filename in a list, and it is one less thing to explain at an interview.

10. Export to PDF unless the form asks for Word

A text-based PDF preserves layout and stays selectable. A scanned or image-only PDF contains no text at all. If a form asks for .doc or .docx, send that instead — the requirement outranks the convention.

11. Test the actual file, not the editor

Open your exported PDF and try to select a sentence in each section. If the text can be selected and copied, a parser can usually read it. If selection produces nothing, the file is an image.

12. Reduce before you add

Every extra font, icon set, and decorative rule is another way the layout can break. The strongest resumes in a pile are usually the plainest ones with the most specific content.

Questions about this page

Can a resume be rejected by an ATS automatically?
Some systems apply knockout questions — work authorisation, licence, location — but those come from the application form, not the resume. What the resume controls is whether your facts are extracted and searchable.
Does a photo break ATS parsing?
It can consume the space where contact details sit, and it is not required in most markets. If you include one, keep it out of the text flow — and leave it out entirely for US and UK applications.
Is a two-page resume a parsing problem?
No. Length is a readability question, not a parsing one. Two pages parse fine; a second page of repeated frameworks does not get read.
How do I know my resume passes?
Extract the text yourself, check that headings, dates, and skills survive as separate items, and score the document for parse safety, completeness, and impact before you apply. The free checker on this site runs the same analysis the editor uses.