12 Common Resume Mistakes (and How to Fix Each One)

By · Published · Updated · 8 min read

Key takeaways

  • Most resume problems are about clarity: vague bullets, missing keywords, and layouts software cannot read.
  • Specific, true results beat adjectives. Say what you did, not what kind of person you are.
  • Spelling errors and wrong contact details are the easiest mistakes to fix and the most costly to leave.
  • Check your file as plain text, because that is how many systems read it.

A recruiter may spend only a short time on a first look at your resume, and software may read it before any person does. Most resumes that do not get a call fail for ordinary reasons that are easy to fix. Here are twelve of the most common, with the fix for each.

1. A generic summary

"Hardworking, passionate professional" could describe anyone. Fix it by naming the role, your experience level and two real strengths. See how to write a resume summary.

2. Bullets that list duties instead of results

"Responsible for customer service" says what the job was. "Resolved billing queries for about 30 customers a day and escalated complex cases to the team lead" says what you did. Only use a number if it is true. See resume bullet point examples.

3. Missing keywords from the job post

If the job asks for a skill you have and you do not use the same words, a person or a system may miss it. Compare your resume with the post using the job description matcher.

4. Skills you cannot back up

Listing tools you have only heard of invites a practical question you cannot answer. Keep only the skills you can discuss.

5. A layout software cannot read

Tables, text boxes, columns that mix up reading order, headers and footers with key details, and icons instead of words can all confuse parsers. Use one column, standard headings and real text. Check with the ATS resume checker.

6. Wrong or unprofessional contact details

A mistyped phone number or an email address from years ago means missed calls. Use a simple email based on your name, and test your number.

7. Spelling and grammar errors

Read the resume aloud, run a spell checker, and ask another person to read it. Make sure the tense is consistent: present for your current job, past for older ones.

8. Too long, or padded

One or two pages is enough for most people. Cut old, unrelated jobs and anything that does not help for this role.

9. Personal details that do not belong

Unless the job post asks, details such as age, marital status or a photo are not needed in many countries and can take space from useful content. See our guide to resume formats by country.

10. Inconsistent dates and titles

Use one date format throughout, keep job titles accurate, and explain real gaps briefly. Do not change dates. See how to explain an employment gap.

11. A file that is hard to open

Send a text-based PDF unless the employer asks for a Word file, and name it clearly, for example "Asha-Patel-Resume.pdf". Check it opens on a phone.

12. No clear target

A resume that tries to fit every role fits none. Choose the role you are applying for and make the top third of the page about it.

Quick final check

  1. Read it aloud for errors.
  2. Compare it with the job post for missing true keywords.
  3. Test the file as plain text and with an ATS checker.
  4. Confirm phone, email and links work.
  5. Save it as a PDF and open it on your phone.

Start fresh with a free template or fix your existing file in the resume builder.

Frequently asked questions

What is the biggest resume mistake?

Sending the same generic resume to every job. Matching your summary, skills and top bullets to each job post is the change that helps most.

Should I use a fancy design?

Not usually. Plain one-column layouts are easier for software and people to read. Spend your effort on content.

Are typos really a problem?

Yes. Spelling and grammar errors are easy for a reader to notice and suggest a lack of care. Read the resume aloud and ask someone else to read it too.

How can I check my resume quickly?

Run it through an ATS checker to see how the text is read, and compare it with the job post using a matcher.

Sources