Interviewers love this question, and candidates underrate it. It looks like a softer, more reflective question than the conflict or failure ones, but it is quietly one of the most revealing things they can ask, because it tests something managers care about enormously and cannot easily assess any other way: are you coachable. Can someone tell you that you got something wrong without you becoming defensive, sulking, or explaining it away.
A manager's life is far easier with someone who takes feedback well, and far harder with someone who does not, however talented they are. So this question is really "will you be a nightmare to give feedback to", and your answer needs to demonstrate, through a real example, that the answer is no.
What a strong answer has to show
Three beats, in order, and skipping any of them weakens it:
- The feedback genuinely stung. If your example is trivial or comfortable, you have not shown anything. The feedback needs to have been hard to hear, something that touched a real weakness or a thing you were proud of.
- You took it in without getting defensive. Your first reaction can be honest (nobody enjoys criticism), but the answer must show you moved past the sting to actually consider whether they were right, rather than defending yourself.
- You changed something concrete. This is non-negotiable. Feedback you received graciously and then ignored proves nothing. The proof of coachability is the specific change you made and the fact that it worked.
A worked example
"In my first year of working, my manager sat me down and told me that in team meetings I was talking over people, and that a couple of colleagues had found it frustrating. That was genuinely hard to hear, because I thought I was being engaged and enthusiastic, contributing lots, and it turned out I was actually steamrolling quieter people without realising it.
My honest first reaction, internally, was defensive, I wanted to explain that I was just keen, that I did not mean anything by it. But I did not say that, because underneath the sting I could tell she was probably right, and the fact that colleagues had mentioned it meant it was a real pattern, not a one-off.
So rather than just resolving to 'be better', which never actually works, I gave myself a concrete rule: in meetings, I would not respond to a point until at least one other person had spoken after it, and I made a point of actively bringing in the two quieter colleagues by name. It felt unnatural for a few weeks, holding back when I had something to say.
A couple of months later my manager mentioned, unprompted, that the meeting dynamic had changed and one of those colleagues had specifically said they felt more able to contribute. The thing I learned was that the feedback that stings the most is usually the most accurate, because it is describing a blind spot, and blind spots are by definition the things you cannot see yourself."
Why it works
The feedback is real and it hurt, it touched something the candidate was proud of (their enthusiasm) and reframed it as a fault. That makes everything after it credible. The candidate is honest about the defensive first reaction, which is far more believable than claiming they welcomed the criticism instantly, and then shows the crucial move: setting the defensiveness aside because they could tell it was probably true.
Then comes the part that separates a good answer from a great one: a specific, mechanical change, the "wait for one other person to speak" rule, not a vague promise to improve. And a verifiable result, the manager and colleague both noticing the difference. The closing insight, "the feedback that stings the most is usually the most accurate, because it is describing a blind spot", is genuinely wise and signals real self-awareness. That is exactly the quality that makes a manager think this person will be easy to develop.
The ways it goes wrong
Fake feedback. Choosing criticism that was not really criticism ("they said I work too hard") is transparent and fails the same way a fake weakness fails. It shows you are not willing to be honest, which is the opposite of what the question rewards.
Getting defensive in the retelling. If, while describing the feedback, you keep justifying yourself ("but really it was because the others were too quiet"), you demonstrate the exact defensiveness the question is screening for. You can note your initial reaction, but the answer must show you got past it.
No change. "I listened carefully and thanked them" is not enough. Feedback received well but acted on not at all proves nothing about coachability. The concrete change is the whole point.
Disproportionate feedback. Do not pick feedback so devastating it raises doubts about your competence, or so minor it shows nothing. Aim for a real, specific weakness that you meaningfully addressed.
A change with no evidence it worked. If you can, include the moment someone noticed the improvement, or a concrete outcome. It closes the loop and proves the change was real, not just intended.
Choosing your example
Look for genuine feedback that landed, a manager, a tutor, a colleague, a coach telling you something about how you worked or came across that you needed to hear. The best ones touch a blind spot: a habit you did not know you had. Then pair it with a specific behavioural change and, ideally, proof it stuck. The competency framework applies whatever the setting.
The hardest part of this answer to control is tone. Even with a good story, a trace of lingering resentment about the feedback can leak into your voice, and interviewers hear it, because it undermines the whole "I'm coachable" message. Say it aloud and listen for whether you sound genuinely at peace with the criticism or still quietly arguing with it. You can practise it and get feedback on how it comes across, which is the one thing you cannot judge from the inside.