12 resume mistakes that kill your interview chances
Ranked by how often we see them in real ATS scoring sessions, with the fix for each.
Mistake 1: No metrics on any bullet
Most common. Recruiters scan for numbers — they're the cheapest credibility signal. If your resume has zero numbers, you're invisible.
Fix: quantify every bullet you can. Use reasonable estimates with confidence ('~$200k revenue impact based on internal data') when exact numbers aren't available.
Mistake 2: Soft skills as the headline
'Proactive team player with strong communication skills' — recruiters skip this entire line. Every candidate claims it.
Fix: demonstrate soft skills through specific outcomes. 'Led the engineering response during a 14-hour outage; wrote the post-mortem now used as the template across 6 squads' shows leadership AND communication without claiming either.
Mistake 3: Hiding GitHub / portfolio when it's strong
If your GitHub has 500 stars across projects, putting the link in tiny grey footer text is malpractice.
Fix: top-line it next to your name. Recruiters click.
Mistake 4: Activity bullets instead of outcome bullets
'Managed the roadmap' vs 'Narrowed the roadmap from 47 to 12 prioritised bets; team's on-time delivery rate went 58% to 87%.'
Fix: every bullet has to end on an outcome.
Mistake 5: Listing every framework you've ever touched
Twelve languages, four cloud providers, six databases. Recruiters quiz you on what's on the page.
Fix: list the 4–6 you'd be comfortable doing a live technical on.
Mistake 6: Two-column layouts in PDFs
Many older ATSes (still in use at large enterprises) parse two-column as one continuous column. Your skills section ends up garbled inside your bullets.
Fix: single-column. You can still make it visually clean.
Mistake 7: Mixed past and present tense in the same role
'Lead a team of 5 engineers; was responsible for system design' — half present, half past, screams 'didn't proofread.'
Fix: current role = present tense, past roles = past tense. Be consistent within each role.
Mistake 8: Hiding the impact of failed projects
Counter-intuitive but true: a clearly-named failure that you owned + learned from often beats a string of vague successes.
Fix: include one specific failure with what you changed afterwards. Senior interviewers actively look for it.
Mistake 9: Bullet bloat
Seven bullets per role, each ending with the same generic '... resulting in improved efficiency'. The recruiter stops reading at bullet 4.
Fix: 4–6 strong bullets for current role, 3–4 for past roles, 2–3 for old roles.
Mistake 10: Missing the company context
'Senior PM at Acme' tells the recruiter nothing if they don't know Acme.
Fix: one-line company descriptor for non-famous companies. 'Senior PM at Acme (B2B SaaS, $40M ARR, 180 people)' gives the recruiter the context to weight the rest.
Mistake 11: Buzzword soup in the summary
'Synergistic, data-driven, results-oriented professional...' — fails the 7-second scan.
Fix: lead with a measurable outcome. 'Senior PM with 8 years building 0→$10M ARR products at Stripe + 2 startups; led the team that shipped...'
Mistake 12: No India-aware version when applying in India
Applying in India with a US-formatted resume that lists salaries in USD, uses MM-DD-YYYY dates, and references US-only companies makes you look like you didn't bother.
Fix: keep a separate India version with INR-aware comp, DD-MM-YYYY dates, Indian companies for the 'similar to' framing.
Related role pages
- Software Engineer Resume Example · Software Engineer Interview Questions
- Product Manager Resume Example · Product Manager Interview Questions
- UX Designer Resume Example · UX Designer Interview Questions
Drop your file. See where you stand. The fix list unlocks free with your email.
Start freeThe ApplyVita Career Team builds the resume-scoring and job-matching tools at the core of ApplyVita. Our guidance is grounded in the same four-component ATS rubric our product scores resumes on — content and impact, keyword match, formatting, and skills — and in current recruiter and hiring-manager practice. Every guide is checked against that rubric before it is published, and updated as hiring norms change.