We Analyzed 5,000 Resumes: The Top Reasons They Fail ATS

We ran 5,000 resumes through ATS parsing engines. The results weren't pretty. Over half had at least one issue that would prevent accurate parsing, and many had three or more. If you've been applying to jobs and hearing nothing back, this data might explain why.

Why This Matters

Most job seekers assume their resume is fine. You proofread it, asked a friend to look it over, maybe even hired a professional writer. But none of that matters if the ATS can't read your resume in the first place.

An Applicant Tracking System (ATS) is software that companies use to collect, parse, and filter job applications before a human ever sees them. According to recent data, 98% of Fortune 500 companies and roughly 75% of all employers use some form of ATS. That means your resume's first reader is almost certainly a machine, and machines are far less forgiving than humans when it comes to formatting quirks, missing keywords, and file issues.

The gap between "looks good to a human" and "parses correctly in an ATS" is where most applications quietly die. Let's look at what the data actually shows.

Our Methodology

ResumeFast's ATS checker processes resumes against real parsing algorithms used by major platforms including Workday, Greenhouse, and Lever. We aggregated anonymous results from 5,000 consecutive scans, categorized every parsing failure, and ranked them by frequency and severity. No resumes were cherry-picked. This is a representative sample of what real job seekers are submitting right now.

The Data: Top 5 ATS Failure Reasons

Here's what we found when we broke down every parsing failure across all 5,000 resumes:

Formatting issues are the number one reason resumes fail ATS systems, affecting 34.7% of all resumes we analyzed. That's more than one in three. And these aren't resumes with typos or weak bullet points. They're resumes that look perfectly professional to the human eye but turn into scrambled text when an ATS tries to read them.

The total adds up to exactly 100% because we classified each resume by its primary failure. In reality, 43% of failing resumes had multiple issues. But the primary failure, the one that caused the most damage to parsing accuracy, fell into one of these five categories every single time.

Deep Dive: Formatting Issues (34.7%)

This is the big one. More than a third of all resumes we analyzed had formatting that broke ATS parsing. The three worst offenders within this category were tables, multi-column layouts, and content placed in headers or footers.

Why Tables and Columns Break ATS

When you create a two-column resume in Word or Google Docs, it looks clean and space-efficient on screen. But ATS parsers read documents linearly, left to right, top to bottom. A two-column layout forces the parser to jump between columns, and most parsers handle this poorly. The result is jumbled text where your job title from column one gets merged with a skill from column two.

Tables cause the same problem. If you use a table to align your dates on the right and your job titles on the left, a human sees a nicely formatted entry. The ATS sees a data grid and often reads cells in the wrong order.

Why Headers and Footers Get Ignored

Many candidates put their name, phone number, and email in the document header. This keeps the information visible on every page without taking up body space. The problem: most ATS parsers skip headers and footers entirely. They're treated as page decoration, not content. If your contact information only exists in the header, the ATS has no idea who you are.

Before and After

Before (fails ATS): Two-column layout with table formatting

Left column: Skills, Certifications, Languages Right column: Work Experience, Education Contact info in document header

After (passes ATS): Single-column layout, no tables

Contact info at the top of the document body Work Experience section with standard headings Skills section below experience Education at the bottom

The Fix

Use a single-column layout with no tables for organizing content. Put all contact information in the document body, not in headers or footers. Use standard section headings like "Work Experience," "Education," and "Skills." If you want visual separation, use bold text and horizontal lines, not columns or table cells.

If you're not sure whether your current resume passes, run it through our free ATS checker to see exactly what the parser extracts.

Deep Dive: Keyword Mismatches (27.9%)

The second most common failure isn't a technical issue. It's a language issue. ATS systems match resumes to job descriptions using keyword matching, and they're frustratingly literal about it.

ATS Matches Exact Terms, Not Synonyms

If a job posting asks for "project management" experience and your resume says "managed projects," some ATS parsers won't make the connection. You might think those mean the same thing, and you'd be right. But basic ATS keyword matching doesn't think. It pattern-matches.

This gets worse with technical terms. "JavaScript" and "JS" might be treated as different skills. "Customer Relationship Management" and "CRM" might not match. Even capitalization can matter in some older systems.

Before and After

Before (low keyword match):

Skills: Team leadership, process improvement, budget oversight, stakeholder communication

After (high keyword match, tailored to a Project Manager posting):

