Every interview has one question you did not prepare for. What you say in the next ten seconds matters more than the fact that you did not know. Here is the three-step reply, the exact phrases, and how to recover the rest of the call.
Buy a few seconds with a calm holding line. Say what you do know and how you would find the rest. Then ask a clarifying question, or reason aloud towards an answer. Never bluff, never sit in silence, and never apologise more than once.
Interviewers ask questions they expect some candidates to miss. What they are watching is what you do next. A candidate who says "I have not used that, but here is how I would work it out" usually scores better than one who guesses confidently and gets it wrong. This guide gives the words for each step, by type of question.
Key takeaways
Interviewers ask questions they expect some people to miss. Not knowing the fact is not the test. The test is what you do next.
They want to see where your knowledge ends, and how you act when you reach that edge. Do you stay calm, say what you know and find a way forward? Or do you guess, go quiet, or swap in a story that does not fit?
That is why an honest "I have not used that, but here is how I would work it out" often scores better than a confident guess. They can give credit for a good process. They cannot give any for silence, and a bluff is found on the next question.
Silence feels twice as long on a video call. A holding line fills it and sounds like thinking, not panic. Pick one and make it a habit, so it comes out before your mind has caught up.
Say: "Let me think about that for a second."
Then: "That is a good question, I want to answer it properly." Or: "Can I take a moment on that one?" Any of the three is fine. Take a breath, then move to step 2.
Almost no question is a complete blank. You usually know a neighbouring topic, the general area, or where you would look. Say that part out loud. It shows the interviewer the edge of your knowledge, which is exactly what they want to see.
Say: "I have not worked with [X] directly. What I do know is [the nearest thing you know]. To do it properly I would [read the docs / check with the team / test it on a small example]."
Then: stop, and let them respond. They will often give you a hint or move on.
If the question was vague, ask what they mean. If it was clear, think out loud: state an assumption, take one step, check it. Interviewers can give partial credit for a good process. They cannot give any for silence.
Say: "Do you mean [interpretation A] or [interpretation B]?" Or: "Let me reason through it. If I assume [assumption], then [first step]. Does that direction make sense?"
Then: follow whatever they say next. If they correct you, thank them and continue from the correction.
Technical questions come in two kinds: a fact you either know or do not, and a problem you are meant to work through. Treat them differently.
Say: "I do not remember the exact [term / syntax / value], so I would rather not guess. The idea behind it, as I understand it, is [what you know]."
Then: if you can, name where it sits: "It is related to [nearby concept], which I have used in [project]."
Say: "I have not solved this exact one before. Let me start with the simplest version: [restate the problem in one line]. A first approach would be [approach], and the problem with it is [weakness]. So I would [next step]."
Then: keep narrating. Every step you say aloud is one they can score. If you get stuck, say where: "I am stuck on [specific part]. Is there a hint you can give me?"
A note on coding tests: this method works in a spoken technical round. On a locked-down platform such as HackerRank or CoderPad, you are on your own, and no tool changes that.
"Tell me about a time you..." questions feel impossible when you have no matching story. You almost always have a near match, and it is fine to say so.
Say: "I have not had exactly that situation. The closest was [situation], where I [what you did], and [result]. Would that be useful?"
Then: tell it in the STAR shape. The STAR builder helps you prepare five stories that cover most behavioral questions.
Say: "I have not faced that yet. If it came up, I would [first thing you would do], because [reason]. Then I would [second step]."
Then: stop. A clear plan for a situation you have not met is a complete answer. Interviewers ask freshers this way on purpose.
Definition questions are the ones people bluff most, and the bluff is easiest to catch, because the next question is "and when would you use it?"
Say: "I am not sure of the exact definition. If it is related to [nearby topic], then my guess is [one-line guess], but I would want to check that before using it."
Then: if the interviewer explains it, show you followed: "So it is like [your own comparison]. That makes sense." That moment often counts for more than a memorised definition would have.
If you are a fresher, the questions most likely to go this way are the basics of your own subject.
The full list of things that lose offers, before, during and after the call, is in common interview mistakes.
One missed question does not decide an interview. Letting it into the next five answers does. Here is how to close it.
Practice the recovery, not just the answers. The AI mock interview throws a random question at you with a timer, which is the closest thing to the real moment. The HR question vault covers the tricky ones that catch people out.
Learn the three steps above first; they work in any room. In a live video interview on Zoom, Meet or Teams, ClapAssist listens on your own computer and shows the shape of the answer, drawn from your resume and the job description: one sentence to say first, then the points. That gives you somewhere to start in the second where you would otherwise freeze. Only you see it, and it never joins the call. It does not help on HackerRank-style coding tests, and it does nothing in an in-person interview. Read how it works and try the ten free minutes on a mock call before a real one.
Outside pages that back the advice above, opened and checked on the date shown.
ClapAssist is a small desktop app for Mac and Windows. It listens to your video interview on your own computer and shows an answer written from your resume, one short sentence to say first and then the points. It never joins the call and stays out of screen shares and recordings.
Buy a few seconds with "let me think about that", say what you do know and how you would find the rest, then ask a clarifying question or reason aloud. Do not bluff and do not go silent.
Yes, as long as it is not the whole answer. Follow it with what you do know, how you would work it out, or a question back. Interviewers give credit for the process, not just the fact.
Restate it in one line, say the simplest approach and its weakness, then take one step at a time out loud. If you get stuck, say exactly where and ask for a hint.
Offer the closest similar situation and ask if it is useful, or say plainly that you have not faced it and describe what you would do first and why. Both are complete answers.
Only if you label it as a guess and say what you would check. A confident wrong answer is the most expensive mistake in the interview because it makes every earlier answer suspect.
Close it in one line, reset your posture, give the next answer in one clear sentence first, and if the topic returns later, add what you can. One missed question rarely decides the result.
In a live video call, ClapAssist shows the shape of an answer from your resume so you have a first sentence. It does not work on locked-down coding platforms or in person, and it does not replace knowing your own material.
ClapAssist puts that sentence in front of you in the live call. Ten free minutes, no card.