What to say when you are stuck

Every technical round is designed so that you eventually hit something you cannot immediately do. That is the point — an interview where you sail through tells the interviewer nothing about your ceiling. What they are watching for is what you do in the ninety seconds after you get stuck, and there are only two options: you make the difficulty visible, or you go quiet and hope.

Say where you are

"I know I need to handle the overlapping ranges here, and I can see two ways to do it — sort first and merge, or keep an interval tree. I'm weighing which is simpler to write correctly in the time we have. Let me try the sort."

That sentence costs ten seconds and changes the interviewer's read entirely. They now know you understand the problem, that you have options, and that you are making a decision rather than stalling. Silence transmits none of that.

Ask for the hint properly

Asking for help is allowed and is scored on how you ask. A specific question gets a useful answer and does not cost you much: "am I right that we need this to stay stable under duplicates, or can I ignore that case?" is a good question. "I'm stuck, can you help?" is not — it hands the whole problem back and is the version that hurts.

Reduce the problem

• Solve the smaller version out loud. "Let me do it for a single user first and then generalise" is a legitimate technique, not an admission of defeat.
• Hard-code something and name it. "I'll assume this is sorted for now and come back to it" keeps you moving with a visible debt.
• Walk a concrete example by hand. Most stuck moments dissolve when you stop thinking abstractly and trace three actual values.
• Say your assumption aloud. Half the time the interviewer corrects it immediately and you were stuck on a misunderstanding, not a difficulty.

When you truly do not know

Say so, and then say what you would do about it. "I haven't worked with that directly. What I'd do is look at how the existing service handles it and start from there — my guess at the shape is this, but I'd want to check." This is a strong answer. Confidently inventing an answer is the weak one, and it is transparent to anyone who does know.

Nobody is hired for knowing everything. People are hired for being useful in the moment they don't.