What to Do When You Don't Know the Answer to an Interview Question

What to Do When You Don't Know the Answer to an Interview Question

Linkjob AI

Every candidate eventually hits a question they can't answer. A technical detail you've never used, a framework you forgot, a "how would you estimate" puzzle that leaves your mind blank. How you handle that moment often matters more than the gap itself, because interviewers are watching how you behave under uncertainty, which is what the real job looks like most days.

Don't bluff

Inventing an answer is the worst option. Experienced interviewers usually notice, and once they catch one confident wrong answer, they start doubting the correct ones. Saying "I haven't worked with that directly" costs you far less than being caught making something up.

Say what you do know

"I don't know" is a dead end. "I haven't used Kafka in production, but I've built a queue-based system with RabbitMQ, and I'd expect the trade-offs around ordering and retries to be similar" is a bridge. It shows adjacent knowledge and honest limits at the same time.

A useful pattern:


  1. Acknowledge the gap in one sentence.

  2. Connect to the closest thing you have done.

  3. Reason out loud about how you'd approach it.

Reason through it in the open

For problem-solving questions, a blank answer and a thoughtful attempt are very different signals. Restate the question, state your assumptions, and work forward step by step. "I'd start by figuring out how many users are active per day, then estimate requests per user" is already a strong start, even if your final number is off.

If you get stuck mid-way, say where and why: "I'm not sure whether this index would be used here; I'd check the query plan." That's what a good engineer or analyst does at work.

Ask a clarifying question

Sometimes you don't know the answer because the question is ambiguous. Asking "Do you mean in a single-region setup or across regions?" is not stalling; it's precision. Just keep it to one or two questions so it doesn't feel like avoidance.

Show you'd close the gap

End with what you'd do next: "I'd read the documentation on its consistency guarantees and run a small test before relying on it." Interviewers hire people who learn quickly, not people who already know everything.

Follow up afterwards

If the question bugs you after the interview, look up the answer and mention it briefly in your thank-you note. It's a small touch that shows curiosity and ownership.

Practise the uncomfortable moment

The best way to stay calm is to rehearse not knowing. Ask a friend to throw unfamiliar questions at you, or use a mock interview tool such as Linkjob AI to practise answering out loud. (Disclosure: I work on Linkjob AI.) After a few rounds, "I'm not sure, but here's how I'd think about it" stops feeling like failure and starts feeling like your normal answer.

Report Page