You can spot most skill gaps in an interview by asking candidates to walk through a specific past example of the skill in action, then probing for details a bluffer couldn't invent. Compare what they describe against how the work is actually done in your business. Do this consistently across candidates and you rarely need a separate skills test to know who can genuinely do the job.

Why You Don't Always Need a Formal Test

Skills tests have their place, especially for highly technical or safety-critical roles. But for most small and mid-sized business hires, a well-run conversation can reveal just as much, faster and with less friction for the candidate. Tests also add time to your process, and strong candidates with other offers on the table sometimes drop out rather than complete one.

The goal of an interview is not to make someone prove a skill on the spot. It is to get them to describe, in enough detail, a time they used that skill for real. People who genuinely have a skill can go deep on specifics. People who are exaggerating or guessing tend to stay vague, generic, or start describing what a team did rather than what they personally did.

The Core Method: Ask for the Story, Not the Summary

Most interviewers ask questions that invite a summary answer, such as "are you good at managing conflict?" or "how would you rate your Excel skills?" These questions are easy to answer well whether or not the skill actually exists. The fix is to always ask for one specific, real instance instead of an opinion or a rating.

Instead of: "Are you comfortable handling difficult customers?"Ask: "Tell me about the last time a customer was genuinely upset with you. What did they say, what did you say back, and how did it end?"

Notice the second version forces a real memory. Someone without the experience will hesitate, generalise, or reach for a textbook answer. Someone with it will usually answer fast, with names, numbers, or a specific sequence of events, because they are recalling rather than inventing.

Follow-Up Questions That Separate Real Experience From Rehearsed Answers

The first answer to a story-based question is rarely the most revealing part. The follow-up questions are where skill gaps show up. Good follow-ups ask for detail that only someone who actually did the work would know or remember easily.

  • "What was the hardest part of that, specifically?"
  • "What did you try first, and why didn't that work?"
  • "Who else was involved, and what exactly was your part versus theirs?"
  • "What would you do differently if you did it again tomorrow?"
  • "What tool or method did you use, and why that one over the alternatives?"

Candidates with real depth in a skill answer these naturally, often adding detail you didn't ask for. Candidates who are stretching the truth or describing a team effort as their own tend to go quiet, repeat themselves, or pivot back to generic language like "we worked together" or "it was a group decision."

Skill-Specific Questions You Can Ask

Different skill types need slightly different probing angles. Here is a practical set you can adapt.

Technical or hands-on skills

"Walk me through the last time you [used the specific tool/process]. What was the actual output, and what would have gone wrong if you'd made a mistake at step two?"

People with genuine technical skill can explain the sequence of a task and the consequences of getting a step wrong. Someone without it usually knows the terminology but not the mechanics.

Communication and collaboration

"Tell me about a time you had to explain something complicated to someone who didn't have your background. How did you know they understood?"

Strong communicators describe checking for understanding, adjusting their language, and reading the other person's reaction. Weaker ones usually just describe what they said, not whether it landed.

Problem-solving and judgement

"Describe a decision you made with incomplete information. What did you decide, and how did you know it was the right call afterwards?"

This question is hard to fake because it needs a real trade-off, a real outcome, and honest reflection on whether the judgement was actually good.

Leadership and people management

"Tell me about the last time you had to give someone feedback they didn't want to hear. What did you say, and what happened next?"

This surfaces both the skill and the person's comfort with the harder parts of managing others, which is often the real gap in first-time managers.

Reading the Signals Beyond the Words

What candidates say matters, but how they say it also tells you something. Pace, hesitation, and the order in which details come out are all useful signals, though none of them are proof on their own.

  • Genuine experience is usually recalled quickly, with small, specific, sometimes irrelevant details (a date, a person's name, an odd detail about the day).
  • Fabricated or borrowed experience often comes out in a neat, well-structured narrative that sounds slightly rehearsed, with round numbers and no messy details.
  • Watch for answers that describe what "the team" or "we" did without ever clarifying the candidate's individual contribution, and ask directly: "what was your part specifically?"
  • Confidence is not the same as competence. Some highly skilled people undersell themselves, and some unskilled people interview very well. Weight the content of the answer over the delivery.

None of these signals should be used in isolation to reject or advance a candidate. They are prompts to dig one level deeper with a follow-up question, not a verdict.

Work Samples and Light-Touch Exercises as a Middle Ground

If a conversation alone isn't giving you enough confidence, you don't have to jump straight to a formal test. A lighter middle option is to ask the candidate to bring or produce a small work sample relevant to the role, such as a short writing sample, a spreadsheet they built, or a walkthrough of a project in their portfolio.

You can also ask them to talk you through a real artefact from their past work in real time, such as sharing their screen to show you a report they built or a process they documented. This is not a test in the formal sense, it is simply asking to see evidence of the story they already told you, which makes it very hard to fake.

Building a Simple Scorecard So You Compare Fairly

Whatever questions you ask, write down what you're listening for before the interview, not after. This keeps you consistent across candidates and reduces the risk of unconsciously favouring whoever you liked personally.

A basic scorecard for each must-have skill can be as simple as:

  • Did they give a specific, real example (not a hypothetical or generic answer)?
  • Could they answer the follow-up questions with genuine detail?
  • Was their individual contribution to the outcome clear?
  • Did their account match the level of the role you're hiring for?

Score each skill area independently rather than forming one overall impression, since a candidate can be strong in one area and weak in another. Structured, consistent interview scoring is one of the most well-documented ways to improve hiring accuracy and reduce bias, according to guidance from SHRM. If you're running interviews across multiple roles or a growing hiring pipeline, a tool like Hyrewell can help by screening applicants against your must-have skills automatically, producing a ranked shortlist with evidence, and letting shortlisted candidates self-book interview slots, so your own conversation time goes to people worth probing deeply rather than everyone who applied.

Common Mistakes to Avoid

  • Asking only hypothetical questions like "how would you handle X?" instead of "tell me about a time you actually handled X."
  • Accepting a team achievement as proof of an individual skill without asking what the candidate specifically did.
  • Letting a confident delivery substitute for checking the actual content of the answer.
  • Changing your questions or standards between candidates, which makes comparisons unfair and unreliable.
  • Treating a single vague answer as a hard fail instead of probing further with a follow-up.
  • Not writing down your assessment straight after the interview, which lets memory and bias creep in later.

When a Real Test Is Still Worth It

Questioning techniques go a long way, but they are not a full substitute for a skills test in every situation. Roles where a mistake is costly, safety-critical, or highly technical (such as certain engineering, medical, or regulated financial roles) usually still benefit from some form of practical assessment alongside the interview. The International Labour Organization has highlighted skills mismatches as a persistent global challenge across industries, which is part of why structured evaluation methods, whether interview-based or test-based, matter so much for hiring accuracy.

Employment law, disability accommodation requirements, and rules around what can and cannot be asked in an interview vary by country and region. Always check your local labour regulations and official government sources before finalising your interview questions or assessment methods, particularly around requests for work samples or exercises that could be seen as unpaid work.

Used well, story-based questioning gives you a fast, low-friction way to see real skill in action. It respects the candidate's time, avoids the drop-off risk of a formal test, and often reveals more about how someone actually works than a standardised assessment ever could.