Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Common Resume Mistakes & Red Flags

Avoiding mistakes is just as important as doing things right. This guide covers the most common resume pitfalls, from formatting disasters to content red flags.

Formatting Mistakes

1. Inconsistent Formatting

The #1 formatting killer. Examples:

  • Mixing date formats: “Jan 2026” in one place, “01/2026” in another
  • Different bullet styles: • in some places, - in others
  • Inconsistent spacing between sections
  • Some job titles bolded, others not

Fix: Pick a format and apply it uniformly. Use find-and-replace to check consistency.

2. Wrong File Format

  • ❌ Submitting as .docx (formatting can break across Word versions)
  • ❌ Submitting as .pages (recruiters can’t open this)
  • ❌ Submitting as .jpg/.png (not searchable, not ATS-friendly)
  • ✅ Always PDF unless specifically asked otherwise

File naming:

  • ❌ resume_final_v3_REAL.pdf
  • ❌ myresume.pdf
  • ✅ Jane_Doe_Resume.pdf

3. Poor Visual Hierarchy

If everything looks the same, nothing stands out.

Problem: All text is the same size, no bold, no structure Fix:

  • Name: 16-18pt, bold
  • Section headers: 12-14pt, bold, uppercase
  • Body text: 10-11pt
  • Use bold for company names and roles

4. Too Much White Space / Too Little White Space

Too much: Resume looks empty, suggests lack of experience Too little: Wall of text, hard to read, looks cluttered

Fix: Aim for 70-80% text coverage. Use consistent margins (0.5-0.75“).

5. Using Columns or Tables

Many ATS systems can’t parse multi-column layouts or tables correctly.

Fix: Stick to a single-column layout for ATS compatibility.

6. Headers/Footers for Important Info

Some ATS systems ignore content in headers and footers.

Fix: Put your name and contact info in the body of the document, not in the header.

Content Mistakes

7. Typos and Grammar Errors

This is an instant rejection for many recruiters. It signals carelessness.

Common errors:

  • “Led” vs “Lead” (past tense is “Led”)
  • “It’s” vs “Its” (possessive has no apostrophe)
  • “Effect” vs “Affect” (usually you want “effect” as a noun)
  • Inconsistent capitalization
  • Missing periods at end of bullets

Fix:

  1. Use spell check
  2. Read it backward (catches different errors)
  3. Read it out loud
  4. Have 2-3 people review it
  5. Wait a day, then review again

8. Objective Statements

“Seeking a challenging position where I can utilize my skills…”

This is outdated and wastes space. Recruiters know you’re seeking a position — you applied.

Fix: Remove it entirely. If you have 5+ years of experience, consider a brief professional summary instead.

9. Including a Photo

In the US and Canada, photos on tech resumes are:

  • Unnecessary
  • Can introduce unconscious bias
  • Takes up valuable space
  • Some companies auto-reject resumes with photos (to avoid bias claims)

Fix: Remove your photo. Exception: Some international resumes (EU, Asia) may require them.

10. Listing References

“References available upon request” is assumed and wastes a line.

Fix: Remove it. Prepare a separate reference sheet if asked.

11. Including Personal Information

Don’t include:

  • Age / Date of birth
  • Marital status
  • Nationality / Citizenship (unless relevant for work authorization)
  • Social security number
  • Photo
  • Height / Weight
  • Religious affiliation

Exception: Work authorization status can be relevant: “Authorized to work in the US” or “Requires H-1B sponsorship”

12. Irrelevant Work Experience

If you’re applying for a software engineering role, your high school retail job doesn’t need 5 bullet points.

Fix:

  • Keep relevant experience detailed (3-5 bullets)
  • Minimize or remove irrelevant experience
  • If you must include it (to fill gaps), use 1-2 bullets focusing on transferable skills

13. Listing Every Course You’ve Taken

“Relevant Coursework: Intro to CS, Data Structures, Algorithms, Operating Systems, Databases, Networks, Software Engineering, Discrete Math, Linear Algebra, Calculus I, Calculus II, Calculus III, Physics I, Physics II…”

