It happens constantly. Someone takes a screening call, and somewhere in the middle the recruiter — politely, or not — implies they're lying about their experience. Red flags, apparently. A ton of them. The call ends, and the candidate spends the rest of the day replaying it, wondering if their own career is somehow fake.
If that's you: the call went badly, but probably not for the reason you think. Here's the thing nobody says out loud. The recruiter screen is not an interview. It's a filter. And treating it like an interview — a conversation between two professionals evaluating each other — is exactly how it hurts you.
What the screen is actually for
The recruiter on that call usually has a checklist, a quota of calls to get through, and a hiring manager somewhere behind them who gave a rough sketch of what “good” looks like. Their job is to match you against the sketch. Title history. Tidy dates. Plausible salary expectations. Notice period. Location. Right-sounding tech words in the right order.
What they are mostly not doing is evaluating whether your experience is real. They can't. A recruiter who has never built anything can't tell deep experience from confident summary — so they fall back on pattern-matching, because pattern-matching is the tool they have.
Which means when a recruiter says “red flags,” it almost never means I have caught you in a lie. It means your resume doesn't match the pattern I was told to look for. Short stints read as flaky. Contract roles read as “couldn't get hired properly.” A gap reads as something to hide. A title that jumps around reads as inflation. None of these are lies. All of them trip the filter. That distinction matters, because you can't argue with an accusation. You can absolutely deal with a pattern mismatch.
Make the doubt name itself
The worst move on a screen is defending your whole career at once. Vague doubt survives by staying vague — so your first job is to make it specific. The recruiter says: “I'll be honest, some of this experience seems… inflated.” You, calm, almost bored:
Which part reads that way? I'd rather clear it up now than have it hanging over the rest of the process.
That's the whole script. Don't fill the silence after it. Once the doubt has a name — “this title,” “this stint,” “this gap” — it shrinks to something you can answer in a sentence. If the recruiter can't name it, they'll usually retreat, and you've learned the doubt was never about you.
Pre-empt the pattern before it trips
Better than answering the doubt: get there first. Read your own resume the way a suspicious stranger would. Every short stint, every gap, every sideways title move — write one plain sentence for each, and say it before they ask:
- “You'll notice some short stints in the middle — those were contract roles, they ended on schedule, and the managers will confirm that.”
- “There's a gap after my last role. I was dealing with a family thing; it's resolved, and I've been building through it — I can show you what.”
- “The title says analyst but the work was engineering. I can walk through exactly what I shipped.”
One sentence each. Flat tone. No apology in your voice, because apology reads as confirmation. A pattern flag that gets explained before it's raised stops being a flag — it becomes evidence you know your own story.
When they flat-out call you a liar
Sometimes it isn't soft doubt. Sometimes the recruiter says, more or less, you didn't do this. The instinct is to plead. Don't plead — produce. “That checkout rewrite is live — I can send the link. The repo's public. And my manager from that team will take a reference call.”
Receipts beat adjectives every time. You will not convince a stranger of your honesty by describing your honesty. You convince them with an artifact: a link, a repo, a shipped thing, a named human who will vouch. If you have receipts, the accusation collapses. If you genuinely have none — no links, no humans, nothing — that's worth fixing before your next application, because every screen from here gets easier the moment your claims are checkable.
And notice what the accusation tells you about them. A recruiter who opens with you're lying and follows with but maybe I can still put you forward is running a softening play — shake your confidence, lower your salary expectations, make you grateful. You're allowed to end that call. Some pipelines aren't worth entering.
The salary trap, while we're here
Most screens end with the money question, and it's asked like a formality: “What are your expectations?” Answering first, against a band you can't see, is how people undercut themselves. Try: “Before I throw out a range — can you share the band for the role? I'd rather react to a real number than guess at one.” If they won't share it, that's information too. Note it, give a deliberately wide answer, and move on. The screen is a filter; don't hand the filter a reason.
The screen is going robotic anyway
The human recruiter screen — the checklist call, the vibes-based red-flag hunt — is being replaced by AI screens, right now. Here's why that matters for the red-flag problem specifically: a human recruiter's doubt, you can push back on — you can make it name itself, like we just did. A black box doesn't doubt you out loud. It just scores you, silently, on things nobody discloses. So all the pre-emption we covered has to move into your answers, up front, because there's no follow-up question coming to give you a second chance. The full playbook for that format is in how to prepare for an AI interview — go in with your one-sentence explanations already loaded.
Before your next screen
Three things, tonight, none of them hard:
- Audit your resume as a suspicious stranger. Write the one-sentence plain answer for every stint, gap and title jump.
- Rehearse the delivery until it's flat. Apology in the voice reads as confirmation — flat is what “nothing to hide” sounds like.
- Stage your receipts. Links, repos, shipped things, referees — one folder, so “I can send you that” is true before the call ends.
The recruiter screen filters out people who sound unsure of their own story. It is not a test of whether your story is true — which is exactly the problem with it, and exactly why it's beatable.
Back to all articles