How to format a resume an ATS can actually read

Before any person judges the content of your resume, software has to turn it into structured text. If that step fails, nothing else matters: your job title merges into the company name, your phone number disappears, your 2023 role gets attached to 2019. And there is no error message — you simply never surface in the recruiter's search.

The good news is that formatting is the most controllable part of the whole process. This guide covers the decisions that actually matter to the parser, ordered by how often they cause trouble.

1. Use a single column, always

Two-column layouts are problem number one. The parser reads the document in the order elements were inserted, not the order you see them. A resume with "Skills" on the left and "Experience" on the right can be extracted as a nonsensical interleaved sequence — skill, title, skill, employer.

If you love the column look, keep it for the version you email directly to a hiring manager and use a linear version for portal applications. One column never hurts human readability; two columns often hurt machine readability.

2. Keep information out of headers and footers

Page headers and footers — the ones that repeat automatically — live in a separate document layer, and many parsers ignore them entirely. That is the origin of the classic "I sent my resume and the recruiter said there was no phone number".

• ✓Name, phone, email, city and LinkedIn in the body of the document, in the first lines.
• ✓No text boxes for contact details.
• ✓No page numbering in a footer that also carries relevant information.

3. Predictable section headings

The parser looks for known labels to know where each block starts. "My journey so far" is charming, but the system has no idea that block is work experience. Use standard names:

4. Month/year dates, reverse chronological

Write `01/2023 – 08/2025` or `Jan 2023 – Aug 2025`. Avoid year-only ranges (the system cannot compute duration), avoid prose ranges ("from early 2023 to mid 2025"), and avoid putting the date on the same line as the title separated only by whitespace — use a clear delimiter.

For your current job, write "Present" rather than leaving the range open. Many parsers need an end marker to close the period.

5. Font, size and file type

• ▸Font: any common, readable typeface — Arial, Calibri, Helvetica, Lato, Verdana. What matters is standard glyphs; decorative fonts can export as artwork.
• ▸Size: 10 to 12 pt for body text, 14 to 16 pt for headings. Below 10 pt you hurt human readability and gain nothing.
• ▸File: a text-based PDF. Confirm by opening it and trying to select a word — if you cannot, it is an image and the parser reads nothing.
• ▸DOCX: also safe, and sometimes preferred by older portals. If the posting requests a specific format, follow the request.

6. Charts, icons and proficiency bars

Those "Spanish ▮▮▮▮▯" bars carry no information for the system — and honestly none for the human either, since there is no defined scale. Replace them with text: "Spanish — advanced (C1), used in client meetings and technical documentation."

The same goes for icons replacing labels. A phone glyph before your number is decorative; the parser needs the textual context, and so do screen readers.

7. Do not forget who reads it next

Clearing the parser is the first filter, not the goal. Ladders' 2018 eye-tracking study measured how long recruiters spend on an initial screen: 7.4 seconds on average. In that window their gaze goes to the current title and employer, then the previous one, then the dates — checking progression.

The study's practical conclusion matches what the ATS needs: simple layouts, clear sections, bold headings and bulleted accomplishments performed best. Machine-readable formatting and 7-second-readable formatting are, conveniently, the same thing.

Final checklist before you send

• ✓Single column, no text boxes, no tables used for layout.
• ✓Contact details in the document body, not in a page header.
• ✓Standard section names.
• ✓Month/year dates, reverse chronological, "Present" on the current role.
• ✓PDF with selectable text (test: select all, paste into a plain text editor).
• ✓No proficiency charts, no photo unless the posting asks for one.
• ✓Title and employer visible in the first 7 seconds of reading.