11 resume mistakes that get you auto-rejected (and the fixes)

The same handful of mistakes show up in resume after resume, and they cost real interviews. Each of these is fixable in under a minute. None require a redesign.

1. Two-column layout that breaks PDF parsers

Looks great in preview, fails in production. ATS systems read PDF text in document order, not visual order. A sidebar-on-the-left layout typically gets read as: full sidebar, then full main column, scrambling your section flow. Use a single column or a parser-tested two-column template. For the mechanics, see our ATS resume guide.

2. Contact info in the header or footer

Many ATS parsers strip headers and footers entirely. Your email and phone need to be in the body of the document, at the top. If the recruiter cannot find your contact details after the parser is done, your resume is effectively dead.

3. Photos, logos, and graphic skill bars

In the US and UK, photos invite bias-claim risk and many recruiters discard resumes that include them. Logos and skill bars are non-text content the parser drops entirely. Whatever they communicate visually is invisible to the scoring layer.

4. Buzzword soup as your opening

"Passionate, results-driven team player with a track record of delivering high-impact solutions." The ATS does not weight this. Recruiters skim past it. Replace with a specific summary: role, seniority, two strongest experience signals, target role.

5. Bullets without numbers

"Worked on the API." versus "Refactored the billing API to cut p99 latency from 850ms to 120ms across 12M weekly requests." The second bullet does the same job in the same number of lines and tells the reader you can measure your work. If you do not have a metric, use scope: "across our top 20 enterprise accounts" or "in the first quarter after launch."

6. Inconsistent date formats

"Jan 2021 - Present" in one role, "01/2021 - Now" in another, "2021-2024" in a third. Parsers either pick one and miss the others, or they reject all of them. Pick a format and use it everywhere.

Recruiters spend roughly 6-8 seconds on the first scan. Your job is to make those seconds count, then survive the parser-level scoring that decides if a human ever scans it at all.

7. The wrong file format

Submit PDF unless the application explicitly asks for .docx. Some posts insist on Word; respect that. Otherwise PDF is more reliable. Never submit a Pages, Keynote, or RTF file. Never submit a Google Docs link.

8. Long paragraphs instead of bullets

A 5-line paragraph under your most recent role buries every useful signal. Convert to bullets. Each bullet is one verb, one accomplishment, one outcome.

9. Section titles the ATS does not recognize

"Where I have been" instead of Experience. "What I bring" instead of Skills. ATS parsers anchor on standard section names. Use them: Experience, Education, Skills, Projects, Certifications. Save the creativity for the bullets.

10. Including everything you have ever done

That summer job in 2009 is not helping. Cap your resume at the last 10 years for most roles, last 15 for senior. Drop the second high school internship. Drop the languages you have not used in 5 years. The space you save makes the relevant content load louder.

11. AI-generated bullets that sound like AI

"Leveraged synergistic frameworks to deliver impactful outcomes." Recruiters have learned to spot this in a heartbeat, and they trash the resume. If you use AI, use it to compress what you already wrote, not to invent new accomplishments. More on that in should you let AI write your resume.

The fix list

• Audit your current resume against this list. Almost everyone is hitting at least three.
• Switch to a single-column or parser-verified template.
• Move contact info into the body if it is in a header.
• Replace adjective-heavy bullets with verb + metric versions.
• Run an ATS check before each submission.

Key takeaways

• Most rejections happen at the parser, not the recruiter. Fix layout first.
• Numbers and scope beat adjectives. Every bullet earns its line.
• Use the section names the ATS expects. This is not where you get creative.
• If you use AI, let it edit, not author.