Resume red flags don't announce themselves. The resumes that require the most scrutiny often look the most polished — they've been written by someone who understood exactly what to put in and what to omit. The interviewer's job is to close that gap between what the resume projects and what the candidate actually did.
Most interview red flags are caught late — if they're caught at all. An interviewer who didn't read the resume carefully arrives with no specific questions, the candidate delivers their best stories, and the evaluation is based on impression rather than interrogation. The hire goes through. The problems surface later.
Here are five patterns that recur constantly in resumes, what they usually signal, and — most importantly — the exact question to ask when you find one.
Vague metrics that can't be interrogated
Every resume consultant tells candidates to quantify their achievements. The problem is that this advice produces a lot of numbers that sound meaningful but aren't. "Improved conversion by 40%." "Reduced costs by $2M." "Grew the team by 300%." Each of these statements collapses under basic questioning.
What was the baseline before the improvement? Over what time period? Was the candidate the cause, or did they report on a result that came from something else? Did they own the initiative or were they one of twelve people working on it?
A suspicious metric is any metric that (a) appears prominent on the resume, (b) lacks context that would explain it, and (c) would be very hard to verify independently. These aren't automatically lies — but they're often compressed descriptions of partial involvement that don't survive a direct question.
"The 40% conversion improvement you mention — walk me through how that was measured, what the baseline was when you started, and what specifically you changed that drove it."
Title inflation and scope ambiguity
"Director of Engineering" at a 15-person startup and "Director of Engineering" at a company with 400 engineers are different jobs in every dimension that matters — team size, scope, budget authority, architecture complexity, organizational influence. Resumes routinely elide this context.
Title inflation is particularly common in candidates who progressed rapidly at small companies or startups. They held genuine titles, but the scope behind those titles was much narrower than the same title implies elsewhere. This isn't necessarily a disqualifier — but it needs to be understood before you evaluate fit.
Watch for: seniority claims that don't match the company size visible elsewhere on the resume, leadership language used for contributions that were likely individual in scope, and founder-adjacent titles at very early-stage companies that indicate breadth without depth.
"When you were Director of Engineering at [company], how many engineers reported directly to you? What was your budget authority, and how many of the major architectural decisions were yours versus someone above you?"
Unexplained timeline gaps
Employment gaps are not inherently red flags. Parental leave, illness, caregiving responsibilities, extended job searches, career pivots — all of these explain gaps that have nothing to do with performance. The problem is when gaps are simply absent from the resume rather than addressed.
A well-prepared candidate has a ready answer for any gap. An unprepared one, or one who hoped the gap wouldn't be noticed, will be caught off-balance by a direct question. Either way, you want to ask before you make a hire decision, not after.
More revealing than the gap itself is usually what the candidate says when asked about it. Someone with a clean explanation gives it immediately and specifically. Someone who is evasive, who pivots away, or who gives an explanation that doesn't quite fit the timeline — that's the signal worth investigating further.
"I noticed there's a gap between [date] and [date] on your resume. Can you tell me what you were doing during that period?"
Buzzword stacking without depth
The modern resume has been heavily optimized for applicant tracking systems, which scan for keywords. The result is a skills section that reads like a technology vendor's marketing page — fifteen languages, six frameworks, four cloud platforms, assorted methodologies — with no indication of depth in any of them.
This is different from a genuinely broad technical background. The distinguishing question is: can the candidate go deep on any of it? A real practitioner can explain tradeoffs they navigated, things that surprised them, ways the tool fell short of expectations. A keyword-stacker can define what the thing does.
Buzzword stacking is also common in non-technical roles. "Strategic thinker." "Data-driven decision maker." "Cross-functional collaborator." These phrases appear constantly and mean nothing without an example that demonstrates the capability they claim.
"You list [technology/skill] prominently. Tell me about the most difficult production problem you've debugged involving it — what was the issue, how long did it take you to find it, and what did you learn?"
AI-generated cover letters and application materials
This one is newer and more nuanced. A cover letter generated by ChatGPT isn't necessarily a disqualifier — many hiring processes don't weigh cover letters heavily, and there's an argument that using available tools is simply efficient. But an AI-generated cover letter that makes specific claims about the candidate's fit for this specific role — and those claims don't hold up in conversation — is a signal worth probing.
The issue isn't the tool; it's the gap between the application's articulation and the candidate's ability to speak to the same points in their own words. A candidate who used AI to write a strong cover letter but can't explain their own claimed motivations in an interview is showing you that the application was more prepared than the candidate.
This extends to any materials where specific, tailored knowledge is claimed. If a cover letter articulates a precise understanding of your product's architecture or market position, it's worth asking the candidate to demonstrate that understanding without the document in front of them.
"Your cover letter mentions [specific claim about your company or role]. Can you tell me more about what you know about that and how it informed your interest in this position?"
The pattern behind all five flags: they all share the same structure — a claim that looks compelling at the surface level but may not hold up when interrogated with a specific question. The interview's job is to find out which ones do and which ones don't.
Building the habit of flag-first reading
Reading a resume for red flags is a skill that improves with practice, but it requires deliberate technique. The default mode — reading a resume to decide whether to advance a candidate — produces a charitable read. You're looking for evidence of fit, so you find it.
Flag-first reading inverts this. You read specifically for things that don't add up, things that require more context to evaluate, and things that are claimed but not substantiated. Each flag generates a question. The interview tests whether the flag was warranted or not.
Most flags clear. A vague metric often has a completely solid explanation that just didn't fit on the resume. An unexplained gap is usually mundane. Title inflation at a startup is normal. Finding flags doesn't mean you've found disqualifying problems — it means you've found specific questions worth asking, which is exactly what a good interview requires.
AskSharp finds these flags automatically
Upload a resume and get probe areas, targeted questions, and an answer cheat sheet in 30 seconds.
What to do when a flag doesn't clear
Sometimes a candidate can't explain their own metric. Sometimes the scope behind a title really was much narrower than it looked. Sometimes the cover letter demonstrates deeper understanding of the company than the candidate can demonstrate in person.
When a flag doesn't clear, the right response is to note the specific discrepancy in your post-interview write-up — not as a disqualifier, but as an unresolved concern. If you're making a hire decision without resolving it, you're taking on known risk. If the concern is significant enough, it warrants a follow-up conversation before the offer.
The goal of resume screening for interview red flags isn't to eliminate candidates with imperfect resumes. It's to ensure that your evaluation is based on what candidates have actually done, not on what they were able to put on a page or script in advance. AskSharp automates this process — it reads the resume, identifies probe areas, and generates the targeted questions so you can focus on the conversation itself.