Resume Mistakes That Get Filtered Out: What Engineering Recruiters Reject

Resume Mistakes That Get Filtered Out: What Engineering Recruiters Actually Reject

Most “top resume mistakes” lists are written by career coaches who haven’t read 10,000 engineering resumes. The mistakes that actually filter you out at FAANG, AI labs, top startups, and finance tech are different from generic career advice. They’re specific patterns that engineering recruiters and hiring managers spot in five seconds and use as quick rejection signals. This guide covers the real filters — based on what engineering hiring teams actually screen on — and what to do instead.

Top-Third Wasted

The top third of your resume is the highest-leverage real estate you have. Recruiters read top-down and stop when they’re convinced (either way). Wasting it on filler kills your chances even when the rest of the resume is strong.

Common waste patterns

Objective statement. “Seeking a challenging software engineering position where I can apply my skills to solve interesting problems.” Universally redundant. Cut.
Career summary in third person. “Experienced software engineer with a passion for distributed systems…” Reads as marketing copy. Cut or rewrite as a one-line lead-in only at staff+ levels.
Skill rating bars. “Python: ★★★★☆” — visually large, conveys nothing, makes engineering reviewers groan.
Mission statement. “Driven by a commitment to engineering excellence and continuous learning.” Filler.

Use the top third for: name, contact info, current role title, and the strongest 1–3 bullets from your most recent job. That’s it.

Vague Bullets Throughout

The single most common rejection driver. Bullets that describe responsibilities instead of outcomes filter you out at the recruiter screen even when your overall background is strong.

Vague patterns to fix

“Worked on the [X] team” — replace with what you actually did.
“Responsible for [Y]” — passive; replace with active accomplishment.
“Helped improve [Z]” — too weak; if you only helped, the bullet doesn’t earn space.
“Various contributions to [project]” — meaningless.
“Significantly enhanced performance” — quantify or cut.
“Developed scalable solutions” — empty buzz; describe a specific solution.

Cover the rewrite framework in our Quantifying Impact guide.

Buzz-Word Stacking

“Synergized cross-functional initiatives to leverage innovative solutions for enterprise-scale transformation.” Engineering hiring managers read this and reject. The pattern: corporate-speak that says nothing concrete. Words to look for in your own resume and remove or replace:

Synergized, leveraged, championed, spearheaded, orchestrated, drove (most uses), pioneered, transformed (without specifics)
“Innovative solutions,” “best-in-class,” “next-generation,” “cutting-edge”
“Stakeholder management” used as filler — describe specifically what you did with which stakeholders
“Strategic thinking,” “results-driven,” “detail-oriented” — soft-skill claims unbacked by examples

Replace with concrete verbs and specific work. See our action verbs guide for the calibration.

Skills Section Overload

Listing 80 technologies you’ve touched once each. Recruiters and hiring managers see this and infer “this candidate doesn’t actually know any of these deeply.” The pattern is so common that an enormous skills section now actively hurts you.

Better approach

Group by category. List only what you’d be comfortable being interviewed on. Example:

Languages: Python, Go, C++
Frameworks: gRPC, FastAPI, React (basic)
Infrastructure: AWS (EKS, RDS, Kinesis), Terraform, Docker
Data: PostgreSQL, Redis, Kafka

“React (basic)” is honest about partial knowledge — this is fine. “JavaScript, TypeScript, React, Vue, Angular, Svelte, Next.js, Nuxt.js, Gatsby, Remix” is not.

Lying or Stretching

The most expensive mistake — caught later, but career-ending when caught. Common patterns:

Stretching dates to hide gaps. Background checks compare your dates against tax records and prior-employer references; mismatches end the loop.
Title inflation. Calling yourself “Senior Engineer” when your actual title was “Software Engineer II” gets caught at reference check.
Claiming work you didn’t do. “Architected the payments platform” when you wrote 30% of the code under a tech lead. Fine on the resume; fatal during the interview when you can’t defend the architectural decisions.
Listing degrees you didn’t finish as if you did.

The fix: be precisely accurate. Calibrate verbs to your actual contribution. Honest descriptions of substantial work are more impressive than over-claims that fall apart in interviews.

Company Filter: Working Backward

Recruiters scan company names. If your most recent role is at a company they don’t recognize, and you don’t make the work specific enough that the work signals quality, you can get filtered.

What helps

Brief context line for unknown companies: “Acme (Series-B fintech, $40M ARR, payments infra for SMB)”
Specific scale numbers in bullets that prove the work was substantial
Notable customers or partners (“partnered with Stripe and Adyen on the integration layer”)

