15 common resume mistakes that quietly cost you interviews
Jorge Sánchez·24. august 2026
Recruiters spot the same 15 mistakes in the first 30 seconds — weak verbs, buried achievements, generic summaries, mismatched keywords. Real before/after fixes for each.
Most "my resume isn't working" cases are not about talent, template, or template choice. They're about 15 recurring pattern errors that recruiters flag inside the first 30-second scan. Fix them and reply rate goes up measurably — usually within one application cycle.
Emplirao's CV analysis flags every one of the 15 mistakes below against your actual resume, per bullet and per section — and returns specific fixes grounded in your own experience.
Analyze my resumeThe 15 mistakes, ranked by impact
Every mistake with its one-line fix
| Mistake | Why it fails | One-line fix |
|---|---|---|
| 1. Generic summary at the top | Reads as filler — recruiter skips to bullets. | Cut it, or rewrite as 2 sentences naming your role + one measurable outcome. |
| 2. Weak leading verbs ("responsible for," "helped with") | Signal passivity; no ownership. | Replace with an action verb: led, shipped, built, cut, grew. |
| 3. Bullets with no metric | Recruiter can't compare you to other candidates. | Add a number, range, or time-to (see XYZ formula). |
| 4. Skills-only list without in-bullet context | Boolean parses match but relevance score stays low. | Every top skill also appears named inside one Experience bullet. |
| 5. Buried achievements (best story in the last bullet) | Recruiter reads first 1-2 bullets per role. | Move your strongest bullet to position 1 of your most recent role. |
| 6. Job titles that hide seniority ("Engineer" for a Staff role) | Boolean searches on level miss you entirely. | Use your actual title + a parenthetical clarification if needed: "Engineer (Staff level)". |
| 7. Dates in inconsistent format | ATS can't compute years-of-experience filters. | Pick one: MM/YYYY or Month YYYY. Apply everywhere. |
| 8. Missing recent role dates ("Present" without start) | Reads as evasion; filters treat as unknown tenure. | Always include start date: "Jan 2022 – Present". |
| 9. Photo on the resume (US/UK/Canada context) | Legal-risk flag for hiring teams; often auto-discarded. | Remove for US/UK/Canada roles. Keep for EU roles where cultural norm accepts it. |
| 10. Two-column layout | ATS scrambles text order. | Single column. Every time. |
| 11. Skills spelled inconsistently ("React.js" vs "React") | Boolean searches don't match variants. | Use the exact form from the JD. |
| 12. Too many technologies for the role | Signals inflation, not depth. | Cap Skills at 12-15 items directly relevant to the target role. |
| 13. Reference "available upon request" | Filler line; wastes real estate. | Delete. If they want references they'll ask. |
| 14. Cliché adjectives ("passionate," "detail-oriented," "team player") | Every candidate claims them; they carry zero signal. | Replace with a demonstrated example or delete. |
| 15. Hobbies/interests as a full section | Only helps for early-career or when directly relevant. | Cut after 3 years of experience unless a hobby ties into the role. |
The three fixes with the biggest impact
- Add a number to every bullet on the most recent role. If you can't find one, add a proxy ("cut deploy time by half a workday"). Ranks bullets from generic to comparable.
- Move your strongest bullet to position 1 of your most recent role. Recruiters read that specific slot 100% of the time.
- Replace every "responsible for" with an action verb + measurable outcome. This alone rewrites 60% of most weak resumes.
Do the three fixes above BEFORE spending time on layout, template, or design. Every hour on typography is wasted if the bullets still read as generic.
Once the mistakes are fixed, the next lever is length — the honest one-page vs two-page rule by experience level.
Read the resume length guide
