13 ATS Resume Mistakes That Get Good Candidates Auto-Rejected (And the Fix for Each)
The most damaging ATS resume mistakes are invisible formatting traps — decorative lines and dividers, contact details trapped in headers, creative section headings, inconsistent date formats, unexplained acronyms and text baked into images — that stop applicant tracking systems from reading your experience correctly. Your content can be excellent and still fail, because roughly three in four large employers now use an ATS at some stage of screening according to widely-cited recruiter surveys, and a parser that mangles one field can drop you before a human ever looks. This list covers thirteen mistakes we see repeatedly in real resumes, why each breaks parsing, and the exact fix. Note: this guide focuses on layout and language traps; for structural parsing failures like tables, columns and graphics-heavy templates, read our dedicated post on ATS resume format fundamentals instead.
1. Decorative Lines and Horizontal Dividers
That elegant rule under your name or between sections is a classic parser trap. Depending on how the ATS converts your file to text, a drawn divider can be interpreted as a stray character, a table border, or a page-break signal — any of which can truncate everything above or below it.
- The fix: Delete drawn lines entirely. Create visual separation with bold, slightly larger heading text and white space. If you must keep some structure, use paragraph borders sparingly in Word (they survive better than inserted shapes) — but plain headings are safest.
2. Contact Details in the Document Header
Many parsers skip Word headers and footers completely because they're stored as separate document layers. The result: your name, phone number and email never make it into the candidate record — and some systems reject records without parseable contact fields.
- The fix: Put name, city, phone and email as normal body paragraphs on line one. Keep them out of headers, footers, and definitely out of text boxes.
3. Creative Section Headings
"Where I've Made Magic" reads nicely to humans and means nothing to software. Parsers identify sections by matching standard labels — Work Experience, Education, Skills, Certifications, Projects — and map content accordingly. A heading like "My Journey" can cause your entire job history to be filed under "unknown", where recruiters' filters won't find it.
- The fix: Use conventional heading names exactly. Personality belongs in your summary sentences, not your section labels. For the full recommended sequence, see our breakdown of the section order ATS parsers expect.
4. Inconsistent Date Formats
Mixing "Jan 2023–March 2024", "01/2023 – 03/24" and "2023-2024" across entries confuses date-extraction logic that calculates tenure and sorts your history. Bad date parsing produces employment gaps you don't actually have — and gaps trigger recruiter filters.
- The fix: Pick one format — "Jan 2023 – Mar 2024" works globally — and apply it everywhere: jobs, education, certifications. Never abbreviate years ("'24") and never rely on right-aligned dates floating in white space next to job titles.
5. Acronyms Without Expansion
If the job description says "Search Engine Optimisation (SEO)" and your resume only says "SEO", keyword-matching algorithms may register no hit — many matchers score exact phrase matches, not synonyms. The reverse also happens: spell it out only and miss recruiters searching the acronym.
- The fix: Write the expanded form once with the acronym in brackets — "SEO (Search Engine Optimisation)" — then use whichever form the job posting prefers afterwards. Do this for tools (CRM), methodologies (CI/CD) and qualifications alike.
6. Text Inside Images, Logos and Icons
Some candidates embed skill badges, company logos with names rendered in them, or entire summary blocks as images. ATS software extracts text characters; pixels are ignored. An image-based "skills wheel" contributes zero keywords, and a scanned-in PDF behaves like one giant image.
- The fix: All text must be real, selectable text. Test it: try selecting your name with a cursor in your PDF viewer. Can't select it? Neither can the parser. Our guide on PDF vs Word for ATS covers which file formats keep text extractable.
7. Fancy Bullets and Custom Symbols
Wingdings arrows, emoji bullets and multi-level ornate numbering usually convert harmlessly — but occasionally render as garbage characters that interrupt sentence flow in parsed output. Worse, some candidates use symbols *as* separators inside lines ("Python ★ SQL ★ Tableau"), which parsers may read as one long nonsense word.
- The fix: Standard round or square bullet points from your editor's default set. Separate skills with commas in a normal line of text.
8. Job Titles Detached From Their Dates and Company
Layout tricks — titles left, dates far right, company underneath in small italics — look designed but scramble the association between title, employer and duration when linearised into text. Some parsers then invent their own groupings, merging two roles into one or splitting one role into phantom duplicates.
- The fix: Put each entry on consecutive simple lines: Job title (bold), then "Company | City | Jan 2021 – Mar 2023" beneath it, then bullets. One role per block, no floating elements.
9. Missing or Misplaced Keywords From the Job Description
Beyond formatting, the biggest auto-rejection driver is ranking: many ATS score resumes against the posting's required skills and rank candidates. A resume that says "built reporting dashboards" while the advert demands "Power BI" loses points against identical candidates who used the tool's actual name.
- The fix: Mirror the posting's vocabulary wherever truthfully applicable, including exact product names and spelled-out phrases. Systematic tailoring beats guesswork — our step-by-step guide to tailoring a resume to a job description shows the process.
10. Overloaded Design Elements That Survive Parsing But Kill Readability
Sometimes the ATS copes fine and the human doesn't. Two-column layouts that parse correctly can still present a jumbled reading order to a recruiter skimming for eight seconds. Tiny fonts (below ~10pt), pale grey text and cramped margins all raise the odds a busy screener moves on.
- The fix: Single column, 10–12pt body font, black or near-black text, generous margins. Simplicity wins both audiences — our annotated ATS resume examples show what this looks like finished.
11. Special Characters in File Names and Contact Lines
File names like "Rohit's Resume (FINAL) v3!.pdf" sometimes break uploads or get truncated in candidate portals. Em-dashes and unusual unicode in phone numbers can similarly garble parsed contact data.
- The fix: Name files plainly: "FirstName-LastName-Resume.pdf". Use plain digits and spaces in phone numbers.
12. Repeating the Same Keyword Stuffed Into White Text or Footers
Some applicants respond to ATS fears by hiding keyword lists in tiny footers or white-on-white text. Modern parsing pipelines index everything they can extract — including your hidden text — which means recruiters searching candidates can surface your resume with keywords you never legitimately demonstrated, then discover the trick in seconds.
- The fix: Earn keywords through real content in visible sections. We've tested what happens with invisible text directly — see our write-up of the signs an ATS rejected your application for how rejection actually manifests.
13. Ignoring the Application Form Entirely
Here's the mistake hiding behind all others: when a portal makes you re-type your work history into structured fields, many candidates assume the uploaded resume is what gets screened. Often the reverse is true — recruiters filter on the structured fields, and the resume file is only opened later. A perfect resume attached to empty form fields can still be filtered out.
- The fix: Complete every portal field with the same care as the document itself: full job titles, complete dates, every required skill listed. Consistency between form and file matters too — mismatches read as sloppiness to human reviewers.
How Do You Check Whether These Mistakes Exist in Your Resume?
A five-minute self-audit catches most of this list:
- Select-all test. Ctrl+A in your document — anything that doesn't highlight (images, shapes, header text) isn't reliably parseable.
- Paste-to-notepad test. Copy your PDF's text into Notepad. If the order looks scrambled or content is missing, that's what the ATS sees.
- Date scan. Visually confirm every date follows one format.
- Acronym check. Search for capitalised strings and expand each once.
- Keyword comparison. Lay your resume beside the posting and mark unmatched required terms.
Manual checking works but scales badly if you're applying to dozens of tailored applications — which, per our analysis of how many jobs you should apply for per day, you should be doing deliberately rather than spraying identical CVs.
Do These Mistakes Actually Cause Auto-Rejection, or Just Bad Parsing?
Worth separating, because the two failure modes have different fixes. Parsing failures (mistakes 1–8) corrupt what enters your candidate record — missing phone numbers, merged job titles, phantom gaps. Ranking failures (mistakes 9, 12) happen when parsing works but scoring against the posting ranks you below competitors. And process failures (mistakes 11, 13) occur after your document is already fine. The practical takeaway: fix parsing first, because nothing downstream matters if your experience never made it into the record intact.
It's also worth calibrating expectations honestly. Not every employer's system rejects on formatting — smaller companies using lightweight tools may never parse your file at all, just open it. But you can't know which system sits behind any given application, so the rational strategy is building one resume that survives the strictest parser and reads beautifully to humans. That's exactly the philosophy behind our annotated ATS resume examples: format once correctly, then tailor content per application.
A Quick Word on What This List Doesn't Cover
Six recurring parsing problems deserve their own deep dive because their fixes are structural rather than cosmetic: multi-column layouts that scramble reading order, tables splitting cells into orphaned fragments, graphics-heavy designer templates, text boxes, footers-as-contact-blocks at scale, and template files whose embedded styles break conversion. If your resume uses any of those, start with our complete guide to ATS resume format, then come back to this list for the finishing touches.
How Often Should You Re-Check Your Resume for These Mistakes?
Run the full audit whenever you change templates, switch file formats, or edit heavily — and at minimum once per job-search season. Formatting mistakes creep in through small edits: a new entry pasted from an old document with different date styling, a divider added to "fix" spacing, a heading renamed during a redesign. The paste-to-notepad test takes under a minute and catches almost every regression, so build it into your pre-application routine the same way you'd proofread a cover letter. If you're maintaining one master CV with per-application tailoring — which our analysis of how many applications per day actually works recommends — check the master thoroughly once, then only re-verify after structural edits.
Key Takeaways
- Most ATS rejections come from layout traps: dividers, header contacts, creative headings, mixed date formats and image text.
- Expand acronyms once, mirror job-posting vocabulary, and keep every entry in simple stacked lines.
- Fill in portal form fields as carefully as your resume — filters often run on those, not the file.
Next Step: Scan Your Resume Before Your Next Application
Don't wait for silence after applying to learn your resume has a parsing problem. Upload your CV to JD2CV's free ATS Resume Checker and get an instant format-and-keyword score against your target job description, with specific fixes flagged line by line.