Skip to content
Back to blogATS Guide

Common ATS Résumé Mistakes

Resume Master Team · · 5 min read

ShareLinkedInX

The most common ATS résumé mistakes are small formatting choices that quietly break parsing: contact details in the header, tables and columns, images instead of text, and creative section labels. None of them look like errors to you. All of them can scramble what the software reads. Fix these and your résumé gets parsed into the right fields, so your real experience actually reaches a recruiter.

An applicant tracking system reads your file, pulls the text into a database, and matches it against the job. When a design choice confuses that process, your qualifications get mangled before a human ever sees them. Here are the mistakes that come up again and again, and the exact fix for each.

Which formatting choices break ATS parsing?

Some templates put your name, phone, and email in the document's header region. Older parsers skip that region entirely, so a résumé can score well on content and still list no way to contact you.

Fix: Put contact details as normal text at the top of the page body — not in the header/footer area.

Tables and multi-column layouts

Tables look tidy, but many ATS flatten them or read them left-to-right across the whole page. A two-column résumé can interleave your sidebar skills into your job bullets and produce gibberish.

Fix: Use a single-column layout. Lay out sections top to bottom, not side by side.

Text saved as an image

A résumé exported as one big graphic, or a skills chart with rating bars, reads as nothing to a parser. It can't extract text from a picture.

Fix: Keep everything as real, selectable text. Test by trying to highlight your words with the cursor — if you can't select them, neither can the ATS.

Icons instead of labels

Little phone and envelope icons look clean, but a parser reads an icon as nothing and a screen reader announces nothing useful.

Fix: Write the words. "Email: you@example.com" beats an envelope glyph.

Which content mistakes hurt your score?

Creative section headings

ATS matches on heading text. "My Journey So Far" or "What I Bring to the Table" may not register as your work history.

Fix: Use plain labels — "Experience", "Skills", "Education", "Certifications".

Keyword stuffing

Pasting the entire job description into white text, or repeating a keyword 20 times, is an old trick that modern systems and recruiters catch. It also reads as spam to a human.

Fix: Use the important terms from the posting naturally, and only where they're true. If the job wants "SQL" and you know SQL, put it in your skills and show it in a bullet.

Vague, verb-free bullets

"Responsible for managing reports" tells a recruiter almost nothing and carries no strong keyword.

Fix: Lead with an action verb and add a number where you can. "Built 12 weekly dashboards that cut reporting time from 2 days to 3 hours."

Inventing experience to match keywords

Padding your résumé with tools you've never used gets exposed in the interview and burns trust. A good résumé builder should never invent experience for you either — the goal is to surface your real skills in the language the job uses, not fabricate new ones.

Fix: Only claim what you can defend. If there's a genuine gap, address it in a cover note or by highlighting adjacent experience.

Which file and date mistakes trip people up?

The wrong file type

An unusual format, or a file the system can't open, can fail to parse.

Fix: Unless the posting says otherwise, a clean, text-based PDF or a .docx is the safe choice. Follow the application's stated preference when there is one.

Inconsistent date formats

Mixing "2023", "Jan 2023", and "01/23" across jobs makes it hard for a parser to attach dates to the right role, which can distort your timeline.

Fix: Pick one format — "Jan 2023 – Present" works well — and use it on every entry.

Fancy fonts and special characters

Decorative fonts and unusual bullet symbols sometimes render as junk characters after parsing.

Fix: Use a standard font and a standard round bullet. Boring parses cleanly.

A quick before/after

Before:

  • Name and email in the header region
  • Two columns, skills in a sidebar with rating bars
  • Section titled "Where I've Made an Impact"
  • Bullet: "Responsible for various data tasks"

After:

  • Contact info as plain text at the top of the body
  • Single column, skills as a simple bulleted list
  • Section titled "Experience"
  • Bullet: "Cleaned and modeled 2M+ rows of sales data, cutting report prep from 8 hours to 1"

Same person, same career. The second version gets read correctly, so the score reflects the real qualifications instead of a parsing accident.

Catch these before you apply

You don't have to guess which of these mistakes your résumé has. A free ATS check parses your file the way an applicant tracking system would and shows you each issue plus the specific fix — not a mystery number, but "contact info is in the header, move it into the body." Make the change, re-run it, and confirm the fix landed.

Run your résumé through the ATS check once, clear the flagged mistakes, and you'll stop losing interviews to formatting you never knew was broken.