Fixes & cleanup

Common resume mistakes that get you auto-rejected

Twelve specific mistakes that quietly kill applications — and the one-line fix for each. Most candidates make at least three.

Updated May 14, 20266 min read

Most resume advice is about what to add — better verbs, more numbers, stronger structure. Less talked about is the inverse: the specific mistakes that quietly kill applications, often before any human looks at them.

This guide is a punch list. Twelve mistakes, each with the why, the fix, and how to spot it on your own CV. Run your resume against this list and you'll catch issues that no amount of polish would have fixed.

1. The two-column layout with contact info in a sidebar

Why it kills: The ATS parser reads left-to-right, top-to-bottom. A sidebar with your name and email gets read as "Jane Doe Education BS Computer Science" — your contact info ends up inside your Education section. Many systems silently filter you out because the required fields are missing.

Fix: Single column, full width. Contact info on one or two lines at the top.

2. Resume saved as an image-only PDF

Why it kills: Some design tools (Canva exports under certain settings, Figma "image PDF" exports, PowerPoint "Save as PDF" with rasterised text) produce PDFs that are flattened bitmaps. The ATS can't extract text — it falls back to OCR, which is 60–80% accurate on a good day and often skips the document entirely.

Fix: Open your PDF and try to select your name with the cursor. If it highlights as text, you're fine. If it acts like a picture, re-export from a text-preserving tool (Word, Google Docs, LaTeX, or any modern resume builder that produces tagged PDFs).

3. Headers and footers carrying critical info

Why it kills: Most ATS parsers strip page headers and footers as boilerplate. If your phone number, email, or LinkedIn URL lives only in the page header, it's gone after parsing — you become uncontactable inside the system.

Fix: Put contact details in the document body, just under your name. Use headers and footers only for page numbers (which are visual-only and don't need to survive parsing).

4. "References available on request"

Why it kills: This line is universally redundant. Recruiters assume you'll provide references when asked. The line takes up space on a one-page resume that should be doing more useful work, and the cliché signals you copied a template without thinking about it.

Fix: Delete it. Use the space for a stronger bullet.

5. Job duties instead of achievements

Why it kills: A recruiter reading "responsible for managing the team's reporting workflow" learns nothing. Every PM in your company had that responsibility. The bullet differentiates none of them.

Fix: Rewrite each bullet as Verb + Action + Result. (More on this in our achievement bullets guide.) If you can't add a number or a comparative, the bullet probably wasn't STAR-worthy — drop it, don't fluff it.

6. Inconsistent date formatting

Why it kills: Two reasons. ATS parsers expect consistent date formats; some get confused when one role uses "Jan 2024 – Present" and another uses "01/2024 – Current". And a human reviewer notices the inconsistency immediately, registering it as carelessness.

Fix: Pick one format and apply it everywhere. "Month Year – Month Year" (e.g., "Mar 2022 – Aug 2024") parses cleanly and reads well to humans.

7. Typos in your own name, current role, or company

Why it kills: A typo in body copy is forgivable; a typo at the top of the page is a brand failure. It also breaks ATS field extraction — "Sneior Product Manager" doesn't match the title taxonomy.

Fix: Read the top two inches of your resume out loud before submitting. Yes, out loud. You'll catch errors your eye glides past.

8. Skills section with 40+ items

Why it kills: Long skills lists score worse, not better, because each item dilutes the signal. The ATS gives no extra credit for listing a skill you don't reinforce in your bullets — and a recruiter reads "Python, JavaScript, TypeScript, Ruby, Go, Rust, Java, C++, C#, PHP" as either bluffing or unfocused.

Fix: Cap at 12–15 skills, ordered by relevance to the role you're applying for. Cut anything you couldn't credibly discuss in a first-round interview.

9. Generic, untailored summary

Why it kills: "Results-driven professional with a passion for excellence" is the literary equivalent of static noise. It doesn't categorise you for the recruiter, doesn't carry keywords for the ATS, and reads identically to every other generic resume in the pile.

Fix: Two lines, role + domain + one piece of concrete evidence. Tailored to the JD. (Our summary vs cover letter guide goes deeper.)

10. Tools / skills you haven't used

Why it kills: It passes the auto-screen. It also sets up a brutal first-round interview when the engineer asks "tell me about the Kafka cluster you ran" and you don't have a real answer. Recruiters have long memories about candidates whose CV didn't match the conversation.

Fix: Match what's true. If you've touched a tool but aren't fluent, say so honestly — "exposure to" or "familiar with" is acceptable for adjacent skills. Don't claim ownership of work you didn't do.

Catch these mistakes before you submit

Upload your CV and the AI flags the ones that hurt your ATS score most — plus rewrites the bullets that need it. Free, no signup.

Try it free — no signup

11. Photo where the local market doesn't expect one

Why it kills: A photo on a US, UK, Canadian, or Australian resume can be filtered for legal reasons — many companies' policies require they reject CVs with photos to prevent bias-discrimination claims. In Germany, France, parts of Asia and the Middle East, photos are expected. Know your market.

Fix: Match local convention. If you don't know, default to no photo for English-language resumes targeting North America, UK, Ireland, Australia, and New Zealand.

12. The "interests" section that adds nothing

Why it kills: "Interests: hiking, photography, travel" is the most-cited filler section on a resume. It doesn't differentiate you (everyone hikes), it doesn't signal anything to the ATS, and on a tight one-page CV it crowds out content that would.

Fix: Cut it — unless an interest is genuinely unusual, demonstrably long-term, or relevant to the role. "Maintains an open-source kernel module since 2019" is interesting on an engineer's resume. "Enjoys travel" is not.

The quick audit

Print your resume. Take a red pen. Go through this list line by line. The candidates who consistently get interviews aren't the ones with the most polished prose — they're the ones who don't trip on the mistakes everyone else trips on.

Most of these are five-minute fixes. The cumulative effect on your hit rate is large.

← All guides