5 Red Flags in Resumes Every Recruiter Should Catch

Every recruiter has felt it — the resume reads perfectly, the keywords line up, the brands are tier-one, and yet something is off. By the time the offer stage comes around, two or three uncomfortable facts have surfaced that would have saved everyone a week if they had been caught up front.

After reviewing a few hundred thousand resumes across our customer base, five patterns stand out. None of them automatically disqualifies a candidate — but each of them is a signal worth confirming before you book an interview panel's time.

1. The dates do not add up

Watch for roles with month-and-year resolution in some places and year-only in others. "2022 – 2023" sitting next to "Mar 2024 – Present" is almost always hiding a gap or an overlap. The year-only entries are the ones to probe.

Confirm in the screen: "Can you walk me through what you were doing between June and November 2023?" If the answer is confident and specific, move on. If it's vague — a sabbatical that keeps resetting its definition, a "consulting" period with no clients named — treat it as a yellow flag.

2. Titles that outgrow the company

A "Vice President of Engineering" at a 12-person startup is not the same as a VP of Engineering at a 1,500-person company — but on paper, the title is identical. We see candidates re-title themselves ambitiously in later resumes, especially after a small-company exit.

Confirm in the screen: "How many people reported to you? How many layers deep was your org?" The answer should match the title. If a VP had three direct reports and no manager layer between them and ICs, that's a Director of Engineering role elsewhere.

3. Keyword soup in the skills block

Fifteen languages, four cloud providers, every modern framework, and six databases — all claimed with equal confidence. Modern ATS systems favour keyword density, so candidates stuff. A good resume names the skills someone has shipped production code with, not the ones they've read a tutorial on.

Confirm in the screen: Pick the two most impressive items and ask "What was the last thing you built with X?" Expertise reveals itself in texture: specific library versions, specific bugs they had to debug, specific trade-offs they picked over alternatives. Keyword stuffers answer in generalities.

4. Achievements without numbers

"Improved customer satisfaction." "Reduced build times." "Grew the team." These are not achievements — they are activities. Candidates who have actually driven outcomes write with numbers: "cut p95 latency from 420ms to 90ms", "grew engineering from 4 to 11 across two years", "lifted NPS 32 → 51 in six months".

Confirm in the screen: "What were the metrics before and after?" If a candidate can't produce them within a minute of thought, the achievement was probably someone else's and they got credited by proximity.

5. The missing "why I left"

Every mid-career candidate has moved companies. The strong ones can articulate a clean story for each move: "the product-market fit I joined for didn't materialise and I wanted to work on something further along", "my manager left and I didn't vibe with his replacement", "I'd always wanted to try B2B after four years in consumer". The weak ones leave gaps you have to fill in with assumptions.

Confirm in the screen: "What took you from Company A to Company B?" Listen for coherence, not for sanitisation. Candidates with messy but honest reasons ("got put on a PIP I didn't agree with, found a better role before it was finalised") are usually more trustworthy than ones with polished stock answers at every move.

The thirty-second gut check

Scan for all five of these on the first read-through. One is noise. Two is a yellow flag. Three or more is a signal that the resume has been engineered more than lived — spend the screen call confirming before you book the panel. Your time, and your hiring manager's time, is the scarce resource you're protecting.

If you use Recruitizr, RecruiterIQ's resume screening tool automatically surfaces title inflation, gap periods, and keyword-stuffing patterns in its candidate insight panel — so you can go into every screen call already knowing which of the five flags, if any, is worth probing.