Detailed explanation
If you do not know an answer in an interview, acknowledge the gap honestly and then show how you would handle it constructively. You can say, “I haven't worked with that API, so I don't know its exact behaviour.” This is more credible than guessing confidently or giving an unrelated answer. For a fresher or junior developer, incomplete knowledge is understandable; the important distinction is between something you know, something you infer, and something you still need to verify.
Before concluding that you cannot answer, check whether the question is unclear or simply unfamiliar. If a term has multiple meanings, ask a focused clarification, such as, “Do you mean how authentication works generally, or how this library implements it?” If you understand the question but cannot recall a detail, take a brief pause. Then explain any relevant knowledge you do have. For a coding or problem-solving question, state your assumptions, work through a small example, and describe a basic approach before attempting an optimisation. Ask for a hint when it would help you move forward.
When discussing an unfamiliar tool or feature, explain how you would verify your understanding rather than merely saying you would search online. For example: “I haven't used that API, but similar APIs use pagination for large results. I would check the official documentation for its parameters and response format, then try a small request. May I walk through my reasoning?” This demonstrates a practical learning process while clearly labelling the proposed behaviour as an inference, not a fact. If you have no useful starting point, admit that directly instead of forcing an explanation.
Interviewers may use such moments to assess honesty, communication, problem-solving, and willingness to learn, alongside technical knowledge. A transparent response does not guarantee a positive outcome, especially if the missing knowledge is essential to the role, but bluffing adds a credibility problem to a knowledge gap. Keep your response brief enough to let the interviewer decide whether to offer a hint, explore your reasoning, or move on. Afterwards, note the topic and study it so that the experience becomes a concrete learning opportunity.
Key points to remember
- Acknowledge what you do not know without excessive apologies.
- Clarify ambiguous questions before attempting an answer.
- Separate established knowledge from assumptions and guesses.
- Explain a relevant reasoning process or specific verification plan.
- Accept a hint or move on gracefully when you cannot make progress.
Common mistakes candidates make
- Bluffing with technical jargon or presenting guesses as facts.
- Stopping at “I don't know” when you could offer useful reasoning.
- Rambling, repeatedly apologising, or promising to learn everything immediately.
Likely follow-up questions
Is it acceptable to ask the interviewer for a hint?
Yes, particularly in a problem-solving discussion. Explain where you are stuck and ask a specific question rather than asking for the entire solution.
What if I know part of the answer?
Explain the part you know and clearly identify the missing detail. You can reason beyond it, but label assumptions rather than presenting them as confirmed facts.
Should I look up the answer during the interview?
Only if the interviewer permits external resources; ask before using documentation, search, or AI tools. Otherwise, describe how you would verify the answer without actually looking it up.
Interview tip: Practise a calm three-part response: acknowledge the gap, offer relevant reasoning, and explain how you would verify it.