20 Resume Mistakes That Get You Rejected (ATS + Recruiters)

ATS Parsing Mistakes (1-8)

These mistakes prevent ATS systems from correctly reading your resume. Even if your content is perfect, parsing failures mean your data gets scrambled or dropped before any scoring happens.

1. Using a two-column or sidebar layout

Why it hurts: ATS parsers read top-to-bottom, left-to-right. Two-column layouts cause the parser to interleave content from both columns, producing nonsensical output. Your skills section might get merged with your job descriptions.

Fix: Use a single-column layout. Every major ATS (Workday, Greenhouse, Lever, iCIMS) handles single-column formats reliably.

2. Putting contact info in headers or footers

Why it hurts: Many ATS parsers ignore document headers and footers entirely. If your name, email, and phone number are in the header, the system may not extract them at all - creating an anonymous candidate record.

Fix: Place all contact information in the main body of the document, at the top.

3. Using tables for layout

Why it hurts: Tables look organized to humans but most parsers strip the table structure and dump cell contents in reading order. A neatly aligned skills table becomes a jumbled string of text.

Fix: Use plain text with standard formatting. Bullet points and line breaks work everywhere.

4. Embedding text in images or graphics

Why it hurts: ATS systems cannot read text inside images, icons, charts, or infographics. If your job title is rendered as part of a graphic header, it's invisible to the parser.

Fix: Every piece of information on your resume must be selectable text. No icons for contact info, no image-based section headers, no skill-level bar charts.

5. Submitting the wrong file format

Why it hurts: .pages, .odt, Canva exports, and JPEG/PNG screenshots of resumes either fail to parse or produce garbled output. Even some heavily designed PDFs with embedded fonts can cause issues.

Fix: Submit as PDF unless the application specifically asks for .docx. Use a clean, text-based PDF - not a designed export from Canva or Figma.

6. Using creative section headings

Why it hurts: ATS systems look for standard section labels to categorize your content. "Where I've Made Impact" instead of "Experience" or "My Toolkit" instead of "Skills" prevents correct field mapping.

Fix: Stick to standard headings: Experience, Education, Skills, Summary, Projects, Certifications. These are what ATS-friendly resumes use.

7. Using text boxes or floating elements

Why it hurts: Floating text boxes in Word or Google Docs are treated as separate objects by many parsers. Content inside them may be extracted out of order or not at all.

Fix: Type directly into the document body. No text boxes, no shapes, no SmartArt.

8. Non-standard date formats

Why it hurts: ATS systems parse dates to calculate tenure and detect employment gaps. Unusual formats like "Q1 2023," "Winter 2024," or "2023.01" confuse parsers and may result in incorrect tenure calculations.

Fix: Use "Month Year – Month Year" (e.g., "Jan 2023 – Mar 2026") or "Month Year – Present." Spell out or abbreviate the month - both work.

Content Mistakes (9-14)

These mistakes pass ATS parsing but fail the recruiter review. Your resume gets correctly read by the machine, then rejected by the human.

9. Listing responsibilities instead of achievements

Why it hurts: "Responsible for maintaining the API" tells a recruiter nothing about your impact. Every candidate at your level had similar responsibilities. What distinguishes you is what you accomplished.

Fix: Start every bullet with an action verb and end with a measurable result. Use the formula: [Action] + [What] + [Technology] + [Result].

10. No numbers or metrics anywhere

Why it hurts: Without quantification, your bullets are claims without evidence. "Improved performance" could mean anything from a 2% tweak to a 10x improvement. Recruiters mentally discount unquantified statements.

Fix: Add at least one number to every bullet point: users served, revenue generated, time saved, percentage improved, team size, requests per second, error rate reduced.

11. Using the same resume for every application

Why it hurts: Each job description uses specific keywords. A generic resume will match some and miss others, consistently scoring lower than a tailored version. Recruiters also notice when a resume doesn't align with their specific requirements.

