Every week we talk to professionals who have failed an interview they "should have passed". They have the profile, the experience, the track record. And yet they leave the room (or close the video call) with that uncomfortable feeling that something didn't add up.
The problem is rarely a lack of technical preparation. It's almost always the same one: nobody taught them to build their story before trying to tell it.
"Practising answers without a clear narrative is like memorising isolated phrases in a language you don't speak."
In this article we break down the real reasons professionals fail interviews, and the specific mistakes that come up again and again, whatever the industry or the seniority of the role.
The root problem: a broken narrative
Something separates the candidates who pass interviews from the ones who don't. It isn't intelligence, or experience, or even confidence. It's having a coherent narrative: a clear story about who you are, what you've done, and why it makes sense for you to be in that chair.
When that narrative breaks down — inconsistencies, gaps in the timeline, answers that don't connect to each other — the interviewer starts to doubt. And doubt, in an interview, is the silent killer.
Beyond the technical questions, interviewers are trying to answer one very simple question: Does this person know who they are and where they're going? If they can't answer it clearly, you don't move on.
The narrative breaks when a candidate answers questions in isolation, as if each answer stood alone, without connecting their past to their present and their present to the role they're going for. The interviewer ends up with a collection of anecdotes and no thread running through them.
The 5 mistakes we see most (and nobody tells you about)
Almost everyone's first instinct when they land an interview is to Google "common interview questions" and prepare an answer for each one. The problem is that you're building the roof before the foundations.
Without a clear narrative about your career, every answer sounds improvised. It may be technically correct, but it doesn't connect to the rest. And the interviewer notices.
"What are your strengths?" → prepare 3 strengths with examples. "Why do you want this job?" → prepare an answer about the company. With nothing linking them.
First you build your story: who you are, what thread runs through your career, where you're heading. Then every answer grows out of it. They're coherent because they start from the same place.
When someone asks "tell me about your last project", the average candidate starts describing their day-to-day. "I was responsible for X, I coordinated with Y, I managed Z." All description. Nothing memorable.
Interviewers don't want to know what was in your job description. They want to know what happened because of you. What changed. What improved. By how much.
If your answers have no numbers, no before/after, no concrete result, you're describing your job, not your impact. Impact is the only thing anyone remembers.
"I was responsible for content strategy and coordinated with the design and paid media teams."
"I redesigned the content strategy, which took us from 8,000 to 35,000 monthly organic visits in 9 months and cut cost per lead by 40%."
This question comes up in almost 100% of interviews. And yet it's the one candidates get wrong most often. Either they say something negative about their current employer — the worst possible move — or they give an answer so generic it sounds rehearsed and hollow.
- Never speak badly about your current company, manager or team. Even if your reasons are legitimate, the interviewer will wonder what you'll say about them one day.
- Avoid "I'm looking for new challenges" unless you can be specific. It's the most repeated answer and the one that says least.
- The strong answer connects your reason for leaving with what draws you to the new opportunity, specifically and honestly.
I've learned a great deal at [current company] and I value what I built there, particularly [something specific]. But at this point in my career I want [something specific this company offers], and I believe [company you're applying to] is where I can contribute most and keep growing in that direction.
The interview doesn't end when the interviewer stops asking questions. There's almost always a moment where they say: "Do you have any questions for us?" And far more rides on it than it seems.
A candidate with no questions, or who asks things they could have looked up on the website, signals a lack of interest or of strategic thinking. A candidate who asks good questions shows they've thought seriously about the role, the team and the fit.
"What did the best performer in this role over the last two years do differently?" · "What's the biggest obstacle the team is facing right now?" · "What would you expect to see from me in the first 90 days?"
Rehearsing in your head isn't practice. Neither is reading answers out loud. And answering questions from an AI that validates everything you say is probably as close as you can get to not practising at all.
The problem isn't AI. The problem is the absence of real pressure: the awkward silence, the sceptical look, the unexpected follow-up. All of that only exists with a real person on the other side.
"The first time you feel real pressure cannot be on the day of the interview."
Candidates who practise with real people — coaches, industry professionals or well-briefed peers — arrive at the interview having already worked through the nerves. For them, the day itself is almost déjà vu.
Recognise yourself in any of these?
We work with mid and senior professionals to build their narrative, fix these mistakes and practise under real pressure before the interview.
See how it works →The conclusion few people want to hear
The mistakes we've described aren't about a lack of experience or a lack of talent. They're mistakes of form, of structure and of preparation. And that is, in fact, good news: every one of them can be fixed.
The catch is that fixing them alone is very hard. When you've spent years telling your experience one particular way, it's almost impossible to see from the outside what's failing. You need someone to see it for you.
What sets apart the candidates who pass interviews isn't that they're smarter or more capable. It's that they know how to build their story, how to quantify their impact, and how to connect all of it to what the interviewer needs to hear.
And that, unlike talent, can be learned.
In short: the 5 mistakes to avoid
- Preparing answers before you have a solid narrative about your career
- Describing responsibilities instead of quantifying achievements with real impact
- Answering "why are you leaving?" negatively or generically
- Forgetting that the questions you ask say as much as the ones you answer
- Practising alone or with AI instead of under real human pressure