Practise writing candidate rejection emails, giving constructive feedback, and professionally closing the loop after interviews and take-home assessments.
0 / 18 completed
1 / 18
Which candidate rejection email opening is most professional and appropriately timely?
Option B is specific (names the role), appreciative (thanks their time), and direct (states the decision clearly) without being cold.
Rejection emails should be sent promptly — leaving candidates waiting for weeks damages employer brand more than the rejection itself. Avoid vague hedging like "due to a variety of factors" (option C), which sounds evasive, and avoid the empty promise "we'll keep your resume on file" (option D) unless you genuinely intend to follow up.
Standard structure: thank the candidate → state the decision clearly → (optionally) offer feedback → close professionally.
2 / 18
A rejected candidate emails asking for feedback on why they weren't selected. Legal/HR policy in your company restricts detailed feedback. What is the best response?
Option C balances two real constraints: legal/policy limits on detailed feedback (common in the US to reduce discrimination-claim exposure) and the candidate's legitimate desire for closure.
Vocabulary for this situation: • "Due to company policy, we're unable to share detailed interview feedback" — standard disclaimer used by many large employers • general, constructive takeaway — a high-level theme, not interviewer-by-interviewer detail • Never share raw interviewer notes, scores, or comparisons to other candidates — this exposes the company to legal risk and can be unfair to the interviewers.
Ignoring the request (option A) is worse for employer brand than a brief, policy-compliant reply.
3 / 18
Rewrite this rejection feedback line to be constructive and specific rather than vague:
"You didn't do well enough in the interviews."
Option B follows the constructive-feedback pattern: acknowledge a genuine strength → name the specific gap → tie it to the specific role/level (not the candidate as a person).
Pattern: "We were impressed by [strength], but felt there was a gap in [specific area] for this particular role."
Avoid: blunt judgments ("you failed", "didn't do well enough") that give no actionable information and can feel personal rather than role-specific. Constructive feedback describes the *fit* between the candidate and this role/level — not a verdict on the candidate's overall ability.
4 / 18
What is "ghosting" in the hiring context, and why should recruiters avoid it?
Ghosting — leaving a candidate without any closure after interviews, sometimes for weeks or permanently. It is one of the most common candidate-experience complaints and directly damages employer brand (candidates share these experiences publicly, e.g. on Glassdoor).
"Closing the loop" is the opposite behavior: sending a timely, clear message — even a short one — so the candidate knows where they stand. "We are closing the loop on your application" is standard professional phrasing for a final rejection after a candidate has invested significant time (e.g. take-home projects, onsite interviews).
Rule of thumb: anyone who completed a live interview or paid assessment deserves a personal, timely closing message — not silence.
5 / 18
Which sentence correctly and professionally explains a rejection after a take-home technical assessment?
Option B acknowledges the effort ("thank you for completing"), gives a specific, defensible reason tied to the evaluation rubric (test coverage, edge case handling), and states the decision clearly.
Because take-home assessments require real candidate time investment, feedback expectations are higher than for a quick phone screen — candidates reasonably expect at least a brief, specific explanation.
Useful vocabulary: "functional but…", "met the baseline but fell short on…", "we've decided not to move forward at this time" (softer than "reject"), "this level" (frames feedback relative to the specific seniority bar, not as an absolute judgment).
6 / 18
John commented on the PR: 'This code is messy and hard to read. Needs serious refactoring.'
Maria, the original author, replies with:
'Thanks for the feedback. I'm still learning, but I appreciate you pointing this out.'
This scenario highlights the importance of responding to code review comments constructively. Option 1 acknowledges the feedback without defensiveness, offering support for Maria's learning process – a key element of fostering collaboration. Options A and B are overly critical or unhelpful, while option C is passive and doesn't address the issue raised. A good response demonstrates willingness to improve, not resistance.
7 / 18
Ben's comment during the code review highlights significant concerns about Alex's PR. Which of the following responses from Alex is MOST appropriate in replying to Ben?
Alex:
'Okay, thanks for the review!'
The key here is acknowledging feedback and demonstrating willingness to improve. Option 3 ('Okay, thanks for the review!') is a polite but ultimately unhelpful response that doesn't show engagement with Ben's concerns. Options A & B are too vague and don't indicate any action. Option C is acceptable as a basic acknowledgment, but failing to address the issues presented by Ben demonstrates poor communication skills and a lack of commitment to quality. While asking for elaboration (option D) could be appropriate later, it's not the immediate response needed in this scenario.
8 / 18
John commented on the PR: 'This code is messy and hard to read. Needs serious refactoring.'
Maria, the original author, replies with:
'Thanks for the feedback. I'm still learning, but I appreciate you pointing this out.'
This scenario highlights the importance of responding to code review comments constructively. Option 1 acknowledges the feedback without defensiveness, offering support for Maria's learning process – a key element of fostering collaboration. Options A and B are overly critical or unhelpful, while option C is passive and doesn't address the issue raised. A good response demonstrates willingness to improve, not resistance.
9 / 18
Ben's comment during the code review highlights significant concerns about Alex's PR. Which of the following responses from Alex is MOST appropriate in replying to Ben?
Alex:
'Okay, thanks for the review!'
The key here is acknowledging feedback and demonstrating willingness to improve. Option 3 ('Okay, thanks for the review!') is a polite but ultimately unhelpful response that doesn't show engagement with Ben's concerns. Options A & B are too vague and don't indicate any action. Option C is acceptable as a basic acknowledgment, but failing to address the issues presented by Ben demonstrates poor communication skills and a lack of commitment to quality. While asking for elaboration (option D) could be appropriate later, it's not the immediate response needed in this scenario.
10 / 18
John commented on the PR: 'This code is messy and hard to read. Needs serious refactoring.'
Maria, the original author, replies with:
'Thanks for the feedback. I'm still learning, but I appreciate you pointing this out.'
This scenario highlights the importance of responding to code review comments constructively. Option 1 acknowledges the feedback without defensiveness, offering support for Maria's learning process – a key element of fostering collaboration. Options A and B are overly critical or unhelpful, while option C is passive and doesn't address the issue raised. A good response demonstrates willingness to improve, not resistance.
11 / 18
Ben's comment during the code review highlights significant concerns about Alex's PR. Which of the following responses from Alex is MOST appropriate in replying to Ben?
Alex:
'Okay, thanks for the review!'
The key here is acknowledging feedback and demonstrating willingness to improve. Option 3 ('Okay, thanks for the review!') is a polite but ultimately unhelpful response that doesn't show engagement with Ben's concerns. Options A & B are too vague and don't indicate any action. Option C is acceptable as a basic acknowledgment, but failing to address the issues presented by Ben demonstrates poor communication skills and a lack of commitment to quality. While asking for elaboration (option D) could be appropriate later, it's not the immediate response needed in this scenario.
12 / 18
John commented on the PR: 'This code is messy and hard to read. Needs serious refactoring.'
Maria, the original author, replies with:
'Thanks for the feedback. I'm still learning, but I appreciate you pointing this out.'
This scenario highlights the importance of responding to code review comments constructively. Option 1 acknowledges the feedback without defensiveness, offering support for Maria's learning process – a key element of fostering collaboration. Options A and B are overly critical or unhelpful, while option C is passive and doesn't address the issue raised. A good response demonstrates willingness to improve, not resistance.
13 / 18
Ben's comment during the code review highlights significant concerns about Alex's PR. Which of the following responses from Alex is MOST appropriate in replying to Ben?
Alex:
'Okay, thanks for the review!'
The key here is acknowledging feedback and demonstrating willingness to improve. Option 3 ('Okay, thanks for the review!') is a polite but ultimately unhelpful response that doesn't show engagement with Ben's concerns. Options A & B are too vague and don't indicate any action. Option C is acceptable as a basic acknowledgment, but failing to address the issues presented by Ben demonstrates poor communication skills and a lack of commitment to quality. While asking for elaboration (option D) could be appropriate later, it's not the immediate response needed in this scenario.
14 / 18
Sarah received the following Slack message from a teammate after submitting a bug fix:
`@David: 'This is… interesting. I'm not sure I follow your logic here.'`
What's the MOST professional and constructive response Sarah should send?
The best response demonstrates openness to feedback and seeks clarification. Option A is dismissive and avoids engagement. Option B directly requests specific details, prompting a productive discussion. Options C and D are unprofessional and don't address the concern.
15 / 18
During a daily standup, team lead Emily says: 'Mark, your code isn't fully documented. It makes it difficult for others to understand and maintain.'
What is the MOST appropriate way Mark should respond *at this moment*?
Mark's priority is to acknowledge the feedback and commit to action. Option A deflects responsibility. Option B shows proactive commitment. Options C and D are evasive or dismissive, failing to address the core issue of incomplete documentation.
16 / 18
You've been asked to write a PR description for a change that improves API performance. The code was tested against a specific benchmark and achieved a 20% improvement. Which of the following descriptions is BEST?
A good PR description should be specific and quantify the impact of the change. Option A is vague and uninformative. Option B provides concrete details about the benchmark results which demonstrates value. Options C and D are overly simplistic and lack technical context.
17 / 18
During a code review, David points out a potential security vulnerability in Alex's code. Alex replies: 'I didn't know about that.'
What is the MOST professional and helpful response Alex should give?
Alex's response needs to acknowledge the feedback and demonstrate a commitment to addressing the vulnerability. Option A is dismissive. Option B minimizes the issue. Option C shows gratitude for the observation and a proactive intention to fix it – crucial in security contexts. Option D is unprofessional and negligent.
18 / 18
You've received an email from a hiring manager rejecting your application for a Senior Developer role. The email reads:
`Dear [Your Name], Thank you for your time and interest in [Company Name]. After careful consideration of all candidates, we have decided to move forward with other applicants whose qualifications more closely align with the needs of this position.`
What is the MOST appropriate way to respond?
A polite and gracious response acknowledges the rejection while maintaining a professional tone. Option A expresses gratitude without demanding further information. Options B is terse and unhelpful. Option C directly requests feedback, which may not be provided or could lead to unproductive debate – it's generally best to accept the decision gracefully. Option D can appear overly eager.
What does the "Rejection & Feedback Language" exercise cover?
Write timely, respectful candidate rejection emails and give constructive feedback in English — including how to close the loop and respond to feedback requests professionally.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Rejection & Feedback Language"?
This exercise has 18 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Developer Hiring exercises?
Browse the full Developer Hiring hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.