How to Handle 'I Don't Know' in an Interview

What do you say when you don't know the answer in an interview?

Never just say "I don't know" and stop. Acknowledge the gap, then pivot — to what you do know, to the closest related concept, or to how you'd find the answer in the next five minutes. Interviewers expect new grads to have gaps; they're grading how you handle the unknown, not whether you have it memorized.

The 3-step pivot

Use this every time a question hits a gap:

Step 1 — Acknowledge briefly (5 seconds). "I haven't worked directly with that, but…" Don't apologize. Don't go on about how you should know it. One short sentence, then move.

Step 2 — Bridge to what you do know (15-20 seconds). "…I've used [related thing], which solves a similar problem by [mechanism]." This shows you can reason by analogy — one of the strongest signals of engineering judgment, per the Harvard Business Review's research on interview signal.

Step 3 — Propose how you'd close the gap (10-15 seconds). "If I needed to ship this on Monday, I'd read [docs / source / paper], try a minimal example, and check it against [reference]." Now you've signaled that you can learn fast — which is what the interviewer is actually trying to measure for an entry-level role.

What to avoid

Three failure modes that tank candidates faster than honestly saying "I don't know":

1. Bluffing. If an interviewer asks you to explain TCP slow-start and you make it up, two things happen: senior engineers spot it within a sentence or two, and the rest of the interview is rated against that moment. The hiring decision often locks in right there.

2. Defensive non-answers. "That's a really tough question. I'd have to think about it." If you stop there, you've said nothing. The Levels.fyi interview-debrief data flags this as one of the highest-correlation predictors of "weak hire" or "no hire" outcomes.

3. Pivoting to something completely unrelated. If you can't bridge from what was asked to what you do know in one sentence, the pivot reads as evasion. Better to say "I don't know, but I'd start by…" than to launch into an unrelated topic.

Behavioral questions: the adjacency rule

For behavioral questions ("tell me about a time you led a team"), the same logic applies. New grads often haven't led a team. That's fine. Use adjacency:

"I haven't formally led a team yet. The closest I've done is mentoring a junior intern at [company] for two months. The thing I learned was…"

Now you've answered the question. You've also shown self-awareness about where you are in your career, which is a stronger signal than fabricating leadership experience that didn't happen.

Per the Indeed Career Guide's interview research, recruiters explicitly look for candidates who can map their actual experience to the question, even when the experience isn't a perfect fit. Adjacency is acceptable. Invention is not.

When the question is testing whether you'll bluff

Some interviewers — especially at senior engineering teams — ask questions on purpose that they expect you won't know. The point of the question isn't the answer. The point is to see whether you'll admit the gap or fake it.

If you sense this is happening (often signaled by the interviewer pressing follow-ups on a topic you've already shown unfamiliarity with), say it plainly: "I don't want to guess on something I haven't actually used. Could you walk me through it, and I can ask follow-ups?" That answer often scores higher than the correct one.

About the author: Alex Chen is the founder of InterviewChamp.AI and writes about the modern tech interview from the inside — what changed, what works for new grads, and where the old playbook fails.