How to handle a candidate who lies in an interview
On this page
- Exaggeration and fabrication are different problems
- What to do in the room, in the moment
- What not to do in the room
- Verifying after the interview
- A worked example
- A decision guide: what the finding actually means
- If you discover it after an offer, or after they've started
- Where claims get stretched most often
- A checklist for this situation
- Questions people ask
Handle a suspected lie in an interview by asking a specific, neutral follow-up rather than an accusation, noting the exact inconsistency for later verification, and deciding afterward, with evidence rather than a gut read, whether it was exaggeration or a fabrication that disqualifies the candidate. Most interviewers either let a lie slide because confronting it feels awkward, or jump straight to a conclusion they can't support in the room. Neither serves you as well as a good follow-up question and a verification step after the call.
Exaggeration and fabrication are different problems
Not every inflated claim is the same kind of risk, and treating them the same either lets serious fabrication through or disqualifies people for the kind of embellishment most candidates do under interview nerves.
- Exaggeration inflates something real: claiming more ownership of a team result than they actually had, rounding up a metric, or describing a supporting role as if they led it. Common, worth probing and scoring down, but not automatically disqualifying on its own.
- Fabrication invents something that didn't happen: a job that wasn't held, a degree not earned, a specific result that was never achieved, or a project they were never involved in at all. This is a different category and usually a disqualifying one once confirmed.
The line between them is whether there's a real thing underneath the claim, just described generously, or nothing underneath it at all. You often can't tell which one you're looking at from the room alone, which is why the next question matters more than a snap judgment.
What to do in the room, in the moment
Instead of accusing: Ask this:
"That doesn't sound right." --> "Walk me through the specifics --
what exactly did you do, week by
week, on that project?"
"I don't believe that number." --> "How did you measure that? Who
else would have seen that number
at the time?"
"You said something different --> "Earlier you mentioned [X] -- can
last time." you connect that to what you just
described? I want to make sure
I've got the sequence right."
"Are you lying to me?" --> "That's a pretty senior-sounding
scope for that stage in your
career -- what did the reporting
structure actually look like?"
The pattern in every version on the right: ask for detail that a real experience would have and a fabricated one usually doesn't. A true story gets more specific and more consistent the more you ask; a fabricated one tends to stay vague, shift, or produce details that don't fit together when you ask a second time from a different angle.
- Ask the same thing twice, later, differently worded. A genuine memory holds up; a constructed one often drifts in small, telling ways.
- Ask who else was there. A real claim usually has a checkable witness: a manager, a teammate, a client. Hesitation or vagueness about who could confirm it is itself informative.
- Write down the exact words, not your impression. "Said they 'led' the migration, then later said they 'were part of the team that did' it" is checkable. "Seemed off" is not.
What not to do in the room
- Don't accuse outright. An accusation you can't back up shuts the conversation down and can create real legal exposure if you're wrong and the candidate feels defamed or discriminated against.
- Don't let it go because confronting it feels awkward. Silence reads as acceptance, and you lose your best chance to get the specific detail you'll need to verify or disqualify later.
- Don't decide in the room. A single inconsistency can be a memory slip, nerves, or genuinely how the candidate experienced their own role. Treat it as a flag to check, not a verdict to deliver on the spot.
Verifying after the interview
The interview gives you a flag; verification gives you a fact. Three steps, roughly in order of effort:
- Check it against what's already documented. Compare the claim to the resume, the LinkedIn profile, and anything else the candidate submitted. Inconsistencies between the interview story and the written record are often the easiest catch.
- Verify employment and dates directly. A former employer will often confirm little beyond dates and title, but that's frequently enough to catch a fabricated role or an inflated seniority. See how to verify employment history for the method and a call script.
- Ask a reference the specific question the candidate's answer raised. Not a general "would you rehire them," but the exact thing you're trying to confirm: "Can you tell me about their role on the migration project specifically -- who owned what?" The reference check template has more on getting past generic answers.
A worked example
Invented, to show the follow-up pattern in use.
Candidate: "I led the rollout of our new inventory system across all twelve locations."
Interviewer: "That's a big rollout. Walk me through the first location specifically -- what did week one look like, and who else was on the project with you?"
Candidate: "I mean, I was part of the core team. There were a few of us. I handled a lot of the training materials."
Interviewer, later in the interview, from a different angle: "Earlier you mentioned the inventory rollout -- if I called your manager at the time, what would they say your specific role was?"
Candidate: "Probably that I was on the training and documentation side, not the technical lead. There was a project manager who ran the overall thing."
The gap between "I led the rollout" and "I was on the training and documentation side" is real and worth noting exactly, in those words, on the scorecard. It's not necessarily disqualifying on its own: there's a real project underneath the claim, and the second, more precise answer is consistent with itself. It's exaggeration, worth a lower score on the accuracy of self-reporting and worth asking the stated reference the specific question directly.
A decision guide: what the finding actually means
| What verification finds | What it likely means | What to do |
|---|---|---|
| Dates, title and scope all check out | The interview inconsistency was likely nerves, imprecise language, or your own misread | Proceed normally; don't hold a resolved flag against the candidate |
| Role and scope were meaningfully inflated but the underlying job and achievement were real | Exaggeration, common and worth a lower score on honesty and self-awareness, not automatic disqualification | Score it, discuss it in debrief, weigh it against the rest of the evidence |
| The job, degree or specific claimed result did not exist at all | Fabrication | Disqualify. This is rarely worth arguing yourself past, regardless of how strong the rest of the interview was |
| You can't verify either way (employer won't confirm anything, references are limited) | Genuinely unresolved | Weigh the interview inconsistency itself as a data point, and consider a more specific follow-up conversation before deciding |
If you discover it after an offer, or after they've started
This section describes common practice, not legal advice. Rescinding an offer or acting on a post-hire discovery can carry legal exposure that varies by jurisdiction, contract language, and the specifics of what was discovered. Confirm with your own HR or legal counsel before acting.
A material misrepresentation discovered through standard verification, most commonly a fabricated degree, job, or license required for the role, is commonly treated as grounds to rescind an offer or, if the person has started, to end employment, subject to your organization's own policies and applicable law. Document what was found and how, keep the communication factual rather than accusatory, and loop in HR or legal before you act rather than after.
Where claims get stretched most often
| Area | Common stretch | Question that tests it |
|---|---|---|
| Scope of ownership | "I led" a project they contributed to but didn't run | "Who did you report to on this, and who reported to you?" |
| Team or budget size | Rounding up headcount or budget managed | "What was the actual headcount, and how much of the budget did you personally control?" |
| Results and metrics | A number that was a team or company-wide figure, attributed to one person | "How was that measured, and who else would have seen that same number?" |
| Reason for leaving a role | A voluntary departure reframed to avoid mentioning a termination or performance issue | Verified separately through reference or employment checks, rarely worth pressing hard on in the room |
| Tools and technical skills | "Experience with X" that was really brief exposure, not working proficiency | A specific, applied follow-up: "walk me through the last time you used it, and what you built" |
A checklist for this situation
- You asked a specific, neutral follow-up rather than an accusation in the room.
- You wrote down the exact words, not a general impression, for later verification.
- You've distinguished exaggeration (a real thing described generously) from fabrication (nothing underneath the claim).
- You verified through at least one independent source before deciding, rather than deciding in the interview.
- If verification confirmed fabrication, you've looped in HR or legal before rescinding or acting further.
- If verification cleared the candidate, you're not holding a resolved flag against them in the decision.
Having an exact transcript matters more here than almost anywhere else in the process: a remembered impression of what a candidate said tends to soften or sharpen depending on how the rest of the interview went. Interview Signal keeps the transcript and the scorecard evidence tied together, so if you need to go back and check exactly what was claimed and how it was worded, you're reading the actual words rather than reconstructing them from memory days later.
Questions people ask
Should I confront a candidate directly if I suspect they're lying?
Ask a specific, neutral follow-up question rather than an accusation. "Walk me through the details of that" gets you more information and fewer defensive shutdowns than "I don't believe you," and it doesn't commit you to a conclusion you can't yet support.
What's the difference between exaggeration and a disqualifying lie?
Exaggeration usually inflates a real, verifiable thing: scope, ownership, or how central their role was. A disqualifying lie invents something that didn't happen at all, such as a job, a degree, or a specific claimed result. Both matter, but they call for different responses.
Can I rescind an offer after discovering a lie post-hire?
Often yes, particularly if it was a material misrepresentation discovered through standard reference or background checks, but the details depend on your jurisdiction, any offer letter language, and whether the person has already started. Confirm with your own HR or legal counsel before acting; this isn't legal advice.
Should I tell other interviewers on the panel if I catch a candidate in a lie?
Yes, promptly and with the specific detail, not a vague impression. "They said X in my round; ask them to repeat it and see if it holds" gives the next interviewer something concrete to check rather than just a bad feeling to work off.