Receiving Feedback and Criticism Gracefully

When an interviewer asks how you handle feedback and criticism, they’re checking whether you get defensive and hurt, or treat it as growth. For a developer this matters enormously — code reviews, retrospectives, and appraisals are wall-to-wall feedback. This page teaches the four-step habit that signals a growth mindset: listen, understand, act, and thank — and the key reframe that criticism is about your work, not about you.

The golden rule is to treat feedback as free coaching. Listen fully first (don’t interrupt, don’t defend mid-sentence), clarify so you know exactly what to improve, then act on it — and let your next piece of work prove it.

The core answer

“I don’t take feedback as an ego hit — my view is that the other person is saving me time by pointing out what I couldn’t see myself. So I listen fully first, without defending in the middle. If something isn’t clear, I ask for a specific example so I know exactly what to improve. Then I actually work on it, and the next piece of work confirms it for them. Even negative feedback is free coaching for me.”

Scenario: harsh, public feedback

Manager: “Suppose you’re told in front of the team that your work wasn’t good. How would you feel, and what would you do?”

You: “My first reaction would sting — that’s natural. But I wouldn’t react in the moment; I’d stay calm and hear the point, because if it’s valid, defending myself in front of the team only makes me look worse. I’d note the feedback. If I felt it shouldn’t have been said in public, I’d mention it politely later, one-on-one: ‘I agree with the feedback; next time, if it can be in private, I’ll absorb it better.’ But I’d keep the focus on the content — if the point is right, it’s better to fix it than to get stuck on how it was delivered.”

Follow-up: “What if you think the feedback is wrong?”

Manager: “What if you feel the feedback itself is wrong — that you did the right thing?”

You: “Then I wouldn’t immediately say ‘no, you’re wrong.’ First I’d accept that they may have seen something I couldn’t. I’d clarify — ‘exactly which part do you mean, could you give an example?’ Often that reveals either a misunderstanding or that they were right after all. If I still believe the feedback is factually wrong, I’d calmly present my side with data — ‘I did it this way because of this reason’ — not as an argument, but to explain. In the end, if it’s a senior’s preference, I’ll go along with it, but only after making my understanding clear.”

This mirrors the disagree-and-commit approach: make your case with data, then respect the final call.

Follow-up: “An example where feedback improved you”

Manager: “Tell me about real feedback you took that made you better.”

You: “A senior once said in my code review that my code worked fine, but my naming and comments weren’t clear, so it took others time to read. At first I thought ‘well, it works’ — but I took it seriously. I started writing meaningful names and a few comments, and I followed a style guide. A few weeks later that same senior noticed and said my code had become easy to review. It made me realise code shouldn’t just run, it should be readable — and that’s been a strong habit of mine ever since.”

Follow-up: “How do you give feedback to others?”

Manager: “If you had to give negative feedback to a junior or peer, how would you do it?”

You: “In private, never in public. And I focus on the work, not the person — ‘this function is a bit complex, could we simplify it?’ rather than ‘you always write like this.’ I mention something good first so the person doesn’t get defensive, then the specific improvement, then a suggestion on how to do it. And I ask ‘what do you think?’ so it’s a conversation, not a lecture. The goal is to make the person better, not to put them down.”

Giving feedback well is closely tied to handling peer conflict calmly and privately.

Tips & mistakes to avoid

• ❌ Immediately defending or arguing against feedback.
• ❌ “I don’t like criticism” or “I take it personally.” → red flag.
• ❌ Speaking badly of the person who gave it (“they nitpick for no reason”).
• ✅ Listen → clarify → act → thank.
• ✅ Say the mindset out loud: “criticism of the work, not of me.”
• ✅ Show that you both take feedback and give it constructively.