Resume red flags: what to weigh, what to ask, what to drop
On 13 November, Google’s AI Overview for “resume red flags” in India opened with this line: recruiters “often scan a resume in under six seconds”. It then listed what gets a résumé rejected in that time: typos, job hopping, unexplained employment gaps, no quantified results, Canva-style formatting. Nearly every result on the page is written for job seekers trying to avoid the list.
Turn the page around and it reads differently. If recruiters really are rejecting on those signals in six seconds, some of them are discarding capable applicants, for reasons that have nothing to do with the job. In March 2022, LinkedIn announced its career breaks feature with a survey finding that 64 percent of women had taken a career break, and that half of hiring managers believe people returning from one have often gained valuable soft skills. An unexplained gap is on almost every resume red flags list. It’s also one of the commonest things in a working life.
This post sorts twelve common red flags into three groups: what a job-matched score should weigh, what a person should ask about, and what to stop counting. It closes a five-post series whose starting point is building a candidate scoring model.
What counts as a resume red flag?
A resume red flag is a sign that an applicant may not fit the role or that something they claim needs checking. The useful red flags are about the job: missing evidence of the core work, claims with no specifics, or a mismatch between title and duties. Gaps, short tenures and formatting are questions or noise, not reasons to reject.
The test for any red flag is simple. Does it tell you something about whether this person can do this job? If yes, it belongs in the score. If it might, depending on the story behind it, it belongs in the interview. If no, it belongs nowhere.
Group one: red flags a job-matched score should weigh
These relate directly to the work. A scoring model built from the job description should already pick them up, because each one is the absence of evidence a criterion asks for.
1. No evidence of the core work. The job is outbound sales; the résumé describes account management with no prospecting. This is the most important red flag on the list and the one six-second scans miss most, because the title often looks right.
2. Claims with no specifics. “Handled multiple projects”, “drove growth”, “responsible for customer satisfaction”. Generic claims aren’t lies, but they’re not evidence either. A score should give partial credit at most, and the interview should ask for the specifics.
3. Title and duties don’t match. “Team Lead” with bullet points that describe individual contributor work, or “Manager” at a company of four. Score the duties, not the title. The title tells you what the employer called the job; the bullets tell you what was done.
4. Skills listed but never used. A skills section with fifteen tools, none of which appear in any role description. The skills list is the least reliable part of most résumés. Score the tools that show up inside the work, and treat the list as a hint to ask about.
HireQwik’s résumé scores carry the quoted résumé line behind each criterion, which makes group one visible: a candidate who scores low on “customer conversations as main work” has no quoted line for it, and a reviewer can see in seconds that the evidence is missing rather than hidden.
Group two: red flags a person should ask about
These might matter. They might not. The résumé alone can’t tell you, and a score that guesses will get it wrong in both directions. The right move is to keep the candidate in play and ask.
5. Employment gaps. Caregiving, illness, study, a layoff, a failed business, a move. All common. Ask what they did and whether anything in that time is relevant. Don’t penalise the gap itself.
6. Short tenures. Three jobs in two years can mean a candidate who leaves at the first difficulty. It can also mean contract roles, startups that shut down, or a layoff wave. Look at the direction: are the responsibilities growing? Then ask.
7. Overlapping or vague dates. “2022-2024” for two different full-time roles, or years with no months. Sometimes it’s a freelance project alongside a job; sometimes it’s padding. One question settles it.
8. A sudden change of field. A facility manager applying for a customer success role. That’s one of the off-target patterns in our published hiring data, and often it is exactly that. But a career-changer with a clear reason and some relevant evidence can be a strong hire. If the score puts them in the review band, a person reading the evidence can make the call.
Each of these becomes a single interview question, not a filter. Write it next to the candidate’s name in the review band so whoever speaks to them next asks it. In a HireQwik first round, the AI interview builds its questions from the job and the candidate’s résumé, so the conversation goes into the work the résumé describes. The recording and transcript let HR read back what the candidate said before the gap question comes up in the next round.
Group three: red flags to stop counting
These show up on almost every list, and they say nothing about whether someone can do most jobs. Counting them turns screening into a test of background, polish or luck.
9. Typos and grammar slips, for roles that aren’t about writing. For a content writer or a customer email role, writing is the job, and it’s in the score already as a criterion. For a warehouse supervisor or a field technician, one typo tells you nothing. Score writing where the job needs it; ignore it where it doesn’t.
10. Formatting and design. A plain Word document and a polished Canva layout describe the same person. Some graphic layouts are harder for software to read, which is a tooling problem, not a candidate problem. Score the content.
11. College name. The college tells you where someone studied at 18. It doesn’t tell you what they can do at 25. We’ve written about why the graduate funnel breaks at the résumé screen for exactly this reason.
12. “Overqualified.” A senior person applying for a junior role might leave quickly. They might also be relocating, returning from a break, or genuinely want less responsibility. Ask. Filtering them out by default throws away people who often ramp up fastest. Our post on overqualified applicants in volume hiring covers when the worry is real.
Notice what group three has in common: each flag is easy to see in six seconds. That’s why they get used. Ease of spotting isn’t the same as relevance.
These flags also stack. Picture an applicant for an operations coordinator role: a tier-3 college, a two-year gap for caring for a parent, and a plain résumé with one typo. Every one of those would cost a point in a six-second scan, and together they put the résumé in the reject pile. Yet the work described before the gap is exactly the scheduling, vendor follow-up and reporting the role needs. A score built on the work ranks that person in the top band. A scan built on group three never sees them.
What about AI-written résumés?
A newer worry: résumés that read as if a chatbot wrote them. Polished, generic, every bullet starting with a strong verb, nothing specific. That’s not really a new red flag. It’s red flag number two, claims with no specifics, produced at scale. The fix is the same: a score that credits specific evidence and gives little for generic claims, and an interview that asks about the claims. We went into the signals in more detail in how to detect AI-generated résumés.
How to put the three groups to work
Turning this into a screening routine takes one change to how you read résumés, and one change to how you set up the score.
In the score: make sure each criterion asks for evidence of the work, and give partial credit, not full, for generic claims. That covers group one automatically. Leave gaps, tenure, college and formatting out of the criteria entirely.
In the review band: when a person reads the middle of the ranked list, they look at group two. A gap or a short tenure gets written down as something to ask about, and never counted against the candidate.
In the interview: each group-two note becomes one question. “You were at two companies in 2023. What happened at the first?” Thirty seconds of the candidate’s answer is worth more than any guess from the résumé.
Once hiring closes: check whether any of the people you hired carried a group-two or group-three flag. If several did, that’s evidence those flags weren’t predicting much, and worth sharing with the hiring managers who still count them.
A red-flag question sheet for the review band
When a group-two flag shows up in the middle band, the useful move is to turn it into one question and know what a good answer sounds like. Keep a sheet like this beside the reviewer, and pass the question on to whoever speaks to the candidate next.
| Flag | Question to ask | A reassuring answer | Worth a closer look |
|---|---|---|---|
| Gap of six months or more | “What were you doing between March and November 2024?” | A clear reason (care, health, study, a layoff, a move) and how they kept their skills current, if relevant | Vagueness, or a story that changes when you ask a follow-up |
| Three or more roles in two years | “What made you move from your last two roles?” | Contracts ending, a company closing, a layoff, or a clear step up each time | Every exit blamed on a manager or a team |
| Overlapping dates | “These two roles overlap in 2023. Were they both full-time?” | A freelance project alongside a job, or a notice period overlap | Two full-time roles claimed at once with no explanation |
| Change of field | “What drew you from facilities management to customer success?” | A specific reason plus something they’ve done that connects the two | No reason beyond “looking for a change” |
| Title above the duties described | “How many people reported to you as team lead?” | A straight number and a description of what leading meant there | An answer that avoids the number |
| Generic claims only | “Tell me about one project you described here, and what you did in it.” | A specific situation with their own actions and a result | Only “we” and no detail when asked twice |
Two cautions. First, ask every candidate with the same flag the same question; a gap question asked only of women, or only of older applicants, is how bias gets back in through the interview. Second, the column on the right is a reason to dig, not to reject. Plenty of good people answer a gap question badly the first time because they’ve been punished for it before.
From flagged résumé to booked interview
The point of sorting red flags this way is to keep good candidates moving. A résumé with a gap and strong evidence of the core work should land in the invite band, not the reject pile. From there, the move to interview is one action: approve the band, and each person picks an interview time from the emailed link, nudged by reminders until the cut-off. The voice interview runs 10-20 minutes; its verdict sits on a four-step scale from Strong Go to No Go, and every question’s score quotes what the candidate said. The decision stays with HR.
For where the flags fit in the wider process, see running applicant screening in two passes, and for keeping the people you nearly hired, re-scoring your talent pool.
Take the red-flag list your team actually uses, written or not, and sort it into the three groups. Anything in group three, stop counting this week. Want to watch a job-matched score handle the rest on your applicants? Book a walkthrough, or hear the interview questions yourself.
Frequently asked questions
What are red flags on a resume?
Resume red flags are signs that an applicant may not match the role or that a claim needs checking. The useful ones relate to the job: no evidence of the core work, claims with no specifics, or duties that do not match the title. Gaps and short tenures need a question, not a rejection.
Is an employment gap a red flag on a resume?
Not on its own. Career breaks for caregiving, health, study or layoffs are common, and a 2022 LinkedIn survey found 64 percent of women had taken one. Treat a gap as a question to ask in the interview, and judge the candidate on the work they have done and can do.
Should job hopping disqualify a candidate?
Usually not automatically. Short stints can come from contract roles, layoffs, startups closing or a bad early fit. Look at the pattern and the reasons: several short roles with steadily growing responsibility tell a different story from repeated exits at three months. Ask about it rather than filter on it.
See your own candidates screened
Book a 30-minute demo. Bring a live JD and we'll screen against it, then start with a pilot on your own candidates before committing to anything.
Existing customer? Sign in