The mistakes that sink resumes are not exotic. They are a handful of patterns that repeat across industries, seniority levels and countries, and most are invisible to the person who wrote the resume, because a document you have read forty times stops looking like anything.
Here are the seven that cost the most interviews, with the weak version and the fixed version side by side. None require talent to fix. They require noticing.
1. A layout the parser cannot read
Two columns. A sidebar with your skills in it. Your job history inside a table. Your name drawn inside a header graphic. Skill rating bars showing you at four stars out of five in Excel.
All of this looks designed. Most of it breaks when an applicant tracking system extracts the text. A parser reading left to right across a two-column page can interleave your sidebar into your employment history. Text inside an image does not exist at all to the machine.
The fix: one column, plain text, standard section headings, nothing important inside a table, text box or image. Your resume should look slightly boring. Boring parses.
Find out which of these you have
Resume Radar flags all seven of these problems in roughly 30 to 60 seconds, for free.
Check my resume freeThe quick test: select all the text in your resume file, paste it into a plain text editor, and read it. If the order is scrambled or chunks are missing, that is what the system sees. The ATS compatibility score in Resume Radar does the same check more thoroughly and names the specific problems.
2. Bullets that describe the job instead of the work
This is the most common and the most expensive mistake on the list. A job description tells the reader what the role involved. It does not tell them whether you were any good at it.
Weak:
Responsible for managing vendor relationships and procurement processes.
Strong:
Renegotiated contracts with 12 vendors during the 2025 renewal cycle, cutting annual spend by $310,000 while keeping every service level agreement intact.
Weak:
Assisted with the migration of legacy systems to the cloud.
Strong:
Migrated 34 legacy services to AWS over seven months with no unplanned downtime, retiring two data centres and cutting infrastructure cost by 41 percent.
The test for every bullet: could my replacement have written this exact sentence? If yes, it describes the chair, not the person who sat in it.
The fix: action verb, what you did, what changed because of it. Start with the verb. Never "responsible for", never "assisted with", never "helped to".
3. No numbers anywhere
Numbers are what makes a claim checkable, and checkable claims are what recruiters trust. A resume with no figures at all reads as a set of assertions.
People skip this because they think their work is unquantifiable. It almost never is. If you cannot find a percentage, use a count, a timeframe, a size or a frequency.
- How many people, customers, accounts, tickets, stores?
- How long did it take before, and how long after?
- How big was the budget, the team, the codebase, the audience?
- How often: daily, weekly, twice a quarter?
Weak:
Improved the onboarding experience for new employees.
Strong:
Rebuilt onboarding for 60 new hires a year, cutting time to first productive week from 3 weeks to 8 days based on manager sign-off.
And a version with no percentages at all, which is still strong:
Ran onboarding for every new hire across 4 offices, replacing a 40-page PDF with a 5-day structured plan now used company-wide.
A caution: every number you add is a question you have invited. Do not use a figure you cannot explain in an interview.
4. A skills section made of adjectives
"Team player. Excellent communicator. Detail-oriented. Passionate about innovation. Self-starter."
None of these are skills. They are self-assessments, everyone writes them, and they take up the space where a recruiter searching the database for a specific tool would have found you.
The fix: the skills section is for nouns. Tools, technologies, methods, languages, certifications, systems, platforms. Specific ones.
Weak:
Skills: Communication, teamwork, problem solving, Microsoft Office, hard working
Strong:
Skills: SQL, Python (pandas, scikit-learn), dbt, Snowflake, Tableau, Airflow, A/B testing, experiment design, German (fluent)
Soft skills are not worthless, they are just in the wrong place. Prove them in a bullet instead. "Excellent communicator" says nothing; "Wrote the incident postmortem template now used by all four engineering teams" says the same thing and is verifiable.
Find out which of these you have
Resume Radar flags all seven of these problems in roughly 30 to 60 seconds, for free.
Check my resume free5. Contact details the machine cannot find
Your phone number in the document header. Your email inside a text box next to a photo. Your LinkedIn URL drawn as an icon with no text behind it.
Parsers treat headers and footers inconsistently. Some read them, some skip them, and you cannot know which is on the other side. Text inside images is never read. So a resume can go out with no reachable contact details from the system's point of view, and nobody will ever tell you.
The fix: name, phone, email, city, LinkedIn URL, and GitHub or portfolio if relevant, in plain text in the body of page one. Write the LinkedIn URL out rather than hiding it behind an icon.
Resume Radar reports contact detection explicitly for phone, email, LinkedIn, GitHub and portfolio. If something you know is in your document is not detected, you have just found a real and silent problem.
6. A summary that could be about anyone
The top third of page one is the most valuable real estate on your resume, and a lot of people fill it with this:
Results-driven professional with a proven track record of success and a passion for delivering value in fast-paced environments.
That sentence fits a nurse, a warehouse manager and a solutions architect equally well, which is exactly why it is worthless.
Strong:
Backend engineer, 7 years, mostly payments infrastructure at fintech scale. Rebuilt a settlement pipeline handling 2 million transactions a day and cut reconciliation errors by 90 percent. AWS Certified Solutions Architect.
Three lines. Function, years, specialization, one concrete achievement, one credential. Anyone reading that knows in four seconds what you are and whether to keep going.
The fix: cut every adjective about yourself and replace it with a fact. If a sentence in your summary could appear on a stranger's resume unchanged, delete it.
7. One resume for everything, with the relevant experience buried
The same document goes to forty postings, and in each one the thing that particular employer cares about is on page two, fourth bullet down, under a job from 2019.
You do not need forty resumes. You need one strong base and the discipline to reorder it for the jobs you actually want.
The fix, ten minutes per application that matters:
- Rewrite the summary's first line to name the function you are applying for.
- Reorder the skills list so the ones in the posting come first.
- Promote two or three bullets that match the role, and cut two that do not.
- Use the market's job title, not your company's internal one. "Growth Wizard" becomes "Growth Marketing Manager", with the internal title in parentheses if you need it for accuracy.
Do this for the ten jobs you genuinely want and send the base version to the rest. Tailoring forty applications is not sustainable and tailoring none is why the forty go nowhere.
How to find which of these you have
You cannot see your own resume properly any more, which is the real problem behind all seven.
Run it through Resume Radar. It is free, needs no account and no credit card, accepts PDF, DOC and DOCX up to 5 MB, and takes roughly 30 to 60 seconds. You get an overall score from 0 to 100 with a letter grade, eight section scores, the document and contact checks, a numbered list of recommendations, and suggested rewrites showing your original line next to a stronger one with the improvement type labelled. Tick the rewrites you can honestly defend and download the improved resume as a Word file.
Mistakes one and five show up in ATS compatibility and contact detection. Two, three and six show up in content impact and lexical analysis. Seven shows up in market alignment. Examples: /resume-radar/examples.
Then, when the resume does its job and the call is booked, the hard part moves to the conversation. That is what InterviewMan is built for: live answer suggestions during the interview, at $30 per month or $12 per month billed yearly.
Frequently asked questions
Which of these mistakes matters most?
Mistake two, bullets that describe the job instead of the work, costs the most interviews overall, because it affects the human decision about whether to call you. Mistake one, an unreadable layout, is more urgent though, because it can stop your resume from being found at all. Fix the layout first, then spend real time on the bullets.
How long should my resume be?
One page for students and early career, two pages for most experienced professionals, and three only when a genuinely long publication or project record demands it. Length is not the real issue anyway. A two-page resume made of specific achievements reads faster than a one-page resume made of vague duty statements.
Is it lying to reconstruct a number I did not formally measure?
Not if the number is a fair, honest estimate of something real and you can explain how you arrived at it. "Roughly 40 support tickets a week" based on your own recollection of your queue is fine. Inventing a 60 percent improvement that nobody measured is not, and it is exactly the claim an interviewer will follow up on.
Should I include a photo on my resume?
It depends on where you are applying. In the United States, the United Kingdom, Canada, Ireland and Australia, the convention is to leave it out. In much of continental Europe and parts of Asia it is normal or expected. Either way, keep your contact details as plain text outside the image, because nothing inside a photo is readable by a parser.
Do these rules apply to non-technical jobs?
Yes. Duty statements, missing numbers, adjective-based skills sections and unparseable layouts appear just as often in marketing, nursing, teaching, finance and operations resumes as in engineering ones. The only part that varies by field is what counts as a specific skill, and what you count as a measurable result.
See also
Find out which of these you have
Resume Radar flags all seven of these problems in roughly 30 to 60 seconds, for free.
