An interviewer offers a hint mid-solve — how do you take it, and what does resisting it signal?

## What a hint actually means The most damaging belief in this whole area is that a hint is a failure marker — that the round was fine until the interviewer spoke, and now it is over. In practice the opposite is closer to true. Interviewers hint because they want a signal they cannot get from a stuck candidate: they already know you are stalled, and watching you stay stalled teaches them nothing further. Handing you a lever converts dead time into observable behaviour. Many loops are explicitly calibrated with the expectation that hints will be given, and the rubric asks how the candidate *used* them, not whether they were needed. So the question a hint really asks is: how do you behave when someone with more context tells you something you did not have? That is a question about working with a colleague, and it is scored as such. ## The three-part recovery **Receive it.** Stop typing. Fingers still on the keyboard while someone explains something is the physical form of not listening. Then say it back in your own words: "So — consider the bookings in order of start time rather than in the order they arrive." This costs five seconds and does two jobs. It proves you heard the hint rather than a hint-shaped noise, and it lets the interviewer correct you immediately if you heard it wrong. Candidates lose real time acting confidently on a misheard hint. **Price it out loud.** A hint is not an instruction; it is a direction with consequences. Say what you think it buys and what it costs: "That adds an ordering step before I start, so I pay for that up front. What I think I get back is that I stop re-examining entries I have already dealt with. Let me run that on the three-booking example and see whether it holds." This is the beat that separates a candidate who *understood* the hint from one who is merely obeying it. Obedience is a weak signal; understanding is the thing being tested. **Act visibly, and name what you are abandoning.** "I'm dropping the pairwise comparison I started — it does not survive this change — and restructuring around the ordered pass." Explicitly retiring the old plan matters, because otherwise you end up with a hybrid: half the code assuming the old shape and half the new. That hybrid is where most post-hint solutions actually die, and the interviewer can see it coming long before you can. ## The four ways candidates mishandle hints **Defending the stalled approach.** "I think mine works, I just need to handle one more case…" said for the third time. Sometimes it is even true, and it is still the wrong move: you are spending the interviewer's offered help on an argument. If you genuinely believe your path is close, the way to say it is a bounded proposal, not a defence: "I think I'm two minutes from correct — can I finish this case, and if it doesn't fall out I'll take the reordering?" That is negotiating with a plan, and interviewers accept it. **Silent absorption.** Nodding, going quiet, then producing the hinted solution as though it were yours. It looks like concealment, and it destroys the only thing the hint was supposed to reveal: how you reason with new input. **Nod-and-continue.** "Right, yes, good idea" — and then the next line of code is from the old plan. This is the most common failure, and it usually is not defiance; it is that the candidate has not actually re-planned and their hands keep going. It is exactly what the restate-and-price beats prevent. **Over-collapse.** Treating one hint as proof that everything you did was wrong, discarding correct work, and losing composure. A hint is usually local: it fixes one step, not your whole approach. Ask which part it touches. ## Asking for a hint yourself Asking is legitimate, and how you ask is itself a signal. A bad ask is "I'm stuck, can you help?" — it transfers the whole problem. A good ask localises: "I've got the structure I want, but I can't find a way to avoid re-examining entries I already handled. Am I missing something there, or is that inherent?" That tells the interviewer exactly where to aim, proves you have a model of your own blockage, and often gets a smaller, cheaper hint than the one you would otherwise have been given. Do it after you have visibly tried something, not as a first move. ## The underlying signal Every one of these behaviours is a proxy for a working relationship: what happens when a reviewer leaves a comment on your change, when a design gets challenged, when someone senior says "have you considered ordering these differently?" Interviewers know they cannot observe a year of collaboration in forty minutes, so they read the two minutes after the hint as a sample of it. Take the data, restate it, price it, use it, and say what it cost you. That sequence is the whole answer.