Learn to write clear, structured hire/no-hire feedback for candidate evaluations.
0 / 12 completed
1 / 12
What is a 'hire/no-hire recommendation' in interview vocabulary?
A hire/no-hire recommendation is each interviewer's evidence-based conclusion — not just a vote but a written narrative supported by specific observations from the interview. The committee weighs all recommendations.
2 / 12
What should interviewer feedback focus on?
Good feedback is specific and evidence-based: 'The candidate was unable to explain why O(n log n) is typical for merge sort when asked' — not 'seemed weak on algorithms'. Evidence reduces bias and enables calibration.
3 / 12
What is 'strong hire' vs 'hire' in feedback vocabulary?
Strong Hire typically means the candidate significantly exceeds the bar for the target level — could potentially be hired at a higher level. Hire means they meet the bar. The distinction helps committees weight signals in close cases.
4 / 12
What is 'leveling feedback' in a post-interview recommendation?
Leveling feedback addresses which level the candidate's performance best matches — e.g., 'The candidate demonstrated strong technical fundamentals consistent with L4; I did not see evidence of L5 scope or cross-team thinking.'
5 / 12
What should you NOT write in candidate feedback?
Feedback must focus on job-relevant observations. Mentioning demographic information, appearance, accent, family status, or subjective personality judgements is discriminatory, legally risky, and not relevant to the hiring decision.
6 / 12
Sarah, a senior engineer, is reviewing John's pull request for the new user authentication module. John writes in the PR description: 'Fixed a bug where users couldn't log in.' Sarah wants to provide constructive feedback. Which of the following phrases best reflects her intention?
The best response encourages John to provide more detail and demonstrate a proactive approach to problem-solving. Simply stating 'Great job' doesn't offer actionable feedback or assess the completeness of the fix. Options B and C prompt for deeper investigation and future prevention strategies – crucial elements in effective candidate feedback.
7 / 12
Mark, a product manager, needs to provide feedback on a junior developer's performance during a recent sprint. He wants to highlight areas for improvement while also acknowledging positive contributions. Which of the following Slack messages is most appropriate?
This response offers a balanced approach by acknowledging the positive aspect (API integration) while directly addressing an area for improvement (code design and scalability). It's specific and invites further discussion – a key element of constructive feedback. Options A and C are too vague, and option B is overly critical without context.
8 / 12
Alex, a team lead, is drafting feedback on a junior developer's recent pull request for the API integration. The PR included a significant refactoring of a core data processing function. Alex wants to emphasize both the technical skill demonstrated and potential areas where further training could be beneficial. Which phrase best captures this nuanced approach?
This question tests understanding of providing balanced feedback. Option A is overly enthusiastic and lacks constructive criticism. Option B is too negative and doesn't acknowledge positive aspects. Option C offers specific areas for improvement alongside recognizing skill, and option D is too general. Alex's goal is to be both encouraging and informative.
9 / 12
Maria, a senior developer, receives a Slack message from a junior colleague asking for clarification on the 'technical debt' discussed during yesterday's standup. Which of the following responses best explains this concept in a way that is both helpful and avoids jargon?
This assesses the ability to explain complex concepts simply. Option A is misleading and uses jargon. Option B provides an accurate definition without excessive technical terms. Option C dismisses the issue and avoids explanation. Finally, option D misinterprets 'technical debt' as a performance metric.
10 / 12
David, a code reviewer, notices several instances of duplicated logic within a module. He wants to provide feedback that encourages the developer to refactor for increased maintainability without appearing overly critical. Which statement would be most effective?
This focuses on phrasing. Option A is confrontational and unhelpful. Option B offers a constructive suggestion framed positively, focusing on the benefit (maintainability). Option C ignores the feedback entirely. Finally, option D shifts the focus to a potentially irrelevant concern – performance – when the primary issue is redundancy.
11 / 12
Emily, a product manager, needs to provide feedback on a developer's contribution during a sprint retrospective. The developer consistently delivered code that met the sprint goals but frequently missed deadlines. Which of the following phrases best balances acknowledging achievement with addressing performance issues?
This question tests ability to handle a common performance-related feedback scenario. Option A is blunt and potentially demoralizing. Option B acknowledges achievement while directly addressing the time management issue with a focus on solutions. Options C and D are overly celebratory or confrontational.
12 / 12
Ben, a senior engineer, is writing a feedback note for a developer who consistently produces high-quality code. Which of the following statements would be MOST appropriate to include?
This assesses understanding of positive feedback. Option A introduces criticism where none is needed. Option B directly praises the developer's quality work and highlights specific strengths (testing and detail). Options C and D offer unsolicited advice or critique.
What does this Technical Interviewing exercise cover?
This exercise, "Writing Candidate Interview Feedback — Vocabulary", tests your understanding of technical interviewing vocabulary and phrasing through 12 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 12 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Technical Interviewing exercise for?
It's designed for IT professionals and learners who want to sound natural discussing technical interviewing topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Technical Interviewing exercises?
Browse the full Technical Interviewing exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.