What to Do When You Don't Know the Answer

In this chapter

Every real interview contains a question you cannot answer from memory.

Junior people panic and fill the air. Senior people sometimes fake expertise and die on the follow-up. The useful move is narrower: say what you do not know, show how you would think, and leave them a way to help you.
This is distinct from general prep.

Prep reduces how often the moment happens. It does not eliminate it. A process that never asks something you have not seen is not hiring for the job. They are hiring for a quiz.
The goal is not to “look smart.” The goal is to remain hireable: honest, structured, still in the problem.

People remember how you were when you were empty more than how you were when you were fluent.

One clean sentence first: “I have not done X.” Then immediately: “Here is the adjacent thing I have done,” or “Here is how I would find out in the first week.” Adjacent truth is a senior move.

A filibuster of related trivia is a junior move. “I’m not sure, but…” followed by a confident wrong answer is the worst of both.
Do not apologize five times.

Do not smile it off. Do not attack the question. The interviewer asked it because it sits on the posting or on their last incident. Respect the ask even when your map has a hole.
If you almost know, separate the parts: “I am solid on A.

B I would need to look up. For C I would start with…” That is a scorecard they can use. A fog of “kind of” is not.

When the question is a problem, not a fact, you can think in front of them without claiming knowledge you do not have.

Restate. Name the constraint. Offer a first-cut approach labeled as a guess. Invite correction: “If I am wrong about the volume, this falls apart.”
2
Use units, orders of magnitude, and process.
- “I don’t know the statute by number
- I would look up the retention rule, then ask compliance before I deleted anything.” That is an answer. Inventing the statute is not.
3
Bridging: take their noun to your nearest real episode, then come back.
- “I have not run that vendor RFP. I have run a three-bid process for a smaller tool
- I would expect the same traps around scope and who signs.” Then stop. Do not drag them into a twenty-minute story they did not ask for.

Ask a narrowing question.

“Are you looking for the algorithm, or for how I would debug it in production?” Often they will tell you the rubric. That is not cheating. That is communication.
Take the hint.

Repeat it. Use it. People who reject hints to protect ego fail this moment twice.
If your mind is blank, buy one breath: look at the posting atom on your page, or repeat the question.

Ten seconds of quiet is allowed. Thirty seconds of panic noise is not. Then pick a structure even if the content is thin.

Bluffing a tool, a drug, a court, a library, a machine.

The next question will be “how.” You will not have a how.
Talking until they change the subject.

They will not remember your courage. They will remember that you could not stop.
Collapsing: “I don’t know” and a shrug, twice, with no structure.

Honesty without a next move looks like you leave holes in the job too.
If the hole is central to the posting — the main verb of the job — you may be in the wrong interview.

You can still be decent in the hour. You should not pretend you are a specialist. Decide after, with a clear head, whether to continue the process.

Practice one sentence of hole-plus-method for each posting atom you are weak on.

Out loud. That is the drill. You are ready when a friend can ask a question off the side of the JD and you can do honesty, structure, and a check-in without spiraling.
The next chapter is the uglier cousin: you thought you knew, you answered, and you hear yourself being wrong.

Recovery is a different move from a clean “I don’t know.”

Generate questions from that job description — free preview, $2 for the full kit. No account. Paste a job description.