ATS Parsing Rules: How Fonts, Columns, and Headers Decide Whether Your CV Gets Read

Applicant tracking systems do not read your CV. They parse it. Those are two different things, and the difference explains why a CV that looks beautiful in Google Docs can score zero in a recruiter's search results.

This guide breaks down exactly how ATS parsing works, and the three layout decisions that quietly destroy more applications than any other mistake.

What parsing actually means

When you upload a CV, the ATS runs a text extraction step. It opens the PDF or DOCX, reads through it the way you would scan a page, and tries to split the content into structured fields:

• Name and contact
• Work experience (with employer, title, dates, bullets)
• Education
• Skills
• Certifications

A strong parser succeeds 95% of the time on a clean CV. A weak parser succeeds 60% even on a perfect document. You do not get to choose which parser the recruiter uses. So the rule is: design for the weakest parser, not the smartest one.

The failure modes are silent. Nothing tells you the parser missed your title. The recruiter searches Senior Backend Engineer, your role gets parsed as a paragraph blob, and you never appear in the results.

Rule 1: fonts that parse cleanly

Fonts are the most common silent killer. PDF parsers extract glyphs and map them back to characters. With most fonts this works. With a few, characters arrive scrambled, ligatured, or missing.

Fonts that parse cleanly (use these)

• Arial, Helvetica, Inter — modern sans-serifs, universally supported
• Calibri, Source Sans Pro — clean defaults for most CVs
• Times New Roman, Georgia — serifs that parse without surprises
• Lato, Open Sans, Roboto — popular sans-serifs with full character maps

Fonts that cause parser failures

• Decorative or display fonts (Comic Sans, Pacifico, anything novelty) — many parsers cannot extract them
• Custom or webfonts without embedded character maps — text shows visually but extracts as gibberish
• Stylised numerals (1 rendered as a glyph, not a character) — common in oldstyle font variants
• Icon fonts for skill badges or section markers — extracts as random characters or nothing

Practical settings

• Body text: 10 to 11 pt
• Section headers: 12 to 14 pt
• Name: 14 to 18 pt
• Line height: 1.15 to 1.4
• No condensed weights (Calibri Light Condensed causes issues)
• No more than two font families in the entire document

Quick test

Open your PDF and select-all the text, then paste into a plain-text editor (Notepad, TextEdit). What you see there is what the parser sees. If anything is scrambled, missing, or out of order, fix the font or the layout.

Rule 2: columns are the second silent killer

A two-column CV looks elegant. It is also the single most common reason a strong candidate's CV scores zero in the ATS.

Here is why. Most parsers read the page in linear order, line by line, left to right. With a two-column layout, the parser reads across both columns instead of finishing the left column first. The result:

```

Name: Maria Chen | Python (advanced)

Title: Senior Engineer | SQL (advanced)

Email: maria@... | AWS (5 years)

Experience | Skills

Acme Corp 2022-Present | Languages

Led migration of payment service | English, Spanish

```

From the parser's view, your name is Maria Chen | Python (advanced), your title is Senior Engineer | SQL (advanced), and your experience becomes garbled.

Some modern parsers detect columns and handle them correctly. Many do not. Greenhouse, Lever, and Workday — the three most common ATSs in 2026 — handle two-column CVs inconsistently. Some templates work, others fail catastrophically.

The fix

Use a single-column layout for the entire CV. If you want visual variety, achieve it with:

• Bold text for emphasis
• A horizontal rule between sections
• Generous white space
• A clearly larger font for the name and headers

Do not use:

• Sidebars for contact info or skills
• Two-column experience sections (job title left, company right)
• Three-column skill grids
• Text wrapped around an image

You can still ship a beautiful CV. You just cannot ship a multi-column one.

Rule 3: headers and footers are dangerous

Many CV templates place name and contact info in the document's header region (the printable header zone, not a styled Header paragraph). Parsers handle this poorly.

In the worst case, the parser ignores the entire header region. Your contact details disappear. The recruiter never sees your email. Your application is filed under unknown applicant.

In the second-worst case, the parser extracts the header but appends it to the end of the parsed text, scrambling field mapping.

The fix

Put your name, title, email, phone, LinkedIn, and location in the body of the document, in the first few lines. Not in a Word header. Not in a Google Docs header. Not in a banner image with text rendered on top.

