what to say when you don't know an answer in an interview

by Wistkey · 23 july 2026 · 6 min read

your mind goes quiet, the interviewer is waiting and every second feels longer than it is. this moment does not need a perfect answer. it needs a calm response that shows you can listen, handle uncertainty and keep thinking without bluffing.

first, work out what kind of stuck you are

“i don't know” can mean several different things. perhaps the question is unclear. perhaps you know the subject but cannot recall one detail. perhaps it covers something you have never done. or perhaps you understand the problem but need time to build an answer.

do not treat all four situations as a complete failure. name the real gap before you respond. if you misunderstood the question, you need clarification. if you lack a fact, you need an honest boundary. if the problem is unfamiliar, you need to show a sensible route through it.

use pause, clarify, boundary, route

this four-part structure gives you somewhere to go when your first answer does not arrive:

• pause — take a breath and ask for a moment to think.
• clarify — check what the interviewer means if the question is broad or ambiguous.
• boundary — say briefly what you do not know or have not done.
• route — explain how you would reason, find the answer or apply relevant experience.

you will not need every step for every question. sometimes a pause is enough. sometimes the most credible answer is a clear boundary followed by your approach. the structure stops one missing detail from turning into a long, nervous guess.

1. make the pause look deliberate

silence feels more obvious to you than it does to the interviewer. instead of filling it with “um”, an apology or the first idea that appears, use one short sentence:

• “that's a useful question. could i take a moment to think?”
• “i'd like to choose the most relevant example. let me think for a moment.”
• “there are two parts to that. i'll start with the first.”

official UK careers guidance recommends asking for thinking time or clarification before tackling a difficult question. the important part is what follows: keep the pause short, settle your breathing and decide on the first sentence rather than trying to script the whole answer in your head.

2. clarify before you guess

if you are unsure what is being asked, say what you think you heard and invite a correction. try: “when you say stakeholder, do you mean an external client or someone in the wider team?” or “are you asking about the technical decision or how i communicated it?”

this is not avoiding the question. it is making sure you answer the right one. the National Careers Service advises asking an interviewer to repeat or explain a question you do not understand, while the University of Oxford careers service also recommends requesting clarification or a moment to think.

3. state the boundary without collapsing

when you genuinely do not know, be precise. “i haven't used that reporting tool” is stronger than “i'm not really technical”. “i don't remember the exact figure” is better than inventing a number. a narrow boundary protects your credibility and leaves room to show what you can do.

keep it to one sentence. repeated apologies make the gap sound larger and use time you could spend on a useful response. avoid pretending the question does not matter, criticising it or answering a different question without acknowledging the change.

4. show the route you would take

after the boundary, move towards action. connect the unfamiliar question to relevant knowledge, talk through the checks you would make or explain how you would learn what is missing. for example:

“i haven't worked with that platform directly. i have configured a similar workflow in another system, so i would begin by checking the required inputs, permissions and test environment. i would then use the product documentation and confirm the approach with the system owner before changing live data.”

the answer does not claim experience you do not have. it still demonstrates judgement, transfer and a safe way of working. for a problem-solving or case question, state your assumptions aloud and move through the problem in a clear order. guidance from the University of Cambridge careers service emphasises listening carefully, asking briefly for clarification and structuring open answers so they stay focused.

adapt the response to the kind of question

• you cannot recall a fact — say that you do not want to guess, give the part you can confirm and explain where you would check the detail.
• you have not used a tool or method — name the gap, connect it to the closest relevant experience and describe how you would get up to speed.
• you cannot find a behavioural example — ask for a moment, widen your search to study, volunteering or another responsibility, then use the star method to keep the example clear.
• the scenario is hypothetical — confirm the goal and constraints, state your assumptions, then explain the first few actions and why you chose them.

what not to say

avoid a flat “no idea” followed by silence. avoid guessing a fact that can be checked. avoid a long speech about why the question is unfair. and do not throw out every related fact you know in the hope that one of them lands.

also watch the nervous habits that can weaken an otherwise honest response: speeding up, smiling through every sentence, looking away for the whole answer or adding “sorry” three times. pause once, make comfortable eye contact and speak at your normal pace.

practise the recovery, not every possible question

you cannot prepare an answer for everything. you can prepare the way you respond when surprised. ask a friend to mix familiar questions with two you have not rehearsed. for each unexpected one, use pause, clarify, boundary and route.

record one practice round and watch only the first fifteen seconds after each hard question. did you rush? did your voice disappear? did you start with a clear sentence? choose one change and repeat the same question. this is how the recovery becomes familiar without turning it into a script.

finish cleanly and move on

once you have given the most useful answer you can, stop. you can close with “that is how i would approach it with the information i have” or ask, “would you like me to go further into any part of that process?” then listen to the next question instead of replaying the difficult one in your head.

one unknown answer does not require ten minutes of repair. handle the gap honestly, show your method and return to the conversation.