How Do I Answer an Interview Question When I Don't Know the Answer?
TL;DR: Don't bluff and don't go silent. Say what you do know, walk through how you'd figure out the rest, and ask a clarifying question if one would genuinely help. Interviewers usually score your problem-solving process here more than the final answer.
The Claim
Nobody expects a candidate to know everything. What interviewers are actually watching for is how you handle not knowing — because that's exactly what happens on the job constantly.
The Evidence
This pattern shows up consistently in coding-interview and behavioral-interview advice: bluffing with false confidence is the single worst response, because it's usually detectable and destroys trust immediately once discovered. Interviewers across technical and non-technical rounds consistently rate "I don't know the exact answer, but here's how I'd find out" higher than a confident wrong guess.
Bluffing vs. Transparent Problem-Solving
| Response type | What it signals | Likely outcome |
|---|---|---|
| Confidently guessing wrong | Poor judgment, risk of it happening on the job | Damages trust once the gap is exposed |
| Freezing or going silent | Lack of composure under pressure | Reads worse than an honest "I'm not sure" |
| "I don't know, next question" | Gives up too early, no attempt at reasoning | Misses a chance to show process |
| "I'm not certain, but here's my reasoning..." | Honesty plus problem-solving skill | Often scores as well as a correct answer |
Step-by-Step
- Pause briefly rather than rushing a guess — a short pause reads as thoughtful, not weak.
- State clearly what you do know or a related concept that's adjacent to the question.
- Reason out loud toward an answer, even an incomplete one — this is what's actually being scored.
- If relevant, ask one clarifying question that would genuinely help you narrow it down.
- If you truly can't get there, say so directly and pivot: "I don't have that specific answer, but here's how I'd find out on the job" — then move on without dwelling on it.
FAQ
Is it better to guess or admit I don't know? Admit it and show your reasoning process — a transparent "I'm not sure, but here's my thinking" consistently scores better than a confident wrong guess.
Should I ask the interviewer for a hint? Yes, if you've genuinely tried first — asking for a nudge after showing effort is normal and often expected in technical interviews.
Does one unanswered question sink the whole interview? Rarely — interviewers weigh your overall pattern of reasoning across the full conversation, not a single gap.
By Pinal Dave Last updated: 2026-07-24