Skills: Project Management (PMP certified), Agile/Scrum, Budget Management, Stakeholder Engagement, Risk Assessment, JIRA, Microsoft Project

The second version mirrors the exact language from a real project manager job posting. Same candidate, same experience, dramatically different ATS score.

The Fix

Every resume you submit should be tailored to the specific job posting. Read the job description carefully and identify the exact terms it uses. Then make sure those terms appear naturally in your resume. Don't stuff keywords. Instead, weave them into your experience bullets and skills section.

Use ResumeFast's Keyword Matcher to compare your resume against any job posting and see your match rate before you apply. For more context on how keyword matching actually works (and what's been exaggerated), read our breakdown of common resume keyword myths.

Deep Dive: File Format Problems (18.2%)

We classified this as "Critical" severity because when file format is the issue, the ATS often can't extract any text at all. It's not a partial failure. It's a total failure. Your resume shows up as a blank page or a garbled mess.

The Canva Problem

Canva resumes were the single largest contributor to this category. Canva exports PDFs as image-based files, not text-based files. To a human, the PDF looks perfect. To an ATS, it's a picture with no extractable text. The parser sees nothing.

This isn't a Canva bug. It's how their rendering engine works. Design tools like Canva, Photoshop, and Illustrator prioritize visual fidelity over text structure. That's great for posters. It's terrible for resumes.

We've written a full deep dive on this issue: Why Canva Resumes Fail ATS.

Creative Templates With Icons and Graphics

Even non-Canva templates cause problems when they use icons (like a phone icon next to your number), progress bars for skill levels, or decorative graphics. ATS parsers can't interpret visual elements. A five-star rating next to "Python" tells the ATS nothing about your Python proficiency.

The Fix

Export your resume from Microsoft Word or Google Docs. Both produce text-based PDFs that ATS systems can read reliably. If you prefer DOCX format, that works too. Avoid design tools entirely for the version of your resume that goes through online applications.

If you want a visually impressive resume for in-person networking or direct emails, keep a separate "design" version. But the version you submit through job portals should always prioritize parseability over aesthetics. For guidance on which format works best, see our guide to the best resume format for ATS.

Deep Dive: Contact Info Failures (12.4%)

This one is preventable and frustrating. Roughly one in eight resumes had contact information that the ATS couldn't parse correctly. The recruiter literally cannot call you back because the system didn't capture your phone number.

Common Contact Info Failures

Phone numbers in headers: As mentioned above, headers get skipped. If your phone number is only in the header, it's invisible to the ATS.

Unusual email formatting: Emails with multiple dots, plus signs, or very long domains sometimes trip up older parsers. The email john.doe+applications@my-custom-domain.consulting is valid, but some ATS systems struggle with it.

LinkedIn URLs that aren't linked: If you paste your LinkedIn profile as plain text without the full URL, some parsers can't identify it as a profile link. Others truncate long URLs.

The Fix

Put your full name, phone number, email address, and LinkedIn URL in the first few lines of the document body. Not in a header. Not in a sidebar. Not in a text box. Just plain text at the top of the page. Use a simple email address when possible. Include the complete LinkedIn URL (e.g., linkedin.com/in/yourname) rather than a shortened or display version.

Deep Dive: Encoding Issues (6.8%)

This is the smallest category, but it's the sneakiest. You often can't see encoding problems by looking at your resume. They're invisible characters hiding in your text.

How Invisible Characters Get In

The most common source is copy-pasting from other documents. When you copy text from a PDF, a website, or even another Word document, invisible formatting characters often come along for the ride. Smart quotes (" " instead of " "), em dashes, en dashes, fancy bullet characters, and non-breaking spaces all look fine on screen but can confuse ATS parsers.

Some candidates copy their job descriptions from LinkedIn or company websites and paste them directly into their resumes. The pasted text brings hidden characters that the ATS stumbles over during parsing.

The Fix

Type your resume content directly rather than copying from other sources. If you must copy text, paste it into a plain text editor first (like Notepad) to strip formatting, then copy it again into your resume document. Use standard bullet points (the round ones), straight quotes, and regular hyphens. Avoid special characters that you didn't type yourself.

For a broader look at how ATS parsing works under the hood, read our explainer on how ATS systems actually work.

The Recovery Checklist

If your resume might be affected by any of these issues, work through this checklist before your next application:

