5 Resume Mistakes That Are Costing You Interviews
Why resumes get rejected
Most resume rejections happen for predictable, fixable reasons. It's rarely because you're unqualified — it's because your resume didn't communicate your qualifications clearly enough, quickly enough, or in the right format.
Here are the five mistakes that account for the vast majority of rejections.
Mistake 1: Writing a resume that isn't tailored to the job
The most common resume mistake is also the most impactful: sending the same resume to every application. A generic resume gets generic results.
Every job description contains signals about what the employer values most. Your resume should reflect those signals back. If the job posting mentions "cross-functional collaboration" three times, those words should appear in your resume — not because you're gaming a system, but because you need to demonstrate that your experience maps to what they're looking for.
The fix: before submitting any application, spend 10 minutes reading the job description carefully and update your bullet points to use similar language and emphasise the most relevant experience.
Mistake 2: Listing duties instead of achievements
The single biggest quality difference between strong and weak resumes is whether the bullet points describe what you were responsible for or what you actually achieved.
- Weak (duty): "Managed a team of 5 engineers."
- Strong (achievement): "Led a team of 5 engineers to ship a payment integration 3 weeks ahead of schedule, reducing checkout abandonment by 18%."
Every bullet point should answer the question: "So what?" If your bullet point doesn't tell the reader what changed, improved, or resulted from your work — it's a duty description, not an achievement.
The fix: go through every bullet point and ask whether a recruiter could tell whether you did your job well or badly. If they couldn't, add a result.
Mistake 3: Formatting that breaks ATS parsing
Applicant Tracking Systems parse your resume as plain text before a human ever sees it. Certain formatting choices cause your information to get scrambled or skipped entirely:
- Multi-column layouts
- Tables
- Text boxes and shapes
- Headers and footers
- Unusual fonts
- Icons instead of text labels
The fix: use a clean, single-column format. Save the design flourishes for the copy — clear, compelling language does more than any visual treatment.
Mistake 4: A skills section that lists soft skills
"Team player. Strong communicator. Detail-oriented." These phrases are meaningless on a resume. Every candidate claims them. They tell the recruiter nothing and take up space that could be used for something useful.
A skills section should list concrete, verifiable skills: programming languages, tools, certifications, methodologies. "Python, SQL, Tableau" is useful. "Results-driven" is not.
The fix: audit your skills section and remove anything that can't be demonstrated or tested. Keep the hard skills. Cut the adjectives.
Mistake 5: A summary that could apply to anyone
Most resume summaries open with something like: "Experienced professional with a proven track record of delivering results in fast-paced environments." This sentence is so generic it communicates nothing.
A strong summary is two to three sentences that tell a specific story: who you are, what you're best at, and what you're looking for. It should be so specific that it could only apply to you.
- Weak: "Results-driven marketing professional with 7 years of experience."
- Strong: "B2B SaaS marketer with 7 years in product-led growth. Specialise in lifecycle email and in-app campaigns — my last two roles saw trial-to-paid conversion rates increase by 22% and 31% respectively."
The fix: write your summary last, after you've written all your bullet points. Pull the best, most specific things up into a three-sentence summary that reads like a human wrote it.
The bottom line
Resume writing is a skill, not an art form. These five mistakes are all fixable in an afternoon. If you're applying consistently and not getting responses, work through this list systematically — there's a good chance at least one of these is the culprit.