Fix: For each application, read the JD and adjust your skills section and bullet point order to match their terminology. You don't need to rewrite from scratch - reorder and swap keywords.

12. Missing keywords from the job description

Why it hurts: ATS keyword matching is often literal. If the job says "Amazon Web Services" and you write "AWS," some systems won't register the match. If they require "React" and you only mention "frontend development," you lose keyword score.

Fix: Include both the full term and abbreviation: "Amazon Web Services (AWS)." Mirror the exact phrasing from the job description.

13. Vague technology references

Why it hurts: "Various programming languages," "modern web technologies," or "multiple cloud platforms" are ATS dead zones. They contain zero matchable keywords. Recruiters also can't evaluate your technical fit from vague descriptions.

Fix: Be specific: "Python, TypeScript, and Go" instead of "multiple programming languages." Name every tool, framework, and platform you've used.

14. Including irrelevant experience

Why it hurts: Your summer job at a restaurant in 2015 doesn't help your software engineering application. Irrelevant experience dilutes your keyword density and wastes the recruiter's 7-second scan on content that won't persuade them.

Fix: Include only roles relevant to the target position. If an old role taught transferable skills, compress it to one line. Otherwise, drop it.

Clarity and Presentation Mistakes (15-20)

These mistakes make your resume harder to read, less credible, or less professional - even when the content is solid.

15. Typos and grammatical errors

Why it hurts: A single typo signals carelessness. In engineering roles where attention to detail matters, a misspelled technology name ("Kubernets" instead of "Kubernetes") can be disqualifying. Recruiters who see errors in the first 10 seconds often stop reading.

Fix: Proofread with a tool (Grammarly, spell check), then read it out loud. Have someone else review it. Pay special attention to company names and technology terms.

16. Writing in first person

Why it hurts: "I built a dashboard" and "I managed a team" waste space on pronouns and read less professionally than resume convention. It also feels oddly personal in a document meant to be scanned quickly.

Fix: Drop the pronoun. "Built a React dashboard that reduced reporting time by 4 hours/week" is cleaner and more direct.

17. Using an objective statement instead of a summary

Why it hurts: "Seeking a challenging position where I can leverage my skills" tells the employer what you want, not what you bring. It wastes prime resume real estate on something that adds zero value to the reader.

Fix: Replace with a 2-sentence summary that states your experience level, domain, and a key achievement. Or remove it entirely - a strong experience section speaks for itself.

18. Including "References available upon request"

Why it hurts: This line has been unnecessary since the 1990s. Everyone knows references are available. It wastes a line and signals that your resume advice is outdated.

Fix: Delete it. Use the space for another achievement bullet.

19. Inconsistent formatting

Why it hurts: Mixed date formats ("Jan 2023" in one place, "January 2023" in another), inconsistent bullet styles, varying font sizes, and uneven spacing make your resume look sloppy. It suggests you either didn't proofread or don't have attention to detail.

Fix: Pick one format for dates, one bullet style, one font, and one heading style. Apply them consistently throughout. Check alignment on every line.

20. Making it too long (or too short)

Why it hurts: A three-page resume for a mid-level role screams "can't prioritize." A half-page resume for a senior role screams "hasn't done much." Both extremes work against you.

Fix: One page for 0-7 years of experience, two pages for 8+. Every line should earn its place. If removing a bullet doesn't weaken your resume, it shouldn't be there.

Before / After Fixes

Resume Rejection Checklist

The Cost of Not Fixing These

Every one of these mistakes is fixable in under 5 minutes. But leaving them unfixed means your resume competes at a disadvantage against candidates who took the time to get the basics right. In a competitive job market, the gap between "qualified but rejected" and "qualified and interviewed" is often just formatting, keyword matching, and clear writing - not talent or experience. For a step-by-step approach to fixing these issues, read our guide on how to get past ATS filters.

Related Resume Examples

Browse all 400+ resume examples →