Fix: List 3-5 courses directly relevant to the target role. If applying for a backend role: “Distributed Systems, Databases, Operating Systems, Computer Networks”

14. Overusing Buzzwords

“Synergized cross-functional teams to leverage cutting-edge solutions for scalable, robust, enterprise-grade applications…”

Fix: Use concrete language. What did you actually build? What was the result?

15. Passive Language

“Was responsible for the development of…” “Duties included managing…” “Tasks involved writing…”

Fix: Use active voice with strong verbs: “Developed,” “Managed,” “Built”

Red Flags That Get You Rejected

16. Employment Gaps (Unexplained)

Gaps aren’t dealbreakers, but unexplained ones raise questions.

Fix: If you have a gap, briefly address it:

  • “Career break for personal projects and skill development (2024-2025)”
  • “Open source contribution and freelance work (2024)”
  • Or address it in your cover letter

17. Job Hopping (Pattern)

Multiple roles lasting <1 year each can be a red flag.

Fix: If you have short stints, consider:

  • Combining contract/freelance work under one entry
  • Omitting very short roles (a few months)
  • Addressing it briefly if there’s a good reason

18. Exaggerated Titles

Being a “VP of Engineering” at a 2-person startup you co-founded is misleading.

Fix: Use accurate titles. If your official title was misleading, you can clarify: “Software Engineer (Founding Engineer)”

19. Exaggerated Impact

“Improved performance by 500%” “Increased revenue by $10M” (as an intern)

Fix: Be honest and provide context. “Improved query performance by 40% for the user dashboard” is more credible than vague massive numbers.

20. Copy-Pasted Job Descriptions

Bullet points that read like job descriptions, not achievements.

❌ “Responsible for developing and maintaining web applications using React and Node.js” ✅ “Rebuilt the customer dashboard in React, reducing load time by 60% and increasing user engagement by 25%”

Technical Resume Mistakes

21. Listing Too Many Technologies

Listing 30+ technologies makes it look like you’ve touched everything but mastered nothing.

Fix: List 15-20 key technologies you’re genuinely comfortable with.

22. Outdated Technologies

Listing jQuery, PHP 5, or SVN prominently suggests you haven’t kept up.

Fix: Keep your skills current. Remove or de-emphasize outdated technologies unless the job specifically requires them.

23. No GitHub / Portfolio Link

For software engineers, not having a GitHub or portfolio is a missed opportunity.

Fix: Create a GitHub, pin your best projects, and link it on your resume.

If your GitHub, portfolio, or project links are broken, it looks careless.

Fix: Test every link on your resume before submitting.

25. Private Repositories

If your GitHub link leads to all private repos, it’s as good as no link.

Fix: Make your best projects public. Keep private what needs to be private, but have visible work.

The “So What?” Test

For every bullet point, ask: “So what?”

Example: “Built a REST API with Node.js” → So what? Who used it? What did it enable?

Better: “Built a REST API with Node.js serving 5K daily users, enabling the mobile team to ship the iOS app 2 weeks ahead of schedule”

Example: “Wrote unit tests for the application” → So what? How many? What coverage? Did it catch bugs?

Better: “Added 200+ unit tests achieving 85% code coverage, catching 12 bugs before production deployment”

Resume Review Checklist

Run through this before every submission:

Formatting

  • One page (for early career)
  • Consistent fonts and sizes
  • Consistent date format
  • Consistent bullet style
  • Proper spacing
  • No columns or tables
  • PDF format
  • Proper file name

Content

  • No typos or grammar errors
  • No objective statement
  • No photo (US/Canada)
  • No personal info (age, marital status)
  • No “references available upon request”
  • Strong action verbs
  • Quantified impact
  • Relevant experience prioritized
  • Tailored to the role

Technical

  • Working links (GitHub, LinkedIn, portfolio)
  • Skills are current and honest
  • Skills match the job description
  • No skill inflation
  • Projects are well-described

Final Check

  • Reviewed by at least one other person
  • Read out loud for flow
  • Passed the “So What?” test
  • Would you interview this person?