Taking feedback in the room
A hint, a redirect, a new constraint or a correction can land mid-answer. Hear it, decide, act on it where the interviewer can see, and return to your thread. Your reaction is read as how you take feedback at work.
What it is
Feedback in the room is anything the interviewer says mid-answer that asks you to adjust: a hint ("have you considered a queue here?"), a steer toward a different part of the problem, a constraint added to a design you've already drawn, or a question that interrupts a story. We use the same word for a role-play note followed by a second run, because the moves are the same. Hello Interview reports that interviewers often introduce these on purpose to see how you respond, and that some are trained to knock a candidate off a line that sounds rehearsed. A Microsoft recruiter's published list of what her interviewers look for includes how you adapt to changing requirements and how you handle feedback.
| What you hear | What it usually is | Taking it looks like |
|---|---|---|
"Have you considered X instead?" | A probe: a check on depth, or a test of how you respond to pushback. It doesn't mean your answer is wrong. | Weigh X against your choice aloud, then pick one and say why. |
"Let's move on to the data model." | A steer toward an area they want to see. | Finish your sentence, then go there without defending the part you were on. |
"Now assume ten times the writes." | A requirement change. They want to see what breaks. | Name the component that fails first and what you'd change, or say why the current design holds. |
"Wait, who made that decision?" | A narrow question about one detail of your story. | Answer that detail in a sentence or two, then say where you were and continue. |
"Try that again, and this time open by acknowledging the customer's frustration." | A note before a second run of a role-play. | Do the one thing the note asked, first and visibly, before anything else you'd planned. |
The four moves. First, hear it: stop and repeat the point back in your own words. Amazon's guide to common interview mistakes asks candidates to check their reading of a question against what the interviewer meant before solving anything, and that applies as much to a hint halfway through as to the opening question. Second, decide aloud: take it or decline it, and say which. Third, act where they can see it: change the box on the diagram, give the short answer to the interrupting question, or in a second run do the thing the note asked. Fourth, return: name the place you left ("back to the fan-out question") so the thread isn't lost.
Declining is allowed, with a reason. A suggestion that conflicts with a requirement you both agreed on earlier is a chance to show judgment. Say what the suggestion would gain, what it would cost against that requirement, and which you'd choose, then offer to go their way if they'd like to see the alternative. Show the reasoning rather than wave the idea off: dismissing a suggestion without weighing it reads as hard to work with.
Why it carries weight. A round is a short sample of working with you, and feedback is one of the moments in it that looks most like a real day on the job. The Microsoft Life piece quotes a senior talent acquisition manager saying that being receptive to feedback and quick to adjust can count for more than a clean answer, because it shows room to grow.
When to use it
Use the four moves when the interviewer says something mid-answer that asks you to adjust. Three cases where it matters:
- You're stuck or drifting. Thinking aloud helps here: Microsoft's recruiters say that talking through your work as you go can earn you tips from the interviewers themselves, who'd like you to do well. A hint you take cleanly costs you little; one you miss costs the time they spent giving it.
- A new constraint lands on a design. Treat it as a requirement change: say which part fails first under the new load, the offline client or the stricter latency, and what you'd change. If the design already handles it, say why, in one or two sentences, rather than redrawing to look responsive.
- A second run after a note. Whatever the note asks for, do it at the start of the run so it can't be missed, and keep what worked the first time.
When not to
Taking feedback doesn't mean taking it literally, or taking all of it.
- When it conflicts with an agreed requirement. Decline with the reason and offer the alternative. Switching anyway, without a word about the conflict, drops a requirement you both set.
- When the "hint" is a clarifying question. "Is that cache per user?" asks what you meant; answer it. Rebuilding the design because they asked reads as not having had a reason for it.
- When an interruption asks about one detail. Answer the detail. Restarting the story from the top spends the time they set aside for depth. See The two-minute answer.
- When a suggestion would replace your design wholesale. "Have you considered X?" doesn't have to mean your approach is wrong. Dropping everything for X without weighing it shows as little judgment as ignoring X.
- When you haven't proposed anything yet. Waiting for the interviewer to supply the direction leaves them nothing to react to. Put a first version down, then adjust it; the adjusting is the part they can score.
Compared
| Response | Sounds like | What it shows | When it's the right move |
|---|---|---|---|
Take it as given | "Sure, a queue. Let me add it." | You can adopt a direction fast. On its own it can look like compliance without thought. | The hint settles something you were unsure about, or time is short and the hint is plainly where they want to go. |
Take it with the trade-off | "A queue decouples the two; the cost is that the caller no longer gets a synchronous confirmation. I'd add it and have the client poll for status." | You weighed it and still moved. Our pick whenever nothing you agreed on earlier stands in the way. | The suggestion fits the requirements you set, or improves on your choice, and you can name what it costs. |
Decline with a reason | "I'd keep the synchronous write because we agreed the sender sees their own message. Happy to sketch the async version to compare." | Judgment, and that you remember the requirements. Risky if the reason is thin. | The suggestion conflicts with something you both agreed on, and you can say what. |
Ask what's behind it | "Is the concern the p99 or the cost per request?" | You'd rather fix the right thing than the first thing. | The hint is ambiguous. Costs a few seconds; asking it twice in a row starts to look like stalling. |
Finish your point, then take it | "One sentence to close this, then yes." | You can hold a thought and still listen. | A single sentence completes the point. Longer than that reads as not listening. |