5 exercises — respond professionally to critique: acknowledge it, ask for clarification, disagree politely, and commit to changes without getting defensive.
Key phrases for receiving feedback
"Thanks for catching that" — acknowledge useful feedback
"Could you clarify what you mean by...?" — ask rather than guess
"Good point, I'll update it" — commit clearly when you agree
"I see your point, though I chose X because..." — disagree with reasoning
"Let's discuss this on a call" — move complex disagreements off the thread
0 / 5 completed
1 / 5
A reviewer points out a real bug you missed. What is the most professional response?
Acknowledging valid feedback openly ("Good catch — thanks") shows you value quality over ego, and committing to a concrete action ("I'll fix it and add a test") closes the loop. This builds trust with reviewers.
Minimising the issue ("tiny edge case"), making excuses ("going to get to that"), or deflecting blame ("not my fault") all read as defensive. Receiving feedback gracefully starts with genuinely thanking people for finding problems — every bug caught in review is one that did not reach production.
2 / 5
A comment is unclear and you are not sure what the reviewer wants. What should you do?
When feedback is ambiguous, asking a specific clarifying question ("Do you want me to extract this or rename it?") is far better than guessing. It shows you are engaged and prevents wasted rework on a misunderstanding.
Guessing risks doing the wrong thing; ignoring or silently resolving the thread dismisses the reviewer; and "this makes no sense" attacks rather than seeks understanding. Offering two interpretations in your question often gets you a fast, precise answer.
3 / 5
You disagree with a suggestion and have a good reason. How do you push back professionally?
Professional disagreement acknowledges the other view, explains your reasoning, and leaves room to continue: "I see your point, but... because it avoids an extra DB call — happy to discuss." This treats review as a technical conversation between equals.
"No" and "You're wrong" are dismissive and escalate tension. Silently complying while resentful ("Fine, I'll change it") avoids the conversation but breeds frustration and may implement a worse solution. Disagreeing well — with respect and reasons — is a core senior-engineering skill.
4 / 5
A review thread has gone back and forth five times without resolution. What is the best move?
Long, circular text threads are a classic sign that the medium is the problem. Moving to a synchronous call ("shall we hop on a quick call?") resolves nuance far faster than more typing, where tone is easily lost and positions harden.
Endless replying wastes time and escalates frustration; merging over an unresolved objection undermines review; immediately escalating to a manager skips the simpler step of just talking it through directly. Recognising when to switch from async to sync is a mark of good communication judgement.
5 / 5
You realise mid-discussion that the reviewer is right and your original approach was flawed. How do you respond?
Openly conceding when you have been convinced ("You're right — I hadn't considered the concurrency case... Thanks for pushing on this") is a strength, not a weakness. It shows intellectual honesty and rewards the reviewer for caring enough to push.
Pretending you always agreed, silently changing it, or defending a flawed approach to "save face" all damage trust and learning. The best engineers update their views readily when shown a better argument — and thank the person who provided it. That culture makes everyone better.