Resume screening examples that separate red flags from good signals

Candidates with an employment gap on their resume get about 45 percent fewer interview callbacks than candidates without one. But candidates who explain the gap in a single sentence get close to 60 percent more interviews than candidates who leave it blank, even though the gap itself hasn’t gotten any shorter. ResumeGo tested this across more than 36,000 real job applications, and the finding cuts against almost every resume screening list you’ll find online.

Most of that advice, including a plain checklist approach, treats a gap, a short stint, or a vague bullet point as a red flag on its own. Spot it, flag it, move to the next resume. But the ResumeGo numbers say the fact barely predicts the outcome. What predicts it is whether anything near the fact answers the question it raises.

That’s the actual skill in resume screening, and it isn’t a checklist skill. It’s a reading skill. Below are five resume patterns that get mistaken for universal red flags, shown next to the version of the same fact that reads as a good signal, with the real phrasing that makes the difference.

Why the same fact gets two different verdicts

Think about what happens in a reviewer’s head when they hit an unexplained eight-month gap. There’s no information there, so the brain fills it in. Best case, they assume something boring. Worst case, they assume something disqualifying: fired, incarcerated, burned out. Either way, they’re guessing, and most reviewers guess toward caution, because a false reject costs them nothing and a false accept might cost them a bad hire you can’t easily undo.

Now add one sentence: “Left to care for a parent after a stroke, returned to work full time in March.” The gap is the exact same length. The reviewer isn’t guessing anymore. They have a bounded, specific, checkable story instead of an empty space they’re free to fill with the worst version.

That’s the entire mechanism behind the ResumeGo numbers. A red flag isn’t a fact. It’s a fact with no answer standing next to it. Once you see it that way, half of the standard red flag list stops being a list of facts to avoid and starts being a list of facts that need an answer.

What it costs you to screen by fact instead of by answer

Screening for facts instead of answers costs you twice. The first cost is rejecting people who did nothing wrong. A shift lead who worked four different retail jobs in three years looks like a job hopper on a fast scan. Read one line further and it might say she was laid off twice during store closures and picked up the next role within two weeks both times. That’s not instability. That’s resilience with bad luck attached, and a fact-based screen throws it out before anyone reads the second line, which is exactly what screening candidates properly instead of skimming them is supposed to catch.

The second cost runs the other way. More resumes than ever have none of the classic red flags and also none of the substance. No gaps, no short stints, clean formatting, a tidy summary line, three bullets under every job that say “responsible for,” “collaborated with,” or “results-driven team player.” Nothing to flag, and nothing to check either.

We’re seeing this shape constantly as candidates lean on AI to polish applications. The writing gets smoother while the evidence underneath it gets thinner, and a red-flag checklist waves the result straight through, because it was built to catch a bad word, not an absence of proof.

The test that replaces the checklist

Instead of scanning for facts, run every fact through one question: does anything within a sentence or two answer the obvious follow-up a hiring manager would ask out loud? Call it the so-what test. A gap says “January to September, unemployed.” So what? If the resume answers that, keep reading. If it doesn’t, that’s your flag, not the gap.

The so-what test works the same way in the other direction. A bullet that says “grew regional sales 34 percent in 18 months” answers its own so-what before you can ask it. A bullet that says “results-driven team player with strong communication skills” doesn’t answer anything, because there’s no claim in it to check. It just sounds like one. This only works if you’re clear on what “checks out” means for your role in the first place, the same reason a vague job description produces vague, clustered scores when you hand criteria to any screening process, human or AI.

This reframes what you’re actually screening for. You’re not hunting for bad words on a page. You’re checking whether each claim can survive one follow-up question. Resumes that survive move forward. Resumes that can’t get held for a closer look, not an automatic reject, because plenty of real, honest experience just hasn’t been written down with the answer attached yet.

Five resume patterns, read both ways

This is where the so-what test earns its keep. Here’s what it looks like against five patterns that show up on almost every stack of resumes you’ll screen this year.

The employment gap

Red flag: “2023 to 2024: no listed employment.” Nothing else on the resume references it.

Good signal: “2023 to 2024: cared for a family member post-surgery, kept certifications current through two online CE courses.” Same length gap. The second version answers the so-what before you have to ask it, and it hands you a second signal for free: she kept her credentials active on her own time.

The short stints

Red flag: Three jobs in three years, each 10 to 14 months, titles identical, no context anywhere on the page.

Good signal: Three jobs in three years, two of them ending in “company acquired” and “location closed,” with the third stint still active at 11 months and counting. The pattern looks identical on a fast scan. The reasons attached to it are the difference between a flight risk and someone who’s had bad luck with employers, not with effort.

The buzzword bullet

Red flag: “Hardworking, detail-oriented team player with excellent communication skills.” No number, no name, no task anywhere in the sentence.

Good signal: “Cut average ticket response time from six hours to 90 minutes by rewriting the intake form.” Same job title, same seniority level, one sentence you could verify with a single phone call.

