Every recruiter knows to look for employment gaps or a typo-riddled resume. But the red flags that actually predict a bad hire are subtler. They require reading a resume with pattern recognition, not just a checklist. Here are seven that experienced recruiters catch — and newer ones often don't.
1. Titles That Don't Match Compensation Expectations
"Senior Engineer" at a three-person startup and "Senior Engineer" at a FAANG company are completely different roles. Title inflation is rampant at small companies — candidates often receive inflated titles in lieu of salary. The red flag isn't the title itself, but a pattern of escalating titles across roles where the company size, scope described, and compensation level don't add up.
What to look for: A "Director of Engineering" who managed zero people. A "Lead Architect" at a company with 8 employees. Ask about team size and reporting structure early.
2. Vague Accomplishment Bullets
"Improved system performance" tells you nothing. "Reduced API response time by 40% by implementing Redis caching" tells you the candidate knows what they did and why it mattered. Vague bullets are a common sign that a candidate either didn't do meaningful work or is actively hiding the scope of their contribution.
Pattern to watch: A resume that reads like a job description rather than an achievement record. Responsibilities listed, not outcomes. This is particularly telling in roles where measurable outcomes should exist (engineering, sales, marketing).
3. Tenure Patterns That Suggest a Performance Problem
Short tenures aren't automatically a red flag — layoffs, acquisitions, and contract work are all legitimate. The flag is a pattern of 6–10 month stints at full-time roles without explanation. One short tenure is a data point. Three in a row is a pattern worth investigating.
The critical distinction: Are the short stints explained (startup failed, contract completed, company acquired)? Or do they appear to be conventional roles that ended abruptly? Candidates with performance-based terminations rarely volunteer this — but they often have dates that don't quite add up if you look carefully.
4. Certification Overload With No Experience to Match
Eight certifications from the last 12 months, with no job history that required any of them. This pattern — common in candidates trying to break into a field — isn't dishonest, but it means the credentials don't reflect practical ability. Certifications validate that someone studied for an exam, not that they've solved real problems.
What a healthy cert profile looks like: Certifications earned incrementally, aligned with roles held at the time, with renewals that suggest active practice. A Security Engineer who earned the CISSP five years into their security career is credible. Someone who earned six cloud certs before their first cloud job is not.
5. Education Listed Without Graduation Dates
Omitting a graduation year is almost always intentional. The most common reasons: the candidate didn't finish the degree, the degree is very old (age discrimination concern), or the institution's reputation is something they're not eager to highlight. None of these are disqualifying on their own, but the omission itself warrants a follow-up question.
6. The "Consultant" Gap Filler
A 14-month gap covered by "Independent Consultant" or "Freelance [Role]" with no named clients and no deliverables listed is a common gap-covering technique. Genuine consulting work has clients, projects, and outcomes. When a resume lists consulting that looks like it was retroactively added to fill time, it's worth asking directly about the work produced.
7. Skills Listed That Contradict the Experience Timeline
A candidate who lists "10 years of experience with Kubernetes" when Kubernetes wasn't released until 2014 is either rounding up aggressively or fabricating. This category of error is more common than most recruiters expect — especially in technical skill sections where candidates list tools they've touched but not mastered.
Technology timelines are hard to memorize. RecruiterSignal flags these inconsistencies automatically — if a claimed experience duration doesn't match when a technology existed, it surfaces the conflict so you can ask the right question in the screen.
The Bottom Line
Red flags don't mean automatic rejection. They mean targeted questions. The goal of resume review is to know exactly what to probe in the phone screen — not to make hiring decisions from paper alone. The best recruiters treat red flags as a prioritized list of hypotheses to test. AI tools can help surface those hypotheses faster so you spend your conversation time where it matters most.