Some candidates interview brilliantly and perform poorly, because interviews reward confident storytelling more than they reward actual skill. The good news is that this gap between claim and capability leaves traceable signs, in resumes, in interview answers, and in how someone responds when you ask them to get specific.

Why Overpromising Happens More Often Than You Think

Most candidates are not lying outright. They are doing what interviews train people to do: present their best possible version of events, smooth over gaps, and claim credit for team wins. Interviews are, by design, a performance, and confident, articulate people tend to perform better than quietly competent ones.

There is also a well-documented halo effect at play. If a candidate is likeable, articulate, or shares your sense of humour, interviewers tend to unconsciously rate their competence higher too, even when the evidence for that competence is thin. Add time pressure on a hiring manager who needs the role filled, and it becomes easy to accept a polished answer instead of digging for proof.

None of this means candidates are trying to deceive you. It means your interview process needs to separate the story from the substance, every single time, for every candidate, not just the ones who seem too good to be true.

Early Warning Signs on the Resume or Application

Before you even get to interview, a resume can hint at an overpromising pattern. None of these signs alone is disqualifying, but two or three together are worth probing hard.

  • Heavy use of impact verbs like "spearheaded," "transformed," or "drove" with no numbers attached to what actually changed
  • Job titles that sound senior relative to the company size or the person's apparent tenure
  • Short stints (under a year) described with outsized achievements
  • Claims of managing a team, budget, or project with no mention of size, scope, or timeline
  • Bullet points that closely mirror the job posting's language, almost word for word

When you see this pattern, do not screen the candidate out automatically. Flag the specific claims you want to test in the interview, and build your questions around them. This is exactly the kind of evidence-based shortlisting that tools like Hyrewell are built for: screening applicants against your must-haves and surfacing the evidence behind each claim, so you walk into the interview already knowing which lines need a follow-up question.

Interview Language That Should Make You Pause

Once you are in the room (or on the call), listen for language patterns rather than just content. These are often more revealing than what the candidate actually says.

  • Passive voice on wins, active voice on blame. "The launch was delivered on time" but "the delay happened because marketing was late" is a common tell of someone avoiding ownership.
  • "We" everywhere, "I" nowhere. Team language is normal, but if a candidate cannot isolate their own specific contribution anywhere in a 20-minute answer, that is worth noting.
  • Jargon without mechanism. Phrases like "optimised the funnel" or "streamlined the process" that never get explained in plain, step-by-step terms.
  • Topic drift under follow-up. Ask a direct clarifying question and watch whether the candidate answers it or pivots to a different, more comfortable story.
  • No mention of mistakes or failure. Genuinely experienced people have failure stories. A candidate who insists everything they have touched has succeeded is either very lucky or editing heavily.

Ask for Evidence, Not Adjectives: The STAR+ Technique

Most hiring teams already know the STAR method (Situation, Task, Action, Result). The problem is that most interviewers stop there, accepting the first answer at face value. The fix is simple: add a "+" round of specific, numeric follow-ups to every big claim.

"You mentioned you grew that channel significantly. Can you tell me exactly what the metric was before and after, over what time period, and what percentage of that result was your work versus the team's?"
"Walk me through the actual tool or process you used, step by step, as if you were training me to do it."
"What would you do differently if you ran that project again today?"

Candidates with real experience answer these follow-ups quickly and get more specific, not less. Candidates who are stretching the truth tend to get vaguer, repeat the same phrase, or restate the original claim without adding detail. The gap between the first answer and the follow-up answer is often the clearest signal you will get in the entire interview.

Use Work Samples and Practical Tests to See Real Skill

For roles where output is observable, a short, realistic work sample beats an hour of conversation. This does not need to be elaborate. A 30 to 90 minute paid exercise that mirrors an actual task from the role (a short writing brief, a sample dataset to analyse, a mock sales call, a small coding challenge) tells you far more than a claim on a resume ever could.

Keep the exercise fair and respectful of the candidate's time:

  • Use a real but low-stakes task, not a piece of actual client work
  • Time-box it clearly and pay for the time where appropriate
  • Give every finalist the same exercise and the same instructions
  • Score it against a simple rubric you agreed on before seeing any submissions

This single step filters out most of the gap between claimed and actual skill, because it is very hard to talk your way through a task that has a concrete, checkable output.

What Good Reference Checks Actually Reveal

Reference checks are often treated as a formality, a quick call to confirm dates and job titles. Used properly, they are one of your best tools against overpromising, because you can ask the referee the exact same specific question you asked the candidate.

"They told me they led the migration to the new platform and it cut processing time by roughly a third. From where you sat, how accurate does that sound, and what was their specific role in it?"
"What would you trust them to own completely, without checking in, on day one with you again?"
"Was there ever a point where their work needed to be redone or heavily corrected?"

Try to speak to at least one former manager, not only candidate-selected cheerleaders, and ask for a second, independent reference where your local hiring practices and the candidate's consent allow it. Note that rules on contacting employers, data protection, and what you can ask a referee vary by country and region, so check your local labour regulations and official guidance before formalising your reference process.

Build a Simple Scorecard to Compare Claimed vs Evidenced Competence

A structured scorecard turns gut feel into a comparable record across candidates. For each core competency on the job description, score two things separately: how strongly the candidate claimed the skill, and how strongly they evidenced it through follow-up answers, a work sample, or references.

A large body of hiring research, summarised by organisations such as SHRM and discussed in analyses published by Harvard Business Review, has consistently found that structured interviews with consistent, evidence-based questions predict job performance far better than unstructured, conversational interviews. The scorecard is what makes an interview structured in practice, not just in theory.

When the claimed score and the evidenced score are close, you have a strong, honest signal either way. When there is a big gap, with high claimed confidence but thin evidence, that is your overpromising flag, and it deserves one more verification step before you move to an offer.

Common Mistakes to Avoid

Even well-intentioned hiring teams fall into a few predictable traps when trying to assess credibility.

  • Hiring on charisma alone. A likeable candidate who cannot answer a specific follow-up question is still a risk, no matter how good the conversation felt.
  • Skipping reference checks under time pressure. This is exactly when the risk of a bad hire, which research from organisations like Gallup links to real costs in productivity and team morale, is highest.
  • Accepting vague metrics without a follow-up. "Significantly improved" is not a result, it is a placeholder for one.
  • Only asking open questions. Open questions invite rehearsed stories. Follow-ups invite proof.
  • Letting one strong answer carry the whole interview. A single great story should not outweigh three vague ones on the scorecard.
  • Inconsistent questioning across interviewers. If different people ask different questions, you cannot compare claimed versus evidenced competence fairly.

Putting It Together in a Repeatable Process

The goal is not to turn every interview into an interrogation. It is to build a process that quietly separates confident talkers from proven performers, applied consistently to every candidate, so nobody gets an unfair pass or an unfair grilling. Start with resume flags, move into STAR+ follow-ups, add a short work sample for skill-based roles, and close with a specific, example-matched reference check. Score claimed and evidenced competence separately, and only make an offer once the gap between the two is small.