September 15, 2026 · 6 min read

Resume Mistakes That Get Rejected by ATS (6 Common Errors)

Most resume mistakes ATS systems catch are invisible to the human eye. Your resume looks polished in a PDF viewer - but the parser sees garbled text, missing sections, and keyword mismatches. Here are the six ATS resume mistakes that kill applications before a recruiter ever reads them, with before/after examples for each fix.

Mistake #1: Using Tables or Columns

Multi-column layouts are the single most common ATS resume mistake. The parser reads your resume left-to-right across the full page width, so a two-column design causes it to merge content from both columns into one scrambled line. Your job title ends up next to your company address. Your skill names merge with your bullet points.

Tables cause the same problem. A three-column skills table often parses as one long unreadable string - or gets skipped entirely. The ATS never sees the skills you worked hard to list.

Before / After

Before (what NOT to do):

Two-column layout: left column has job titles, right column has dates and bullets - ATS reads across and merges: "Senior Engineer | 2022-2024 Led platform migration Reduced latency 40%"

After (what TO do):

Single-column layout: "Senior Engineer, Acme Corp (2022-2024) - Led platform migration - Reduced latency 40%"

Use a single-column layout for everything. If you want visual separation, use bold headers and spacing - not table cells or text boxes.

Mistake #2: Using the Wrong File Format

PDF versus .docx is one of the most debated ATS resume mistakes - and the answer depends on the system. Older ATS platforms (Taleo, some versions of iCIMS) have inconsistent PDF parsing. A PDF that renders perfectly on screen may produce garbled text, merged lines, or blank sections when the parser extracts it.

.docx files use a structured XML format that most ATS platforms parse reliably. Unless the job posting explicitly asks for PDF, .docx is the safer default.

Before / After

Before (what NOT to do):

Submitting a visually styled PDF exported from Canva or a design tool - the embedded fonts and layout layers cause ATS parsers to misread or skip content.

After (what TO do):

Submit a .docx file built in Google Docs or Microsoft Word with standard fonts (Arial, Calibri, Georgia). Save as .docx, not "export to PDF".

If the posting says PDF, submit PDF - but make sure it was exported from Word or Google Docs, not from a design app. Design-app PDFs embed fonts and layers that break most parsers.

Mistake #3: Keyword Stuffing or Missing Keywords

ATS systems do exact string matching, not semantic matching. If the job posting says "project management" and your resume says "project coordination," the ATS counts that as a miss - even though the meanings overlap. This is one of the most damaging ATS resume mistakes because it affects your score silently.

The opposite mistake - stuffing in every keyword whether you have the experience or not - also backfires. Modern ATS platforms use context scoring. A keyword buried in a wall of unrelated text scores lower than the same keyword in a clear, relevant bullet.

Before / After

Before (what NOT to do):

"Oversaw coordination of cross-functional initiatives" - uses "coordination" when the posting says "project management"

After (what TO do):

"Led project management across cross-functional teams, delivering three platform initiatives on schedule" - uses the exact phrase from the posting in context

Mirror the job posting's exact phrases in your bullets where you genuinely have the experience. Do not replace words with synonyms that feel more natural to you - use the posting's language.

Mistake #4: Non-Standard Section Headers

ATS systems are trained on a fixed vocabulary of section labels. When the parser encounters a header it does not recognize, it either skips the section or miscategorizes its content. A creative header like "Where I've Been" instead of "Work Experience" can cause the ATS to miss your entire job history.

This is one of the sneakiest ATS resume mistakes because the resume looks fine to a human reader - but the ATS never correctly parsed the experience section into its database fields.

Before / After

Before (what NOT to do):

  • "Where I've Been"
  • "My Toolkit"
  • "Academic Journey"
  • "Credentials"

After (what TO do):

  • "Work Experience"
  • "Skills"
  • "Education"
  • "Certifications"

Stick to the standard labels: Work Experience (or Professional Experience), Education, Skills, Summary, and Certifications. Creative headers feel personal but cost you points in every ATS that does not recognize them.

Mistake #5: Inconsistent Date Formats

ATS parsers use your dates to calculate tenure and sort your experience chronologically. When date formats are inconsistent across entries - mixing "Jan 2024" in one role with "01/2024" in another - the parser can miscalculate your total experience length, mis-sort your roles, or flag the resume for manual review.

This ATS resume mistake is easy to make when you add new roles over time without checking the format you used earlier in the document. The fix is two minutes of consistency review before every submission.

Before / After

Before (what NOT to do):

Senior Engineer - Jan 2024 to Present | Product Manager - 03/2022 - 12/2023 | Analyst - 2020 - March 2022

After (what TO do):

Senior Engineer - January 2024 to Present | Product Manager - March 2022 - December 2023 | Analyst - June 2020 - February 2022

Pick one format - "Month YYYY" is the safest - and apply it to every date in the document. Avoid abbreviations in some places and full names in others.

Mistake #6: No Skills Section

ATS systems are built to look for a dedicated Skills section. Many platforms specifically extract the Skills field into its own database column, separate from work experience. If your skills are buried inside bullet points but you have no standalone Skills section, the ATS may score you as having zero listed skills - even if every bullet demonstrates relevant expertise.

This is the ATS resume mistake that most often surprises strong candidates. They assume their experience bullets communicate their skills. For a human reader, yes. For the ATS, only if there is a clearly labeled Skills section to parse.

Before / After

Before (what NOT to do):

Resume has only: Summary, Work Experience, Education - skills are woven into bullets but no dedicated section exists.

After (what TO do):

Add a "Skills" section with a plain comma-separated list: "Python, SQL, Tableau, Stakeholder Management, Agile, JIRA, Data Analysis, Cross-functional Leadership"

Add a Skills section even if your bullets already demonstrate those skills. Use a plain comma-separated list under the "Skills" header - no tables, no columns, no star ratings. Keep it to 8-15 of the most relevant terms for the role you are applying to.

Catch Every ATS Mistake Before You Submit

These six ATS resume mistakes are the most common - but they are not the only ones. Embedded images used as bullet points, unusual font encoding, and contact info in document headers are harder to catch manually but equally damaging to your parse score.

Before your next application, run your resume through an ATS checker to confirm every mistake is fixed - not just the ones you can see by reading. A 5-minute check before submission is faster than rewriting your resume after three weeks of silence.

Find all your ATS mistakes - free

Upload your resume and get an instant ATS analysis - keyword gaps, formatting issues, and parse errors ranked by impact. No signup required.

Find all your ATS mistakes - free