Resume Formatting Disasters ATS Systems Can't Parse

I’ve reviewed 10,000+ resumes in my 12 years recruiting for Microsoft, Salesforce, and Stripe. Here’s what no one tells you: 75% of resumes never reach a human. They die in the ATS.

Not because candidates aren’t qualified. Because their resumes are formatted wrong.

Two-column layouts? ATS reads them as gibberish. Custom section headers like “Professional Journey”? ATS skips them entirely. PDFs with embedded images? Parsing failure.

The system is stupid. But it’s the system. And if you want the interview, you need to speak its language.

This is the hall of shame. The formatting disasters I’ve seen kill thousands of qualified applications. If your resume has any of these, fix it today.

Disaster #1: The Two-Column Resume

What it looks like:

[Left Column]           [Right Column]
- Contact info          - Work Experience
- Skills                - Education
- Certifications        - Projects

Why ATS can’t parse it: ATS systems read left to right, top to bottom. When you split content into two columns, the ATS tries to read across both columns simultaneously. It ends up with:

“Contact Skills Certifications Work Experience Education Projects”

Your work experience bullets get mashed together with your skills list. Your job titles disappear. The ATS thinks you worked at “Python, JavaScript, React” instead of “Senior Developer at Google.”

The fix: Single-column layout. Always. No exceptions.

Even if it looks “boring” to you, it’s readable to the ATS. And the ATS decides if a human ever sees it.

Disaster #2: Custom Section Headers

What people write:

“Professional Journey” (instead of “Work Experience”)
“Career Highlights” (instead of “Summary”)
“Core Competencies” (instead of “Skills”)
“Academic Background” (instead of “Education”)

Why ATS can’t parse it: ATS systems are looking for specific section headers: Work Experience, Education, Skills, Certifications. When you get creative, the ATS doesn’t know where to file your information.

Your entire work history gets categorized as “Uncategorized Text.” The ATS can’t extract your job titles, companies, or dates. You score zero for relevant experience.

The fix: Use standard headers. Verbatim:

Work Experience (not Professional Journey, not Career History)
Education (not Academic Background)
Skills (not Core Competencies, not Technical Proficiencies)
Certifications (if applicable)

Boring wins. Creative loses.

Disaster #3: Tables for Formatting

What it looks like: People use tables to create clean alignment:

Position	Company	Dates
Senior Developer	Google	2020-2023

Why ATS can’t parse it: ATS systems don’t read tables. They see the content, but they can’t extract the structure. Your job title, company name, and dates all get jumbled into one text blob.

The ATS can’t tell what you did, where you did it, or when. It reads:

“Senior Developer Google 2020-2023”

And files it as unstructured text. Zero parsing success.

The fix: Use plain text with line breaks:

Senior Developer
Google | 2020-2023

Simple formatting. Clear hierarchy. ATS-readable.

Disaster #4: Text Boxes and Graphics

What people do:

Put their name in a fancy text box at the top
Add a sidebar with a skills bar chart (5 out of 5 stars in Python!)
Include a headshot or company logos
Use graphic design elements for “visual appeal”

Why ATS can’t parse it: Text boxes are images to ATS systems. Graphics are invisible. The ATS literally can’t see them.

If your name is in a text box, the ATS thinks your resume has no name. If your skills are in a graphic, the ATS thinks you have no skills. Your resume gets flagged as incomplete.

The fix: Remove all graphics, text boxes, and images. Use plain text only.

Your name should be typed text (not in a box). Your skills should be a bulleted list (not a chart). Your contact info should be standard text (not in a footer graphic).

Disaster #5: Headers and Footers

What people put there:

Name and contact info in the header
Page numbers in the footer
“References available upon request” in the footer

Why ATS can’t parse it: Most ATS systems ignore headers and footers entirely. They’re designed to skip page metadata.

If your contact info is in the header, the ATS thinks you didn’t include it. If your name is only in the header, the ATS doesn’t know whose resume it’s parsing.

The fix: Put all critical information in the body of the resume:

Name at the top of the first page (body text, not header)
Contact info immediately below name (body text)
No page numbers needed (ATS doesn’t care)
No “References available upon request” (recruiters assume this)

Disaster #6: PDF with Embedded Fonts

What happens: You use a custom font (Garamond, Futura, etc.) to stand out. You save as PDF to “preserve formatting.” The PDF embeds the font.

Why ATS struggles: Some ATS systems can’t extract text from PDFs with embedded fonts. They see the file, but they can’t read it. Your resume shows up as blank or corrupted.

Even if the ATS can read it, custom fonts sometimes get misinterpreted. An “I” (capital i) looks like an “l” (lowercase L). Your job title “Senior Analyst” becomes “Senlor Ana1yst.” The ATS keyword matching fails.

