Common Interview Mistakes: 9 Fixes You Can Rehearse
Nine common interview mistakes, each with what it sounds like, why it happens and the exact replacement behaviour to practise before your next call.
Most common interview mistakes are habits you can hear in a recording, not flaws in your character. Each one has a symptom, a cause under pressure and a replacement behaviour you can rehearse. Below are nine of them, with the wording to try and a short drill for each. You do not need all nine. Pick two or three, practise them aloud, and the fix will show up in the real conversation.
Why "be more confident" is useless advice
Confidence is an outcome, not an instruction. When someone tells you to relax or be yourself, they are describing how you should feel, and feelings do not respond to orders. Behaviour does. You can decide to pause before answering, or to restate a question, or to stop after the result of a story. Those are things you can hear yourself do and change.
So treat every mistake in this article as a behaviour with three parts:
- Symptom: what it sounds like when you do it, so you can catch it.
- Cause: why it happens when you are under pressure, so you stop blaming yourself.
- Replacement: the exact behaviour to practise, so you have something to do instead.
One warning before you start. Changing everything at once changes nothing. Choose two mistakes that sound most like you, work on those, and leave the rest for the next interview.
Common interview mistakes 1 to 3: the question, the ramble and the vague claim
Mistake 1: Answering the question you prepared
What it sounds like: a long answer that starts before the question has finished landing. You hear yourself describing the project you rehearsed, while the interviewer asked about something narrower.
Why it happens: under pressure, your brain reaches for the nearest prepared material. It is a memory shortcut, not laziness.
The fix: restate the question in your own words before answering. "So you're asking how I handled the deadline slip, not the project overall?" That buys you two seconds to think and confirms you heard correctly. Interviewers usually appreciate it, because it shows you are listening rather than performing.
The drill: have someone read questions aloud from a list, and practise restating each one in a single sentence before you respond. Do ten in a row. The habit transfers.
Mistake 2: The rambling answer with no end in sight
What it sounds like: the interviewer interrupts, or you hear yourself saying "and another thing". The answer has no visible finish line, so neither of you knows when it is over.
Why it happens: you are trying to include every relevant detail, because leaving one out feels risky. The result is that the important detail gets buried.
The fix: use a spoken structure with a finish line. Situation, action, result, then one sentence on what you learned. The learned sentence is your brake: once you say it, stop.
Here is a weak version, then a stronger one with the same content, trimmed from about 90 seconds to about 45.
Weak: So we had this launch, and there were a lot of moving parts, and I was coordinating with several teams, and honestly there was a lot going on, and at one point the timeline slipped, and I had to figure out what to do, and I talked to a few people, and we reworked the plan, and eventually we got it out, and it was fine in the end, and I think I learned a lot about communication, and also about planning, and there were other things too.
Stronger: Our launch timeline slipped by two weeks when a dependency arrived late. I mapped which tasks could run in parallel, ran a short call with the three teams affected, and proposed a revised order that protected the customer-facing date. We shipped one week late instead of two. What I learned is to build a buffer around any dependency I don't control.
The stronger version is easier to follow because it names the situation, your actions, the result and the lesson, in that order. The interviewer can now ask a follow-up about any part they care about.
Mistake 3: Vague claims with no example behind them
What it sounds like: "I'm a strong communicator" or "I work well under pressure", with nothing after it. The interviewer nods and writes nothing down, because there is nothing specific to write.
Why it happens: self-descriptions feel safe. A claim cannot be wrong, while an example can be questioned.
The fix: claim plus proof. Every time you describe yourself, follow it with one specific situation. One claim, one example, then stop.
Here is a worked example. "I'm a good team player" becomes:
I'm a good team player. On a project where two teams disagreed about who owned the handover, I wrote a one-page summary of both positions and ran a short meeting to agree the boundary. We settled it in twenty minutes and the handover stopped slipping.
Two sentences: the claim, then a real task, your part and the outcome. That is enough. For more on shaping a single story well, see Greatest Achievement Interview Answer: One Real Story.
Common interview mistakes 4 to 6: credit, criticism and closing questions
Mistake 4: Talking about "we" when they asked about you
What it sounds like: an answer where your own contribution disappears into the team's. Every sentence starts with "we", and the interviewer cannot tell what you did.
Why it happens: most real work is collaborative, and claiming too much credit feels dishonest. So you overcorrect.
The fix: name the team briefly, then say plainly what you did and decided. "The team was five people. I owned the migration plan and made the call on the cutover date." That is accurate, not boastful.
The honesty angle matters here. Credit the team where it is due, and still state your part truthfully. Interviewers are usually trying to place you in a role, and they cannot do that if your contribution is invisible. If ownership is the theme of the interview, Ownership Interview Questions: How to Show You Take Responsibility goes further.
Mistake 5: Bad-mouthing a previous employer
What it sounds like: the answer to "why are you leaving" turns into a complaint about a manager, a process or a colleague. Even when every word is true, it makes the interviewer wonder how you will talk about them one day.
Why it happens: the honest reason often is frustrating, and frustration is easier to say than a neutral summary.
The fix: one neutral sentence on why you are leaving, one forward-looking sentence on what you want next. Here are two versions of the same reason, side by side.
Blaming: I left because my manager was disorganised and never gave clear priorities, and the team was constantly firefighting because of it.
Neutral: I'm looking for a role where priorities are set further ahead, so I can plan work properly. This team's quarterly planning is exactly the kind of structure I do well in.
The neutral version says the same thing about what you want without turning the previous manager into the subject. It also points forward, which is where the interviewer's attention should be.
Mistake 6: Not asking questions, or asking ones you could have looked up
What it sounds like: "No, I think you've covered everything" at the end. The interviewer closes the notebook, and the conversation ends flat.
Why it happens: you are tired, the questions you prepared were answered along the way, and asking something now feels like a test you might fail.
The fix: prepare three questions about the work itself, the team or how success is measured, and pick two. Good ones include: what does the first three months look like, how is success measured in this role, and what is the team's biggest constraint right now. Each one invites a real answer rather than a yes or no.
Avoid questions whose answer is on the company website, such as what the company does or how big it is. The interviewer usually hears those as preparation you did not do.
Common interview mistakes 7 to 9: nerves, gaps and conversation
Mistake 7: Letting nerves show up as speed, filler or apology
What it sounds like: talking fast, repeated "um" and "like", or opening with "sorry, I'm a bit nervous". The content may be fine, but the delivery signals that you are not comfortable.
Why it happens: nerves speed up your breathing, and speech follows. The apology is an attempt to explain the nerves before anyone judges them.
The fix: a deliberate pause before answering. One breath, then start. Replace the apology with a plain statement: "Thanks for having me, I've been looking forward to this." It says the same friendly thing without putting yourself down.
The drill: record a two-minute answer on your phone and count the fillers. Then repeat the same answer with pauses allowed, and count again. Most people find the pause version has fewer fillers and sounds more confident, because the pause gives you time to choose the next word. If you use notes, Sound Natural With Talking Points Interview Guide shows how to keep them from turning into a script.
Mistake 8: Bluffing when you don't know something
What it sounds like: an answer that keeps going and gets less accurate as it goes. You can hear yourself hoping the interviewer will move on.
Why it happens: "I don't know" feels like a failure, so you fill the gap. But interviewers usually spot a bluff, and it costs more trust than the gap would have.
The fix: an honest three-part response. What you do know, what you would check, and how you would find out.
I haven't used that tool, but I've worked with a similar one, so the concepts should carry over. I'd want to check how it handles permissions before relying on it. I'd read the setup documentation, then build a small test case and confirm with someone on the team who uses it daily.
That answer is short, honest and shows how you work. It usually lands better than a confident guess. For more on structuring answers like this, see Communication Interview Questions: Honest, Clear Answers.
Mistake 9: Treating the interview as an interrogation
What it sounds like: one-word answers, no follow-up questions, no back-and-forth. The interviewer carries the whole conversation, and it feels like a form being filled in.
Why it happens: you are focused on giving correct answers, and a question feels like a test rather than an opening.
The fix: treat each answer as an invitation. End some answers with a brief check such as "does that cover what you were after?" or "happy to go deeper on the planning side." It hands the conversation back and gives the interviewer an easy way to steer.
You do not need to do this after every answer. Two or three times in an interview is enough to change the rhythm from interview-as-exam to interview-as-conversation.
A practice routine you can run this week
Pick two mistakes from this list that sound most like you. Rehearse them aloud twice, not in your head, because the habit lives in your speech and not in your notes. Review what you heard, then repeat before the next interview. Two behaviours, rehearsed out loud, will do more for you than nine read once.
Before you walk in
The biggest interview mistakes are habits, and habits change through rehearsal, not resolve. Choose your two, say the replacement behaviour aloud until it feels ordinary, and let the rest wait. If you want a structured way to prepare honestly, the AI Interview assistant guide to preparing honestly for interviews is a sensible next read.
Frequently asked questions
How many interview mistakes is it normal to make in one interview?
Most people make a few in any given interview, and interviewers rarely keep score. What matters is whether the mistakes are small slips or patterns that stop them learning what they need. If you catch yourself rambling once, correct it and move on. Repeating the same behaviour across several answers is the thing worth fixing before the next call.
Should I point out my own mistake if I notice it mid-answer?
Usually no, unless the mistake changes the meaning of what you said. A brief correction such as "let me put that more clearly" is fine and shows self-awareness. Announcing that you are rambling tends to draw attention to it. Finish the answer, then give a tighter version in one sentence if it matters.
Is it bad to ask the interviewer to repeat or clarify a question?
No. Asking once is normal and often sensible, especially if the question was long or had two parts. Say which part you want clarified, for example "do you mean the planning side or the delivery side?" That is more useful than asking for the whole question again. Repeated requests are what start to cost you.
How do I stop apologising at the start of an interview?
Replace the apology with a greeting you have practised. "Thanks for having me, I've been looking forward to this" does the same social work without putting yourself down. Say it aloud a few times before the call so it is the first thing your mouth reaches for, rather than "sorry, I'm nervous".
Do these common interview mistakes matter as much in a video interview as in person?
Yes, and a few show up more clearly. Fillers and speed are just as audible on a call, and rambling can feel longer when there are no visual cues. Pauses help twice over: they slow you down and give the interviewer a natural moment to respond. Test your setup beforehand so the technology is not one more thing to manage.