Resume Red Flags: 12 Things Recruiters Notice, and How to Fix Each

A resume red flag is anything that makes a recruiter doubt you before they've read your evidence. The ones that cause instant rejection are usually fixable in an afternoon: bullets that list duties instead of results, typos, a layout that software scrambles, and a resume that clearly wasn't written for this job.

Gaps and short stints are different: they rarely sink an application on their own, as long as you explain them. Red flags matter more than they should because the first pass is short. Ladders' 2018 eye-tracking study measured an average initial screen of 7.4 seconds. In a window that short, one visible problem can plausibly outweigh a page of good work. Below are twelve red flags in two tiers, ordered by how much they cost you, each with a fix, followed by four 'red flags' that aren't.

Red flags that get resumes rejected (fix before you send)

1. Duties instead of results

'Responsible for managing vendor relationships' is true of everyone who held the job. A recruiter reading ten of those lines learns you were employed, not that you were good. Fix: rewrite each bullet as action, context and result, with a number where you have one. The ACR resume format has a fill-in template.

2. Typos and inconsistent formatting

A typo on a document you had unlimited time to check reads as carelessness, especially for roles that claim 'attention to detail'. Inconsistency does the same quietly: 'Jan 2023' in one role and '01/22' in the next, or three different bullet styles. Fix: read the resume aloud once, then check every date uses one format and every role uses the same layout.

3. A layout the software scrambles

Two-column designs, tables, text boxes and contact details in a page header often come out of an applicant tracking system jumbled: dates separated from titles, skills attached to the wrong job. The recruiter then sees that mess, not your design. Fix: a single-column layout with standard headings (Experience, Education, Skills). The reasoning is in how to format a scannable resume.

4. A generic resume sent to every job

When none of the posting's key terms appear, the resume doesn't come up in the recruiter's search, and if it does, it reads as a near-miss. Fix: pull the 10 to 15 keywords that matter from the posting and work the true ones into your bullets. See how to pick keywords from a job description.

5. Claims you couldn't defend in an interview

An inflated title, a skill you used once, or a suspiciously round number ('increased revenue 300%') invites exactly the follow-up question you can't answer. Many recruiters cross-check titles against LinkedIn, and interviewers ask how you got your numbers. Fix: if you can't explain how you got a number, use a range you can defend, or describe the outcome without one.

6. Generic, buzzword-heavy phrasing

'Results-driven, dynamic self-starter with a passion for synergy' says nothing, and so does a summary that could sit on anyone's resume. Generic phrasing reads as filler, whoever or whatever wrote it. Fix: replace each adjective with the evidence behind it. 'Detail-oriented' becomes the audit you ran with zero findings.

7. Missing or broken basics

No dates on roles, no location (or 'open to relocate' when it matters), an email address from your teens, a LinkedIn URL that 404s. Each is small, and each makes the recruiter work harder or wonder what's being hidden. Fix: month and year on every role, a city and country, a plain firstname.lastname email, and a link you've clicked yourself.

Red flags that need context, not panic

These raise a question rather than end the conversation. A short, factual answer on the resume itself is usually enough.

8. Employment gaps

A gap of a few months is unremarkable. Longer gaps are common too: caregiving, health, study, layoffs, a move. LinkedIn added a dedicated Career Break option to profiles in 2022 for this reason. What reads badly is an unexplained hole. Fix: list the break like a role, with dates and one line ('Career break: relocated to Austin; completed AWS Solutions Architect certification'). You don't owe anyone private details.

9. Short stints and job-hopping

Several roles under a year can suggest you leave when it gets hard. Often there's a structural reason the resume doesn't show. Fix: label it. Mark contract and freelance roles as such and group them under one heading, and add a few words where a company was acquired, shut down or ran layoffs. One context line turns a pattern into a story.

10. A career change or a step down in title

A finance manager applying for a product role, or a director applying for a senior IC job, makes a recruiter wonder whether you know what you're signing up for. Fix: a two-line summary at the top that states the move and the bridge: the transferable work you've already done. Then order your bullets so the most relevant evidence comes first, not the most recent.

11. Too long or too thin for your stage

Three pages for a role with four years of experience reads as an inability to prioritize; half a page for a senior role reads as thin evidence. Fix: match length to career stage. Our guide to how long a resume should be gives page and word-count ranges by stage.

12. Outdated content

An objective statement ('Seeking a challenging position…'), 'References available upon request', tools nobody uses any more, or a full address. None is fatal, but together they date the resume and its owner. Fix: replace the objective with a short summary, drop the references line, and cut tools that are more than a few versions old unless the posting asks for them.

Myths: things that aren't red flags

• Two pages. Fine once you have the evidence to fill them. One page is the norm for students and early-career candidates, not a rule for everyone.
• PDF instead of Word. Mainstream applicant tracking systems read a text-based PDF. The real problem is a scanned image or a design-tool export with no selectable text. What an ATS really does covers this.
• No photo. For US, UK and Canadian applications, leaving the photo off is the norm, not a gap.
• A single short role. One stint under a year, with a reason, is ordinary. It's a pattern of them that needs the context above.

How to check your resume for red flags

Do the fold test first: cover the bottom half of page one and ask whether a stranger could tell your current role, your strongest skills and one result. Then run it through the free resume gap analysis. It flags several of the red flags above automatically: bullets without results or numbers, layouts that scramble in parsing (columns, merged text, repeated headers), missing section headings, and length that's off for your career stage. It doesn't flag employment gaps or job-hopping; those need your judgement and a line of context.