Sooner or later an interviewer asks something you cannot answer: a technical term you have never met, a figure you do not have, or a request for an example you simply do not possess. The instinct is to fill the silence with something that sounds like an answer. That is usually the worst option.
The short version: pause, check you have understood the question, say honestly what you do and do not know, then show how you would find or reason towards the answer. The rest of this guide works through six common situations, with illustrative wordings for each.
Why bluffing costs more than admitting a gap
Careers advisers are consistent on this point. gradireland’s interview guidance puts it bluntly: “if you don’t know the answer, do not waffle.” Northeastern University’s careers service gives the same advice for technical interviews: if you are unsure, say so honestly rather than bluffing.
There are practical reasons. Interviewers often ask follow-up questions, so a bluff tends to unravel within a minute. Many interviewers are specialists in the area they are probing. And a confident wrong answer raises a bigger question than a gap does: will this person tell us when they do not know something on the job?
In many interviews, the answer is not the only thing being assessed. Virginia Tech’s career services notes that in technical interviews “the interviewer is less concerned with your conclusion as they are with your thought process.” Northeastern lists problem-solving, meaning how you approach an unfamiliar problem, and communication alongside technical knowledge. A gap handled well gives you a chance to show exactly those things.
The basic move: pause, check, admit, reason
- Pause. gradireland notes that you do not have to give an immediate response to a difficult question, and suggests a line such as: “That’s an interesting question; can I have a minute to think it through please?”
- Check the question. Sometimes the problem is the wording, not your knowledge. Restating it (“Do you mean X or Y?”) either brings the answer back or confirms the gap.
- Admit the gap specifically. “I haven’t used that tool” is better than “I’m not sure about that”. It tells the interviewer where your knowledge stops.
- Bridge or reason. Offer the nearest thing you do know, explain how you would work it out, or describe how you would find the answer on the job.
This should take about thirty seconds to a minute. A long apology wastes time that you could spend showing your reasoning.
Six situations and how to handle each
1. A technical fact or term you do not know
Situation: an interviewer for a data role asks about a database feature you have never used.
Say what you do know nearby, without pretending it is the same thing. Then explain how you would learn it.
Illustrative answer: “I haven’t worked with that feature directly. The closest I’ve used is [related feature], on a reporting project last year. If I needed it here, I’d start with the official documentation and test it on a small copy of the data before using it on anything live. Could you tell me how the team uses it?”
The closing question is optional, but it turns a dead end into a conversation and tells you how important the gap is.
2. A problem you cannot solve straight away
Situation: a coding question, an estimate, a calculation or a case question where you do not see the answer immediately.
Here, do not say “I don’t know” and stop. Work in the open. Northeastern advises explaining your approach before you start, asking clarifying questions about inputs, edge cases and scope, and, if you are unsure, making a reasonable assumption and continuing. Virginia Tech suggests thinking out loud as you decide which method to use.
Illustrative answer: “I don’t know the exact figure, so let me reason it through. I’ll assume [assumption]. On that basis… If the assumption is wrong, the number would change in this direction.”
Stating your assumptions is important. It lets the interviewer correct one assumption rather than dismiss the whole answer.
3. A behavioural question with no matching example
Situation: “Tell me about a time you managed a budget” when you never have.
Do not invent a story. Be honest, then offer the closest real example, and say how it relates.
Illustrative answer: “I haven’t held a formal budget. The closest experience is organising our department’s annual event, where I tracked spending against a fixed amount and had to cut two items when quotes came in high. I’d expect a formal budget to involve more reporting, which I’d want to learn early.”
If you have nothing close at all, say how you would approach it, and keep it short. A hypothetical answer is weaker than a real example, but stronger than a made-up one that falls apart under follow-up questions.
4. A hypothetical you have never faced
Situation: “What would you do if a client threatened to cancel the contract?”
You are not expected to have done it. You are expected to show judgement. Give your priorities in order: what you would do first, who you would involve, what you would avoid. Say where you would check company policy or ask a manager, because knowing the limits of your authority is part of a good answer.
5. A question about the company you did not research
Situation: “What do you think of our latest product?” and you have not seen it.
This gap is harder to defend, because it was within your control. Do not pretend. Briefly acknowledge it, and show what you do know about the organisation.
Illustrative answer: “I haven’t looked at that product in detail. I focused my preparation on [area you did research]. What I’d want to understand is who it’s aimed at, and how this role supports it.”
Then make a note to research more thoroughly before the next round.
6. A question that relies on a qualification or licence you do not hold
Situation: “How would you apply [regulation or standard] here?” for a role where it is listed as desirable, not essential.
Say plainly that you do not hold it or have not applied it, and give a concrete plan if you mean to get it, such as a course you have booked or a date you plan to take the exam. Avoid vague promises; if you have no plan yet, say you would discuss timing with your manager.
What to say, and what to avoid
| Avoid | Why it hurts | Try instead |
|---|---|---|
| A long, confident answer you are not sure of | Follow-up questions expose it, and trust drops | “I’m not certain. My understanding is X, but I’d confirm it before acting on it.” |
| “I don’t know.” Then silence | Gives the interviewer nothing to assess | Admit the gap, then reason aloud or offer the nearest real example |
| Several apologies | Makes a small gap look large and uses up time | One acknowledgement, then move on |
| Changing the subject to a prepared answer | Interviewers notice, and the question remains unanswered | Answer what you can, then add the related example openly |
| Inventing a story or a figure | Can be checked later, including at reference stage | Use a real example that is close, and say how it differs |
After the interview
A gap in the interview is useful information. Write down the exact question as soon as you can, then find the real answer. This helps in two ways: you will be ready if the next interviewer asks it, and it shows you what the employer considers important.
If the gap was significant and the answer turned out to be simple, you can mention it briefly in a follow-up email: “You asked about X. I looked into it afterwards, and…” Keep it to two or three sentences. It shows that you follow through, but it should not read as a second attempt at the interview.
If the same question keeps exposing a real skill gap, that is worth addressing in your CV as well. If you are learning the skill, list the course or project honestly; the resume builder makes it easy to keep a version of your CV for each type of role. For other common interview and CV questions, see the resume questions hub.
Frequently asked questions
Is it acceptable to say “I don’t know” in a job interview?
Yes, as long as you do not stop there. Admit the gap, then show what you do know nearby, how you would reason towards the answer, or how you would find it. Careers services including gradireland and Northeastern University advise honesty over bluffing.
How long can I pause before answering?
A few seconds is normal. If you need longer, say so: gradireland suggests asking for a minute to think the question through. A short, explained pause looks considered; a long, unexplained silence can look like you have frozen.
Can I come back to a question later in the interview?
You can ask, particularly if your mind has gone blank rather than you lacking the knowledge. If you do, make sure you return to it before the end, ideally when the interviewer asks if you have anything to add.
Will not knowing one answer cost me the job?
Not necessarily. Interviewers assess your answers together, and in problem-solving questions they often weigh your reasoning and communication as well as the result. A gap in a core skill listed as essential in the job description matters more than a gap in something peripheral.
Sources
- Interview questions, gradireland
- Interview Type: Technical, Northeastern University Career Design
- Technical interviews, Virginia Tech Career and Professional Development