The unchanged title

Red flag: “Shift lead, 2019 to present.” No other detail across five years, one line.

Good signal: “Shift lead, 2019 to present. Started managing one location, now covers three and trains new leads at each.” Twelve-person diner, no formal ladder to climb into, so the title never moved. The responsibility clearly did, and a title alone can’t show you that.

The suspiciously polished resume

Red flag: Flawless formatting, zero gaps, zero short stints, and also zero specific claim you could check if you tried. Every line reads like it was optimized for an algorithm rather than written by someone describing their own work, a pattern that’s only getting more common as candidates lean on AI to write applications.

Good signal: Clean formatting with at least one line per role that names a real number, a real tool, or a real outcome specific enough that you’d know instantly if it were invented. Polish isn’t the problem. Polish with nothing underneath it is.

Why you can’t just read closer

Why the manual version doesn’t scale

The obvious response is to apply the so-what test by hand to every resume. Read closer, ask the question yourself, catch what the checklist misses.

That works until the stack gets past 30 or 40 resumes in a week, which for most owner-operators screening their own front-desk or shift-lead roles happens constantly. The so-what test is still a judgment call, and judgment calls get worse at 9pm on the fortieth resume of the night than they were on the third. Two reviewers running the same test on the same resume will land in different places, because the test lives in someone’s head instead of anywhere consistent. If you’re already unsure whether that inconsistency counts as bias or just fatigue, it’s worth reading how fairness in AI screening actually gets defined, because the same question applies to a tired human reviewer.

What actually scales instead

The fix isn’t reading harder. It’s writing down, before you touch the pile, what a real answer looks like for each thing you actually care about, the same way you’d brief a person you were handing the stack to. That’s what Truffle’s resume screening layer does mechanically.

You define your must-haves, nice-to-haves, and deal-breakers once during setup, and AI Match scores every resume against that exact list, criterion by criterion, with the reasoning attached to each score instead of one number floating with no explanation. A gap without context scores low on “recent, verifiable experience.” A gap with a specific, checkable reason doesn’t get penalized for it.

You’re not asking the AI to decide who’s a good hire. You’re asking it to run the so-what test on your own criteria at a speed no person managing a stack of 40 can match, and it shows its reasoning every time so you can override anything that doesn’t sit right.

What this changes about how you screen

As more candidates get help from AI writing their resumes, the classic red flags are going to keep thinning out. Gaps get smoothed over. Short stints get reframed. Buzzwords get generated by the same handful of tools, which is part of why so many resumes are starting to read like they came from the same template. The old advice about spotting a strong resume by its writing alone is losing ground every quarter for exactly this reason.

That makes the so-what test more useful, not less. It doesn’t care how the resume was written. It only cares whether a specific claim survives one follow-up question. A resume that’s been smoothed by AI still has to say something checkable somewhere, or it fails the test regardless of how clean the formatting looks. And once a resume passes, the next question is whether the story holds up when the person is actually talking, which is exactly what layering a one-way interview or a skills assessment on the same criteria is for.

The bar worth aiming for isn’t how many red flags you caught this week. It’s how many facts you correctly separated from the answers standing next to them. That’s a different skill than pattern matching against a list, and it’s the one that still works once every resume looks equally polished.

Frequently asked questions about resume screening red flags

Is a gap in employment always a red flag?

No. Field research from ResumeGo found candidates who explained their gap in one sentence got close to 60 percent more interviews than candidates who left it blank, with no change to how long the gap actually was. The explanation, not the gap, drives the outcome.

How many jobs in a short period counts as job hopping?

There’s no fixed number that works on its own. Three jobs in three years with no context looks like instability. The same three jobs with layoffs, acquisitions, or closures attached to two of them looks like someone who’s had bad luck with employers, not someone who quits fast. Check the reason before you count the jobs.

What resume buzzwords should I ignore?

Phrases like “results-driven,” “team player,” and “detail-oriented” carry no information because they can’t be checked against anything. They’re not automatically dishonest, they’re just empty. Look past them for a number, a tool name, or an outcome you could verify with a phone call, and weigh the resume on whether that exists anywhere.

Can AI resume screening catch these context-dependent red flags?

Yes, if it’s scoring against criteria you defined rather than a fixed list of banned words. AI based resume screening done well checks whether a resume answers your specific criteria and shows you why it scored the way it did, the same test you’d run by hand, just applied consistently across every resume in a longer list of screening tools you might be comparing.

Every checklist you’ll find online, including the standard one, is a fine starting point for what to look for. What separates a fast screen from a fair one is what you do with what you find. Read for the answer, not just the fact, and the same stack of resumes starts sorting itself into people worth calling and people who just haven’t told you enough yet.

Try Truffle’s resume screening with a 7-day free trial, no credit card required, and see your next stack scored against your own criteria instead of someone else’s list.