In this article
Before you start
Why interviewers ask this
The question is a test of how you behave when someone tells you that you fell short, and the answer shows whether you learn from it or defend yourself. Receiving feedback is hard for almost everyone: Heen and Stone say in the summary of their Harvard Business Review article that "almost everyone, from new hires to C-suite executives, struggles with receiving it" (Heen and Stone, 2014). An interviewer who asks it is looking for evidence you will take correction on their team.
Many employers use a structured interview, where every candidate gets the same questions and is scored on the same rubric. Google says it documents "what a poor, borderline, solid, and outstanding answer would cover" (Google re:Work, March 2026). A weak answer says "I take feedback well". A strong one gives the interviewer something to score: a specific message, a reaction, a change and a result.
Answering a tough-feedback question from first principles
- Tough feedback
- Tough feedback is a message that says your work or behaviour fell short of what someone needed, and that was hard to accept when you first heard it, so taking it in required a deliberate step.
- Feedback trigger
- A feedback trigger is a reaction that makes feedback hard to take in; Stone and Heen group them into truth triggers, which judge whether the feedback is right, relationship triggers, which depend on who is saying it, and identity triggers, which depend on who you are and how you are wired.
- Closing the loop
- Closing the loop is a follow-up step in which you return to the person who gave you feedback after you changed something, to show what you did and ask whether it helped.
In plain words
Answering this question is like telling the story of a repaired bridge. You say what the inspector found. You say how you checked the report. You describe the repair and show that the bridge now holds. The analogy breaks in one place. A bridge cannot argue with an inspector, but you can, and the interviewer watches how you do.
Stated precisely, the answer is one specific piece of feedback, one way you checked it, one change and one result. It takes about 100 words. The Center for Creative Leadership (CCL) says useful feedback names the situation, describes "the actual, observable behavior" and states its impact (CCL, August 2025). Your story should start from feedback of that kind.
Step 1: Pick specific feedback that is real
The first step is choosing feedback a person could point to. The input is the last year of your work; the output is one message that was specific, true enough to act on and about how you work, not about who you are. "My updates came too late to plan around" is specific. "You need more presence" is a label.
The CCL method asks givers to describe observable behaviour, so choose feedback that was close to that. Avoid a disguised compliment such as "I care too much", a trivial remark, and anything that would disqualify you for the job. Choose feedback you acted on, because the rest of the answer depends on it. What you now know: which story you are telling.
Step 2: Show how you took it in
The second step is the reaction and the check. The input is the message; the output is one honest sentence about how it felt and one question you asked. Stone and Heen's triggers explain why the first reaction is often defensive. The Program on Negotiation (PON) summary of their talk advises you to get "beyond the label", ask for the specific past behaviour behind it, ask what to do differently, and ask for "one thing" you could do better (PON, July 2026). Say that you felt defensive if you did, then say you asked for one example. The interviewer is watching whether you open a conversation or argue. What you now know: the answer has a checking move.
Step 3: Close the loop and report the result
The third step reports the change, the return visit and the result. The input is what you learned; the output is an action, a conversation that shows it worked, and a result someone could observe. This is the rubric line of the question. MIT's Career Advising and Professional Development (CAPD) office suggests spending about 60 percent of a story answer on action and about 10 percent on result, and using "I" so your own contribution is clear (MIT CAPD, read October 2026).
Add the return visit: you went back to the giver, showed the change and asked whether it helped. A standout answer adds one more sentence, a standing check: a recurring check on how your work lands, such as asking your team each quarter. The strong sample below stops before it. What you now know: the answer is complete and the next question is the interviewer's.
Step-by-step description
- Choose specific, real feedback.
- Name the reaction and ask for an example.
- Change one thing, go back to the giver, report the result.
- Choose specific feedback you acted on.
- Say how it felt and ask for one example.
- Change one thing, go back to the giver and report a result someone could see.
A weak and a strong answer side by side
The difference between answers is evidence, not length. Speaking times use 152 to nearly 170 words per minute for English conversation (Yuan et al., 2006).1
What the numbers show
The weak answer is the shortest and carries no evidence. The strong and standout answers spend their words on a message, a check, a change and a result.
The lesson is about content, not length. A 54-word answer fits easily inside a minute; it simply says nothing a panel can check. The 100-word strong answer uses about twice the words on four things a panel can test later: a specific message, a question you asked, a return visit and an observable result. The standout answer adds a pattern that affects other people, a check with those people and a standing check, and at 137 words it still takes only about 48 to 54 seconds.1
Text description of the diagram
- A 54-word answer fits easily inside a minute.
- The 100-word strong answer uses about twice the words on four things a panel can test later.
| Fact | Weak sample | Strong sample | Standout sample |
|---|---|---|---|
| Words | 54 | 100 | 137 |
| Seconds at 170 words per minute | 19 | 35 | 48 |
| Seconds at 152 words per minute | 21 | 39 | 54 |
| Specific message quoted | No | Yes | Yes |
| Check shown | No | Yes | Yes |
| Return visit to the giver | No | Yes | Yes |
| Result | No | Yes | Yes |
| Standing check | No | No | Yes |
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →The Staff-level answer
A standout answer treats the feedback as information about a system the candidate owns, here the way a team works with them, and it changes something other people can see.
Tell me about tough feedback you received.
"My manager told me that engineers on my team found my design reviews intimidating, so they had stopped bringing me early drafts. It stung, because I thought I was being thorough. I asked two engineers for one review each that they remembered, and both described comments that read as verdicts. I made three changes: I opened every review with what worked, I phrased concerns as questions, and I asked authors to share drafts at the halfway point.
Early drafts came back, and late rework fell. After a quarter I went back to my manager and the two engineers and asked whether it had helped; they said drafts now arrived early. Because the problem was how I gave feedback, I now ask my team every quarter how my reviews land, and I give one example with every comment."
What makes it stand out: the feedback is about how the candidate affects other people, the check goes to the people affected and not only the manager, the result is a change in what the team does, it closes the loop with the people affected, and the ending is a standing practice.
The rubric
| Dimension | Weak answer | Strong answer | Standout answer |
|---|---|---|---|
| Example | "I always do my best" | One specific message | A pattern affecting others |
| First reaction | Denied or skipped | Named honestly | Named, then examined |
| Understanding | None | Asked for an example | Asked the people affected |
| Change | Nothing changed | One change | A change the team sees |
| Return visit | None | Asked the giver whether it helped | Asked the giver and the people affected |
| Result | "It worked out" | An observable result | A result the team sees |
| Standing check | None | Not needed | A recurring check on how your work lands |
Three variants of this question
"How do you handle criticism?"
Answer with the same three moves in the present tense, then give the example: you listen to the whole message, ask for one concrete instance, change one thing and go back to check. The PON summary recommends opening a conversation, not withdrawing (PON, July 2026).
"Tell me about a time you disagreed with feedback you received."
Pick feedback where, after you asked for an example, part of it was right and part lacked context. Say what you accepted, what you explained, and what you and the giver agreed to watch. Do not blame the giver. The trap is a story in which you were simply correct, because it shows no learning.
"Tell me about a time you gave someone tough feedback."
Use the Situation-Behavior-Impact order: the situation, the behaviour you saw without judging it, and the impact it had (CCL, August 2025). Then say how you checked that the person understood and what changed. The leadership interviews guide covers this at manager level.
Common mistakes
- Claiming you take feedback well. (wrong) "I welcome all feedback." (right) Tell one specific message, what you did and what changed. A claim gives the panel nothing to score.
- Choosing a disguised compliment. (wrong) "I was told I work too hard." (right) Pick feedback about a real shortfall. The greatest weakness page covers the same trap.
- Skipping the check. (wrong) "She said it, so I changed." (right) "I asked for one example, then changed one thing." Without the check, the panel cannot tell whether you understood the message.
- Blaming the giver. (wrong) "My manager did not understand my work." (right) Name what you took from the feedback, even if you disagreed with part. Blame makes you sound like someone who will defend yourself on their team.
- Ending on a feeling. (wrong) "I learned a lot." (right) A feeling is not evidence; end on the result, and have the standing check ready for the follow-up.
Follow-up questions
Did you get any critical feedback from your peer?
Yes, and peer feedback is a good choice because the person had no authority over you and you still acted. Use the same shape and add what the peer saw that your manager did not. The wider pattern for working across teams is in the engineering management interviews guide.
How did you react and improve?
Give the reaction in one honest sentence, then the change. "I felt defensive, I asked for one example, and I now post a three-line update each morning" answers both halves. The opener for the whole interview is covered in tell me about yourself.
What if I have never received tough feedback?
Everyone has received some, even if it was a review comment, a retrospective note or an offhand remark. Choose a milder example and tell it well; claiming none suggests either a lack of self-awareness or a lack of exposure. If the company publishes values, tie the story to one, such as Learn and Be Curious in the Amazon leadership principles.
What if the feedback was unfair?
Sort what was right from what was not. Say that you asked for the specific behaviour behind the label, that you found part of it fair, and what you did about that part. The why should we hire you answer is the place to explain strengths the feedback missed.
How long should the answer be?
Under a minute: about 100 to 120 words, which takes roughly 35 to 47 seconds at the 152 to nearly 170 words per minute of Yuan et al. (2006), leaving time for a follow-up; the standout sample runs to 137 words because it carries the standing check, and still takes under a minute.1 The three samples run from 54 to 137 words, or about 19 to 54 seconds. See the interview loop overview for where behavioural rounds sit, and save time for a closing question to ask the interviewer.
What would you do differently today?
Answer with the standing check, not a second story. Say what you now do by default, for example "when I get a label like 'communicate more', I ask for one example and check back after two weeks", and stop. This is the standing-check sentence of the standout answer, so keep it ready even if your main answer ends on the result.
- Pick specific feedback you acted on, not a disguised compliment.
- Name your first reaction in one honest sentence.
- Show the check: ask for one example before changing anything.
- Go back to the giver, report an observable result, and keep a standing check ready for the follow-up.
- About 100 words, rehearsed aloud, under a minute.
Sources
- Learning from Feedback Without Losing Your Mind — Program on Negotiation, Harvard Law School (Katie Shonk, summarising Heen and Stone), 1 Jul 2026
- Closing the gap between intent and impact: the SBII method — Center for Creative Leadership, 19 Aug 2025
- Using the STAR method for your next behavioral interview — MIT Career Advising and Professional Development (date = read date), 24 Oct 2026
- A guide to structured interviewing for better hiring practices — Google re:Work (updated March 2026), 1 Mar 2026
- Find the Coaching in Criticism — Harvard Business Review (Heen and Stone), January-February 2014 issue, 1 Jan 2014
- Towards an Integrated Understanding of Speaking Rate in Conversation — Interspeech 2006 (Yuan, Liberman and Cieri; University of Pennsylvania), 17 Sep 2006
