5 exercises on receiving feedback phrases. Choose the most natural and professional option.
0 / 5 completed
1 / 5
A reviewer finds a null check you missed in your PR. How do you acknowledge it most professionally?
Option B is the professional response. It thanks the reviewer, confirms they're right ('you're right'), identifies the specific issue ('null check'), and commits to an action ('fixing now'). 'Oh no, sorry' (A) is emotional without being informative. 'OK I'll fix it' (C) acknowledges the fix but skips any confirmation that you understood the issue. 'I didn't see that, thanks' (D) is polite but passive — it doesn't confirm understanding. A strong acknowledgement does three things: validates the finding, shows you understood exactly what was wrong, and states the next action clearly.
2 / 5
A reviewer left a comment suggesting a different pattern, but you believe your approach is correct for good reasons. How do you disagree gracefully?
Option D is the model response. It acknowledges the reviewer's perspective ('I see your point'), explains the reasoning behind the choice (alignment with the auth module — a concrete technical reference), and invites further discussion without being defensive ('happy to discuss if you feel strongly'). 'I disagree' (A) is blunt without reasoning. 'That's not right' (B) is confrontational and dismissive. 'Actually, I think my approach is better' (C) is the most common defensive reaction — 'actually' signals you're not listening. When you disagree, always cite a specific technical reason and keep the door open for dialogue.
3 / 5
A reviewer used the word 'over-engineered' but you're not sure what specifically they mean. How do you ask for clarification?
Option A is the professional clarification request. It quotes the specific term ('over-engineered'), asks an open question ('say more about'), and explains why you're asking ('I want to make sure I address the right thing') — showing good faith rather than defensiveness. 'What do you mean?' (B) can sound curt or irritated depending on context. 'I don't understand your comment' (C) is passive and could imply the comment was unclear rather than that you want more detail. 'Please explain your review' (D) sounds like a demand. Good clarification requests always quote the exact phrase you're uncertain about and explain your purpose.
4 / 5
There's a valid refactoring suggestion in a PR review but it's too large to include in this PR. What do you say?
Option C is the professional response. It acknowledges the constraint ('can't address this in the current PR'), commits to a concrete action ('create a follow-up ticket'), and creates accountability by linking it to the PR. 'I'll do it later' (A) is vague and easy to forget. 'I'll get to it eventually' (B) is even vaguer and signals low priority. 'This isn't in scope for this PR' (D) is a boundary statement without any commitment to future action. When you defer feedback, always: acknowledge it's valid, create a ticket, and link it so the reviewer knows it won't be lost.
5 / 5
The review was especially thorough and the error handling comments were genuinely useful. How do you thank the reviewer in a way that acknowledges the value?
Option B is a meaningful thank-you. It names what made the review valuable ('thorough review') and specifies the most useful part ('comments on the error handling'). This signals you actually read and engaged with the feedback — not just acknowledged it. 'Thanks' (A) is fine but generic. 'Thank you for your time' (C) is polite but transactional — it focuses on the effort, not the content. 'Good feedback, thanks' (D) is slightly condescending — 'good feedback' positions you as the judge of the reviewer's work. The best thank-yous are specific: name what you found most valuable and why.