Don't Bluff in an Interview: The Power of Saying 'I Don't Know Yet'
There is a moment in an interview that can make even a capable candidate panic. The interviewer asks a question, you understand what they are asking, but the answer is not coming. Maybe they mention a software tool you have never used. Perhaps they ask about a situation you have never handled. Or they ask a technical question and you are not completely sure of the answer.
Your mind starts racing. You want to impress them, so you consider guessing, using big words or giving an answer that sounds confident but is not quite true. Resist that temptation. You do not have to know everything to be a strong candidate. But you do need to show honesty, judgement and the ability to learn.
One of the most useful responses is: 'I don't know the answer to that yet, but I can explain how I would find out.' The word yet matters. It acknowledges the gap without presenting it as permanent, and it gives you an opportunity to show the interviewer how you approach something unfamiliar. It only works, however, when you follow it with a thoughtful next step.
## Why bluffing can work against you
An interviewer may ask a follow-up question to understand how you reached your answer. If you have invented experience or guessed at a technical detail, it can become difficult to explain your reasoning. You may also create an expectation that you can perform a task you have never actually done.
Bluffing does not demonstrate confidence. It can raise questions about your judgement and reliability. A candidate who can identify the limits of their knowledge and respond constructively may demonstrate more professional maturity than someone who pretends to know everything.
This does not mean you should answer every challenging question with 'I don't know'. The aim is to give the strongest truthful answer you can. If you have relevant experience, use it. If you understand the principle but not the exact detail, explain what you do understand. If the subject is genuinely unfamiliar, say so and describe how you would approach learning it.
## How to answer when you genuinely do not know
Start by acknowledging the gap briefly. Avoid a long apology or a nervous explanation. Then explain what you can say with confidence, identify how you would close the gap and connect your response to the role.
For example: 'I haven't used that particular system yet, so I wouldn't want to claim experience I don't have. I have used a similar platform to manage records and track requests. I would start by understanding your workflow, reviewing the guidance and practising the key tasks. I'm confident I can build familiarity with it.'
That answer is stronger than simply saying 'I don't know' because it gives the interviewer useful information: you are honest about your experience, you can identify transferable skills and you have a sensible learning approach.
## Use these responses in common interview situations
### 1. When asked about a tool or software you have never used
Try: 'I haven't worked with that tool yet. I have used [name a genuinely familiar tool] for [explain the relevant task]. I would expect some differences, but I understand the underlying process and would take time to learn the specific system.'
Do not claim that two tools are identical if they are not. Explain the relevant similarity, not an invented level of expertise.
### 2. When asked a technical question you cannot answer
Try: 'I don't have the confirmed answer to that at the moment. My first step would be to check the relevant documentation or source, test the information where appropriate and confirm the answer before acting on it.'
If you know part of the answer, share that part and make the boundary clear: 'What I can confirm is... The part I would need to verify is...' This shows that you can separate facts from assumptions.
### 3. When asked about a situation you have never experienced
Try: 'I haven't faced that exact situation yet. A similar challenge I have handled was... I approached it by... In this situation, I would first...' Then walk the interviewer through the steps you would take.
You can draw on internships, volunteering, academic projects, community responsibilities or personal projects when they are relevant. Be clear about the context and your actual contribution. Do not present a classroom exercise as professional employment.
### 4. When given a problem and asked to solve it on the spot
You do not always need to rush into an answer. Ask a clarifying question if an important detail is missing. Then explain your assumptions and work through the problem logically. You can say: 'Let me think through this. I would first establish..., then I would check..., and based on that information I would...' The interviewer may be assessing your reasoning as much as your final answer.
### 5. When you realise your answer may be wrong
Correct yourself calmly. Try: 'I want to correct one part of what I just said. I may have mixed up those two points. The more accurate explanation is...' Being able to recognise and correct an error is better than defending an answer you no longer trust.
## The difference between 'I don't know' and 'I don't know yet'
'I don't know' can sound like the conversation has reached a dead end, especially when you stop there. 'I don't know yet' leaves room for learning, investigation and action. But the word yet is not a magic phrase. If you say it without showing how you will respond, it can sound like a polished way of avoiding the question.
A useful structure is: acknowledge what you do not know, explain what you do know, describe how you would find out and connect that approach to the job. Keep it concise. The interviewer does not need a speech about your willingness to learn; they need evidence that you can approach a knowledge gap responsibly.
## What if you promised to find out? Follow through.
Sometimes an interviewer may ask for a specific detail you cannot confirm during the conversation. If you say you will check it, make a genuine effort to do so. If you find a reliable answer and the interviewer's contact details or recruitment process allow follow-up, send a short email the same day where practical.
For example: 'Thank you for the conversation today. You asked about [specific question]. I wanted to follow up after checking the information. The answer is [concise, verified answer]. I appreciate the opportunity to clarify this.'
Do not send an email just to manufacture an extra impression. Do not guess again, send an unverified answer or use the follow-up to add a long explanation. If you cannot verify the information that day, do not pretend you have. Send a brief update only if appropriate, and be clear about what remains to be confirmed.
Also remember that not every interview question requires a follow-up email. Use this approach when you have explicitly committed to checking something and can provide useful, accurate information. Respect the recruiter's instructions and avoid repeated messages if the process does not invite further contact.
## What you should avoid saying
Avoid 'I know it, I just can't explain it' if you cannot demonstrate the knowledge. Avoid pretending you have used a system because you watched a tutorial. Avoid blaming nerves for every gap. Avoid giving a random answer just to fill the silence. And do not turn 'I'm a fast learner' into your entire response; support it with an example of something you have learned and applied.
You should also avoid underselling yourself. If you have related experience, do not dismiss it simply because the context was different. Explain the connection honestly and let the interviewer assess its relevance.
## Practise before your next interview
Think about the role you are applying for. List five tools, processes or situations that may come up in the interview. For each one, mark what you can do confidently, what you have some exposure to and what you have not done yet.
For every gap, prepare a truthful response. Identify a related skill or experience, the first step you would take to learn or investigate, and one example that shows you can adapt. Practise saying the answer aloud without memorising a script. You want to sound prepared, not rehearsed.
You can also practise with a friend who asks follow-up questions. If your answer is based on genuine experience, you should be able to explain what you did, why you did it and what happened. If you cannot, revisit the example before the real interview.
## The interviewer is not looking for a human encyclopaedia
A good interview is not a test of whether you have memorised every possible answer. Employers need people who can do the work, communicate clearly, make sound decisions and recognise when they need more information. The exact balance depends on the role, and some jobs do require specific knowledge from day one. Honesty does not remove those requirements, but it helps an employer understand your actual capabilities.
So the next time a question catches you off guard, pause. Do not bluff to protect your ego. Give the best truthful answer you can, explain how you would close the gap and follow through if you promise to check something. You may not know the answer yet. What matters is what you do next.
For a more structured approach to preparing for interviews and managing your job search, explore *You've Been Job Hunting the Wrong Way* by Eniola Oyeleye. The book offers a practical framework for approaching your search with more intention. Find the available formats on the [Zidepeople book page](https://www.zidepeople.com/book/job-hunting-the-wrong-way).