What hurts: assuming the recruiter will know what your previous company does. Many won’t.

Tooling-Specific Resumes That Don’t Match the Role

You apply to a backend role; your resume is heavy on iOS work because that’s what your last job was. The recruiter doesn’t see the connection. Even when your fundamentals carry over, the resume signals “this person is iOS, not what we’re hiring for.”

The fix

Lead with the most-transferable bullets. Reorganize bullets so the systems-design and language-fundamentals bullets appear first; the platform-specific bullets later. You’re not lying; you’re emphasizing what the reader cares about. Tailoring this way takes 10 minutes per application but materially shifts who advances you.

Education Section Mistakes

Listing high school after college. Unnecessary unless you went to an exceptional one and you’re a new grad.
GPA below 3.5 listed for new grads. Hurts more than helps. Below 3.5, omit. 3.7+ helps. 3.5–3.7 is usually fine.
GPA listed at staff+ level. By 8+ years, your shipped work is the resume. Drop GPA.
“Relevant coursework” as a long list at senior+ levels. Remove. New grads can include 3–5 courses; mid-level and beyond, drop.
SAT / GRE scores past your first job. Cut.

Length Mistakes

Padding to two pages when one would be tighter. Recruiters notice padding immediately. If your second page has only 4 lines, condense.
Cramming senior+ experience into one page. By staff level, you have substance to fill two pages well; forcing one creates eye-strain and signals you don’t have enough to say.
Three+ pages. Almost never. The exception: academic CVs for research roles, where publication lists drive length.

LinkedIn / Resume Mismatch

Recruiters cross-reference LinkedIn while reviewing your resume. If your LinkedIn shows different dates, different titles, or no record of the most-recent role on your resume, you raise flags. Fix one or the other; usually keeping LinkedIn current and matching is the simpler ongoing maintenance.

Photos, Personal Info, and Demographics

For US applications: no photos, no marital status, no nationality, no birthdate, no political/religious info. These are conventions; including them flags you as either inexperienced with US hiring or applying from a different cultural norm. For non-US markets: check local conventions.

Format Mistakes That Trigger Rejection

Multi-column layouts that misparse in the ATS
Decorative fonts that look unprofessional or fail to render
Color blocks dominating the layout
Charts, infographics, “skill clouds” visually big but convey no information
White text on white background for ATS keyword stuffing — universally caught now and treated as a black mark
Resumes saved as image-only PDFs (e.g., scanned printouts) — break ATS parsing entirely

See ATS-Friendly Resume Formatting for the deeper treatment.

Job-Hopping Without Context

Five jobs in three years, no narrative. Recruiters worry about retention; they pass. The fix: where job changes had specific reasons (acquisition, pivot, layoff), include a brief one-line context. Where you genuinely jumped frequently, the resume itself is harder to fix; focus on landing roles where the next role is a 4+ year commitment.

Frequently Asked Questions

What’s the single biggest mistake in your experience?

Vague bullets. Engineers under-quantify by default — they think the work speaks for itself, and don’t realize that recruiters and hiring managers can’t tell impactful work from filler without specifics. The fix is mechanical: every bullet gets re-read with the question “what would I want to know if I were the reader?” and rewritten with concrete numbers, scope, and outcomes.

How honest should I be about gaps?

Specific and brief is better than vague. “Career break, 2023, full-time caregiver” or “Sabbatical to study ML, 2024 (completed Andrew Ng’s specialization, built three projects)” reads better than an unexplained gap. Don’t lie; don’t over-explain. A short context line is sufficient.

What about layoffs?

Increasingly common, increasingly accepted. You don’t need to disclose layoff status on your resume. If asked in interviews, “the team was reduced as part of broader org restructuring” is a fine answer. Don’t pretend you chose to leave; recruiters can verify employment status.

How can I tell if my resume is making the right impression?

Three signals: (1) trusted engineering peers can identify your seniority and area of expertise within 30 seconds of reading; (2) recruiters who reach out reference specific things from your resume rather than generic “your background looks interesting”; (3) you advance from cold applications at a meaningful rate (1-in-20 or better for a tailored application is reasonable). If you’re failing all three, the resume needs work; if you’re failing only one, look at where the breakdown is.

Should I get my resume professionally reviewed?

Engineering peer review beats career-coach review almost always. Career coaches optimize for HR-flavored advice that doesn’t match what engineering reviewers care about. Senior engineers and engineering managers in your network give better feedback because they’ve reviewed real candidates for real loops. Send your draft to 2–3 trusted engineering peers and ask for the harshest version of their feedback.