If you want to answer interview questions better than 99% of candidates, stop answering the question on the surface. Every interview question is testing something deeper, and there are only four types. Once you know what each one is really testing, you know exactly how to answer it.
I've sat on the other side of the table and interviewed more than 10,000 professionals. And here's what I've learned: the people who get hired and paid more are never the most impressive. They're the ones who understand what each question is really testing.
What are the four types of interview questions?
The four types of interview questions are behavioural, competency, situational and technical. Each one sounds different, and each one is testing something different underneath.
The four types at a glance
- Behavioural: "Tell me about a time you failed." It's testing your judgment and whether you're a safe bet.
- Competency: "Give me an example of when you led a team through change." It's a test with a hidden marking scheme.
- Situational: "What would you do if...?" It's testing how you think when you don't have the facts.
- Technical: "Walk me through how you'd do this." It's testing whether you can do the work, and what you do at the edge of what you know.
Let's take them one at a time.
How do you answer behavioural interview questions?
Lead with the decision you made and why you made it, not the drama of the situation. A behavioural question isn't asking what you did. It's asking how you think, and whether you're a safe bet to hire.
Most people think the interviewer wants a good story. So they go hunting for their most impressive moment: the biggest project, the highest stakes, the story where they're the hero.
But your past behaviour is the only real evidence an interviewer has that you won't blow up on them later. Think of it like buying a used car. The interviewer doesn't care how the car looks. They care whether it'll break down on them. A behavioural question is them checking the service history. Has it failed before, and did someone actually fix it?
From my client work
I once worked with a senior operations leader who was brilliant on paper but kept failing final interview rounds. When we role-played "Tell me about a time you failed," he gave me a polished story about a big transformation project that slipped. Suppliers, budget cuts, loads of detail. But every reason it failed was something that happened to him. None of it was a decision he'd made.
An interviewer doesn't hear resilience in that. They hear someone who won't own it when things go wrong. And that's a risk.
So we changed one thing. We put his decision back at the centre. Same project, same failure, but now it opened with the call he got wrong and what he does differently because of it. He got the offer in his next interview.
Here's the difference in practice. The question is "Tell me about a time you failed."
Surface-level answer
"We had a project that went over the deadline. It was really stressful, there were a lot of moving parts and the client wasn't happy. But we pulled it together as a team and eventually got it done."
Answering the real question
"I missed a deadline on a key client launch because I said yes to a timeline I already suspected was too tight. That was my call, and it was the wrong one. So I changed how I scope projects. I build in a buffer and flag risk early, before it becomes a surprise. I've not missed a launch date since."
The second answer owns the decision, shows what changed, and quietly tells the interviewer this person has already made this mistake, so they probably won't make it here.
I call it: Story versus signal
Most people bring a story. The ones who get hired prove the signal underneath it.
How do you answer competency-based interview questions?
Work out which competency they're testing, then make the evidence for it impossible to miss. A competency question isn't a conversation. It's a test with a marking scheme you never get to see.
It looks almost identical to a behavioural question: "Tell me about a time you influenced someone above your level." Same shape, same "tell me about a time" energy. That's the trap. Somewhere on the interviewer's desk, or in their head, is a list: did this person show ownership, handle conflict, influence without authority? Every answer gets a tick, or the box stays blank.
Here's what trips strong people up. You can have the skill and still score zero, because if the evidence isn't clear enough to tick, the box stays empty.
It's like claiming expenses. You can spend $200 of your own money on a client dinner, but if you lose the receipt, finance won't pay you back a penny. No receipt, no refund. No evidence, no credit.
So name the situation fast, then spend your time on the specific actions you took, then the result. Structure it so a tired interviewer taking notes can follow it without effort.
Surface-level answer
"I'm quite a collaborative person, so I tend to build good relationships across teams. There was a situation where we all worked together and got to a good outcome that everyone was happy with."
Answering the real question
"Our finance lead wanted to cut the project I was running. I didn't own the budget, so I couldn't overrule him. Instead, I pulled the numbers on what we'd lose if we stopped, walked him through it one to one before the meeting, and gave him a smaller version he could say yes to without losing face. He backed it in the meeting, and the project delivered $140K that year."
Every action in the second answer proves influence without authority. It hands the interviewer the evidence instead of making them dig for it. And on a competency question, buried evidence scores the same as no evidence at all.
I call it: Show and tell
Most people assume the interviewer can tell they're capable. The ones who get hired make it impossible to miss.
How do you answer situational interview questions?
Don't lead with the fix. Lead with what you'd need to find out first. A situational question isn't testing your answer. It's testing how you think when you don't have all the facts.
These are hypothetical: "What would you do if you took over a team that was missing its targets?" There's no story to reach for, so most people panic and rush to sound decisive. "I'd sit them down, set clear expectations and turn it around." Fast, confident and wrong.
Imagine two doctors. You describe your symptoms. The first barely looks up: "Take these, you'll be fine." The second asks how long it's been going on, what makes it worse, and what you've already tried, and only then tells you what she thinks is wrong. Which one do you trust? A doctor who hands out pills before asking a single question is guessing. And a doctor who guesses is dangerous.
Surface-level answer
"I'd set clear goals, have some honest conversations and motivate them to get back on track."
Answering the real question
"Before I changed anything, I'd want to know why they were missing targets, because the fix depends entirely on the cause. Is it unclear priorities? A weak hire? An overloaded team? Those are three completely different problems. So my first move isn't a plan. It's two weeks of finding out what's actually going on, then acting on the real cause, not the symptom."
That answer refuses to guess, and it tells the interviewer this person won't march in and break something on day one.
I call it: Questions before answers
Most people rush to look decisive. The ones who get hired lead with the questions, because that's what safe hands do. The confident wrong answer is the most dangerous answer in the room.
Free guide
Want all 20 of the most common interview questions sorted into these four types, with what each one is really testing? Grab The Question Behind The Question here.
How do you answer technical interview questions?
Show the why behind what you know, and be honest about what you don't, then explain how you'd close the gap. A technical question isn't a memory test. It checks whether you understand your craft well enough to apply it, and what you do when you hit the edge of what you know.
The most dangerous thing you can do is bluff. I've sat on the hiring side of thousands of interviews and seen every kind of bluffer: the waffler, the big-word merchant, the one who answers a slightly different question and hopes nobody notices. Anyone who actually knows the subject can smell a bluff in seconds. And once they catch you, they stop trusting everything else you've said.
Here's the part that surprises people. Admitting what you don't know makes them trust you more, not less.
Think about a waiter. You ask what's good tonight, and instead of "Everything's great," he says, "Maybe skip the salmon tonight, but the sea bass is excellent." You trust him more, and you take his other recommendations too. Psychologists call it the pratfall effect: when someone who clearly knows their stuff admits a flaw, we trust them more.
Bluffing
"Yeah, that's something I've definitely leveraged my experience on, and I drive that forward with best practices."
Answering the real question
"I've not done that exact thing before. Here's the part I'm confident in. And for the bit I haven't done, here's how I'd get up to speed: I'd pull the internal data, sit down with whoever owns it, and have a working answer within a week."
That tells them you know your craft, you're honest about your limits, and you know how to close the gap. Someone safe to hand a problem to.
I call it: Knowing your edges
The strongest technical people aren't the ones who know everything. They're the ones who know where their knowledge stops, and how to close the gap.
What are the most common mistakes when answering interview questions?
Avoid these
- Telling a story where you're the victim. Put your decision at the centre, and what you changed because of it.
- Answering a competency question like a chat. Name the situation fast, then spend your time on your actions and the result.
- Describing your personality instead of proving it. "I'm collaborative" ticks nothing. Show what you did.
- Rushing to a fix on a situational question. Say what you'd want to find out before you decide.
- Bluffing on a technical question. Own the gap, then show how you'd close it.
The bottom line
Every interview question has a surface question and a real question underneath it. Behavioural questions check your service history, competency questions need a receipt, situational questions test whether you diagnose before you prescribe, and technical questions test whether you know your edges. Answer the real question, and you'll interview better than 99% of the people you're up against.
What's your next step?
If you want to see how your CV holds up before your next interview, try the free Six Figure CV tool. Upload your CV and get an instant score with specific fixes.
And if you want to work on this with me directly, here's where to start.