Same goes for the footer. Page numbers, watermarks, dates — keep them out, or accept that the parser may either ignore them or insert them mid-paragraph.

Three other layout choices that affect parsing

Tables

Tables for skills, dates, or experience often parse as one giant cell or get scrambled. Bullet lists work better. If you must use a table (e.g., for a quick-glance skills matrix), use a single-cell layout and avoid grids.

Text boxes and shapes

Text inside a text box, shape, or SmartArt element often gets ignored entirely. The parser treats it as an image. If your CV uses a coloured banner with text rendered inside it, all that text may be invisible to the ATS.

Images and icons

No image carries text. Even a high-resolution PNG of your headline is invisible to the parser. Avoid:

• Profile photos (a separate problem in some regions — see local norms)
• Icon sets for contact info (use the literal word Email: instead)
• Skill level graphics (5-star ratings, progress bars)
• Company or university logos

If the recruiter wants to see your photo or your logos, your LinkedIn is one click away.

The cleanest ATS-friendly CV layout

```

Maria Chen

Senior Backend Engineer

maria.chen@email.com | +44 7700 900000 | linkedin.com/in/mariachen | London, UK

Summary

[Three lines.]

Skills

Languages: Python (advanced), Go (intermediate), TypeScript (intermediate)

Infrastructure: AWS (Lambda, RDS, S3), Docker, Terraform, GitHub Actions

Data: PostgreSQL, Kafka, dbt

Experience

Acme Corp — Senior Backend Engineer, Jan 2022 to Present

• Bullet one with outcome and number.
• Bullet two with outcome and number.
• Bullet three.

Beta Inc — Backend Engineer, Mar 2019 to Dec 2021

• Bullet one.
• Bullet two.
• Bullet three.

Education

University of Manchester — BSc Computer Science, 2018

Certifications

AWS Solutions Architect Associate, 2024

```

Single column. Standard font. Name in the body, not the header. No tables, no icons, no graphics. Every field parses cleanly.

How to actually test ATS parsing

Do not trust a CV template's marketing copy that says ATS-friendly. Test it.

Free options

• Resume Worded ATS scan — shows you how a parser sees your file, flags issues
• Jobscan — paste a job description and see keyword coverage in the parsed output
• Greenhouse practice upload — many companies hosted on Greenhouse let you upload before applying. The parsed preview shows you exactly what they see.
• Lever apply flow — same idea, shows parsed preview before submission

The plain-text test

The simplest test. Open your PDF. Select all. Copy. Paste into Notepad or TextEdit. Read the result.

If the text comes through:

• In the right order
• With your name and contact at the top
• With section headers visible
• With no scrambled characters
• With no missing chunks

It will probably parse correctly in most ATSs. If anything is wrong, the parser sees the same wrong version.

File format: PDF or DOCX?

In 2026 the answer has stabilised: PDF is fine in 90% of cases, DOCX is safer in the remaining 10%.

Use PDF unless:

• The job application explicitly asks for Word format
• You know the company uses Taleo (an older ATS that prefers DOCX)
• You are applying through email and want to make commenting easier

Keep both versions on hand. Same content, exported from the same source document.

Never submit:

• Scanned PDFs (text-as-image, invisible to the parser)
• Pages files (.pages) — many ATSs reject the format entirely
• ZIP files containing the CV
• Files with special characters or spaces in the name (use Maria-Chen-CV.pdf, not Maria's CV (final) v3.pdf)

Six layout mistakes that quietly tank your CV

1. Two-column layout. The number one parsing destroyer.
2. Contact in the header zone. The number two parsing destroyer.
3. Decorative fonts. Especially Comic Sans, but also anything custom or downloaded.
4. Icons replacing text labels. Email, Phone, LinkedIn are words. Icons are pictures.
5. Skill rating graphics. Stars, bars, dots — invisible to the parser, mistrusted by recruiters anyway.
6. Photos. ATS-blind, sometimes legally awkward in the US and UK, and they take up space.

What to do right now

1. Open your current CV
2. Copy all the text into Notepad
3. Look at what the parser sees
4. If anything is wrong, rebuild the document in a single column, with a standard font, with contact in the body, with no tables or icons
5. Re-test

This 30-minute exercise has more impact on your callback rate than any cover letter tweak. The ATS is the first interviewer. Pass that interview first.