The fix: Use standard fonts only:

Arial
Calibri
Times New Roman
Georgia

These are universally readable. ATS systems are optimized for them.

Save as .docx if possible. If you must use PDF, stick to standard fonts and test your resume through an ATS parser before submitting.

JobCanvas runs your resume through parsing simulations of major ATS systems like Workday and Greenhouse. Upload your resume, get your parsability score in 30 seconds, and see which formatting elements are breaking. Sign up free and test it →

Disaster #7: Skills in Paragraph Form

What people write: “Proficient in a wide range of programming languages including Python, JavaScript, React, Node.js, SQL, and experienced with cloud platforms such as AWS and Azure, as well as containerization technologies like Docker and Kubernetes.”

Why ATS can’t parse it: ATS systems look for skills in list format. When skills are buried in prose, the keyword extraction fails.

The ATS might catch “Python” and “JavaScript,” but it misses the others. Your keyword match score plummets.

The fix: List skills explicitly:

Python
JavaScript
React
Node.js
SQL
AWS
Azure
Docker
Kubernetes

Bullet points. One skill per line (or comma-separated if space is tight). The ATS reads this format easily.

Disaster #8: Inconsistent Date Formatting

What people write:

“Jan 2020 - March 2023” (mixed abbreviations)
“2020-2023” (no months)
“01/2020 - 03/2023” (numeric format)

Why ATS struggles: ATS systems are looking for consistent date patterns. When you mix formats, the ATS can’t reliably extract employment duration.

Some systems will flag your resume as missing dates. Others will misinterpret the timeline. Your 3 years of experience gets read as 3 months.

The fix: Pick one format and stick with it:

Month Year - Month Year (January 2020 - March 2023)
MM/YYYY - MM/YYYY (01/2020 - 03/2023)

I prefer “Month Year” format because it’s most widely recognized. But consistency matters more than the specific format.

Disaster #9: Job Titles Buried in Descriptions

What people write: “Worked at Google from 2020-2023 in the engineering department where I served in the capacity of a senior developer responsible for…”

Why ATS can’t parse it: ATS systems are scanning for job titles in a specific location: immediately after the company name or at the start of each job entry.

When your title is buried in a sentence, the ATS keyword extraction fails. It can’t tell what role you held.

The fix: Lead with the job title:

Senior Developer
Google | 2020-2023

[Your accomplishments here]

Job title first. Company and dates on the same line. Then bullet points for achievements.

This structure matches how ATS systems are designed to parse work experience.

Disaster #10: Special Characters and Symbols

What people use:

Bullet points: ✓ ★ → ●
Decorative dividers: ═══════
Ampersands instead of “and”
Smart quotes (” ”) instead of straight quotes (” ”)

Why ATS can’t parse it: Special characters often get misread or dropped entirely. A checkmark (✓) might render as a question mark (?). A star (★) might disappear.

When ATS systems can’t interpret a character, they skip it. Your bullet points vanish. Your section dividers break the parsing flow.

The fix: Use only standard ASCII characters:

Standard bullet points: • or -
No decorative elements
Write “and” instead of &
Use straight quotes, not smart quotes

Keep it plain. The ATS will thank you by actually reading your resume.

The ATS Formatting Checklist

Before you submit your resume, verify:

✅ Single-column layout (no side-by-side sections)
✅ Standard section headers (Work Experience, Education, Skills)
✅ No tables (use plain text with line breaks)
✅ No graphics, text boxes, or images
✅ Contact info in body (not in header/footer)
✅ Standard fonts (Arial, Calibri, Times New Roman)
✅ Skills in list format (bullets or comma-separated)
✅ Consistent date formatting (Month Year - Month Year)
✅ Job titles prominent (first line of each job entry)
✅ No special characters (standard ASCII only)

Testing Your Resume

Don’t guess whether your formatting works. Test it.

Copy your resume text and paste it into a plain text editor (Notepad, TextEdit). If the structure falls apart, the ATS can’t read it either.

Better: run your resume through an ATS parser. JobCanvas simulates how Workday, Greenhouse, and Lever parse resumes. You’ll see exactly which sections fail and get specific formatting fixes. Get started free →

The Bottom Line

Your resume might be beautiful to you. But if the ATS can’t parse it, no human will ever see it.

The formatting disasters I’ve shown you kill 75% of applications. Not because the candidates are unqualified. Because the formatting breaks the automated screening.

Fix these disasters today. Use single-column layouts, standard headers, plain text formatting, and consistent structure.

The ATS is a gatekeeper, not a judge. Once you pass the gate, the human review starts. But you have to get through the gate first.

Test your resume. Fix what breaks. Then apply with confidence.