1. Switch to a single-column layout. Remove all tables, text boxes, and multi-column formatting from your resume.
2. Move contact info to the document body. Name, phone, email, and LinkedIn should be plain text at the top of page one.
3. Check your file source. If you created your resume in Canva, Photoshop, or any design tool, recreate it in Word or Google Docs.
4. Tailor keywords to each job. Run your resume through the Keyword Matcher against the specific job posting before applying.
5. Remove decorative elements. Icons, progress bars, skill charts, and profile photos should all be removed for ATS submissions.
6. Clean up encoding. Open your resume in a plain text editor. If you see weird characters, squares, or question marks, replace them with standard text.
7. Use standard section headings. "Work Experience" not "Where I've Made an Impact." "Education" not "Academic Journey."
8. Test before submitting. Run your final resume through an ATS checker to verify it parses correctly. Fix any issues it flags before you hit apply.

What the Data Tells Us About the "75% Rejection" Myth

You've probably seen the statistic that "75% of resumes are rejected by ATS before a human sees them." We've investigated this claim in detail in our post on the 75% ATS rejection myth, and the reality is more nuanced. ATS systems don't reject resumes in the way most people imagine. They parse and score. A low score means your resume appears further down the list, not that it vanishes into a black hole.

That said, our data shows that over 50% of resumes have at least one parsing issue that reduces their ATS score. The resume doesn't get "rejected," but critical information gets lost, keywords don't match, or entire sections disappear. The practical effect is similar: a qualified candidate gets overlooked because the system couldn't accurately read their application.

The distinction matters because the fix isn't about gaming an algorithm. It's about making sure the ATS can accurately represent your qualifications. When your resume parses correctly, the system works in your favor. When it doesn't, even the strongest experience becomes invisible.

For a complete look at the latest hiring data, including ATS adoption rates, recruiter screening times, and application volumes, see our 100+ Resume Statistics for 2026.

Frequently Asked Questions

What percentage of resumes get rejected by ATS?

The commonly cited "75% rejection rate" is misleading. ATS systems don't reject resumes outright. They parse and rank them. Our analysis found that 52% of resumes have at least one issue that reduces parsing accuracy, which lowers their ranking and reduces the chance of human review. The actual percentage that never gets seen by a recruiter varies by company, role, and applicant volume.

Does ATS reject resumes automatically?

No. An ATS parses your resume into structured data (name, experience, skills, education) and scores it against the job description. Recruiters then review candidates starting from the top of the ranked list. A poorly parsed resume gets a lower score, which means it appears further down the list. In high-volume roles where recruiters only review the top 20-30 candidates, a low score effectively means your resume is never seen.

Can a perfectly qualified candidate fail ATS?

Yes. Our data shows that formatting issues alone can cause a qualified candidate's resume to parse incorrectly. If the ATS can't extract your job titles, skills, or experience because of table formatting or header placement, your qualifications are invisible to the system. The candidate is qualified. The resume just doesn't communicate that to the machine.

What's the best file format for ATS?

A .docx file from Microsoft Word or a PDF exported from Word or Google Docs. Both formats produce text-based files that ATS parsers can read reliably. Avoid PDFs from design tools like Canva, Photoshop, or Illustrator, as these are often image-based and contain no extractable text. When in doubt, .docx is the safest choice.

How do I check my ATS score?

Use ResumeFast's free ATS checker to upload your resume and see exactly what the parser extracts. It shows you how your contact information, work experience, skills, and education appear to the ATS. You can also use the Keyword Matcher to compare your resume against a specific job posting and see your keyword match rate.

Do all companies use ATS?

Nearly all large companies do. 98% of Fortune 500 companies use an ATS, and approximately 75% of all employers use some form of applicant tracking software. Even small companies increasingly use lightweight ATS tools. The safest assumption is that your resume will be parsed by software before a human reads it, regardless of company size. For more context, see our guide on how ATS systems actually work.

Is there a free way to check if my resume is ATS-friendly?

Yes. Several free resume tools work without requiring sign-up, including basic ATS scanners. ResumeFast's ATS checker provides a detailed parsing report that shows exactly what an ATS extracts from your resume, helping you identify and fix issues before applying.

What's the single most impactful change I can make?

Based on our data, switching to a single-column layout with no tables is the highest-impact change. Formatting issues affected 34.7% of resumes in our analysis, and most of those were caused by multi-column layouts and table-based formatting. This one change addresses the largest category of ATS failures and takes less than an hour to implement.