5 exercises on receiving feedback phrases. Choose the most natural and professional option.
0 / 14 completed
1 / 14
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 / 14
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 / 14
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 / 14
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 / 14
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.
6 / 14
Liam from QA just posted a comment on your PR saying: 'I'm seeing inconsistent data when calling the getUserProfile() endpoint. It sometimes returns null, but other times it returns a full user object.' How do you respond to acknowledge his findings and offer to investigate?
The best response acknowledges the issue, expresses willingness to investigate, and thanks Liam for bringing it to your attention. Option A demonstrates proactive engagement and appreciation. Options B and C are dismissive or assume a problem without evidence, while option D shifts responsibility unnecessarily.
7 / 14
Sarah left this comment in your PR description: 'This implementation feels overly complex for simply retrieving user details. Consider a simpler approach.' You believe your current design is optimized for future scalability but want to address her concerns professionally. Which response is most appropriate?
Option 2 is the most constructive. It politely acknowledges her feedback while stating your reasoning and invites further discussion. Options A is defensive without explanation, B is confrontational and dismissive, and D shuts down communication.
8 / 14
David, the senior engineer, left this comment on your PR: 'The error handling here is weak. It doesn't handle potential network timeouts.' You understand his point but are confident in your current timeout implementation. How do you respond to respectfully offer an alternative perspective?
Asking for clarification (Option 3) is crucial when you disagree but want to understand the basis of the concern. It avoids a direct conflict and allows you to learn from David's experience. Options A and B are dismissive, while option D is too vague.
9 / 14
Maria left a detailed review of your code, including several helpful comments on error handling. She went above and beyond to ensure the code was robust. How do you express your gratitude in a way that acknowledges her effort?
Option 3 specifically acknowledges Maria's effort and highlights the positive impact of her detailed review. It's a sincere and appreciative response that shows you recognize the value of her contribution. The other options are generic and lack specific praise.
10 / 14
Alex from the team just posted this comment on your PR: 'I'm running into a 500 error when I try to deploy this. Can you take a look?' You suspect it might be related to the recent database migration. Which of the following responses is most professional and proactive?
This scenario requires immediate troubleshooting. Option 1 demonstrates a willingness to help and requests crucial information for diagnosis. Options 2 actively seeks details to understand the problem, while options 3 and 4 are dismissive and avoid taking responsibility. It's vital to gather data before assuming a solution.
11 / 14
During a standup meeting, Ben mentions that he's struggling with the API response from the 'User Service'. He says the documentation is unclear about handling potential rate limiting. How do you respond in a way that acknowledges his difficulty and offers support?
Ben's experience highlights a genuine communication gap. Option 1 is dismissive and unhelpful. Option 2 demonstrates empathy, offers collaboration, and suggests concrete steps to resolve the issue. Options 3 focuses on blame and option 4 ignores Ben's struggle entirely.
12 / 14
You've received this Slack message from a teammate: 'This feature is going to be a nightmare to maintain. The logic is a total mess!' You believe the code is well-structured and documented but want to understand their perspective without immediately defending your work. What's the best response?
The key here is constructive criticism. Option 1 immediately escalates the situation. Option 2 politely asks for specific details, allowing you to understand their concerns and potentially address them without a direct confrontation. Options 3 avoids the issue and option 4 is confrontational.
13 / 14
You've just received this comment on your PR from a reviewer: 'The JSON schema validation isn't comprehensive enough. It only checks for the presence of the `userId` field; it doesn't validate the data type or range.' You agree with the assessment but want to explain your reasoning briefly. What is the most effective response?
This demonstrates acknowledging the reviewer's valid point. Option 1 confirms understanding and acceptance. Option 2 explains the trade-off you made (which is acceptable to briefly mention), while options 3 deflects responsibility and option 4 denies the validity of the feedback.
14 / 14
A reviewer leaves this comment on your PR: 'This approach is overly complex. Can you simplify it?' You've spent considerable time optimizing the algorithm for performance but believe the current implementation achieves the required results efficiently. How do you respond to acknowledge their concern and offer a deeper discussion?
This highlights the importance of understanding different perspectives. Option 1 is defensive and dismissive. Option 2 invites a constructive dialogue by requesting an alternative solution and prompting a discussion about trade-offs (performance vs. simplicity). Options 3 is aggressive and option 4 lacks justification.
What will I practise in "Receiving Feedback Professionally: Developer Response Phrases"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 14 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 14 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasebook exercises?
See the Phrasebook hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.