Giving and Receiving Feedback Questions
Exchanging feedback constructively in both directions. Covers delivering specific, actionable, and respectful critique to peers, juniors, senior colleagues, cross-functional partners and direct reports, including written review comments on code, documents and analyses that separate must-fix from minor points; receiving feedback and criticism without defensiveness, asking for clarification, pushing back with reasons, and closing the loop afterwards; choosing the channel and setting (live or written, public or private) and adapting to cultural norms; handling defensive reactions; and building feedback loops and habits on a team. Assesses the ability to help others improve without damaging the relationship. Excludes the candidate's own coachability and growth after being given feedback, stories of the candidate's own mistakes, sustained mentoring and development plans, resolving disputes between parties, design-critique craft, and code-review policy and process standards.
One of your reports gets defensive whenever you give them feedback. How would you restructure the conversation so it lands, and what would you try if the pattern continues?
Sample Answer
Direct answer
(Here "reports" means your direct reports: the people who report to you, not status reports.) I would change the format of the conversation, not just the wording: ask for their view first, tie the feedback to one observable event, give them time to react, and agree one concrete next step. If defensiveness continues, I would name the pattern privately, ask what format helps them, try written feedback first, and check whether the cause is trust, workload or my own delivery. Defensiveness is information about how the feedback is landing, not a reason to stop giving it.
Why people get defensive
Feedback can feel like a threat to someone's standing, can arrive by surprise, can sound like a verdict on who they are instead of what they did, or can echo a bad past experience. Understanding which one applies tells me what to change.
Restructure the conversation
- Warn and ask permission. "I have some feedback on Tuesday's design review. Is now a good time?" Surprise raises defenses.
- Start with their self-assessment. "How do you think the review went?" People are often harder on themselves than I would be, and the conversation starts from their view.
- Describe one event, not a trait. Use SBI (Situation, Behavior, Impact, a model from the Center for Creative Leadership): "In Tuesday's review (S), you answered the security question by saying the risk was overblown (B), and two reviewers stopped raising concerns afterwards (I)."
- Pause and listen. If they push back, say back what I heard ("you felt the question came late") before adding anything. Separate the facts they dispute from the interpretation.
- End with a short agreed list. A few concrete actions, each with a named owner (what they will try, what I will change), a date to check back, and the question "What would help?" Keep it to what can realistically be done before the next conversation; in the example below that is one action for them, two for me and a Thursday check-in.
If the pattern continues
- Name it kindly in private. "I notice that when I raise feedback we often end up debating it. Can we talk about what would work better?"
- Offer other channels. Written feedback beforehand, so they can digest it alone; smaller, more frequent feedback so each piece has less weight.
- Check the cause. Stress, fear for their job, a past manager who punished mistakes, or something in my tone. Ask rather than assume.
- State the expectation. Receiving feedback is part of the role; I will adapt the delivery, not drop the content.
- If defensiveness turns into hostility or the work suffers, involve HR (the human resources team) and treat it as a conduct and performance matter. Before that, write down dates, what was said in neutral words, the feedback given, and the support I offered, so the record shows a fair process.
Worked example
Me: "Tuesday's design review: could we talk for ten minutes? First, how did you think it went?"
Report: "Fine. They were just nitpicking."
Me: "I hear that it felt like nitpicking. One moment I want to look at: when the security question came up, the answer was that the risk was overblown, and the reviewers went quiet. What happened for you there?"
Report: "Honestly, I felt ambushed. I had no time to think."
Me: "Thank you for telling me. From now on I will send questions a day ahead. And when a security question comes up live, would you try saying 'I'll verify and follow up'?"
Report: "Yes, I can do that."
Me: "Good. What else would help you in those moments?"
Report: "A heads-up on who will be in the room."
Me: "I can do that. Let's check in for ten minutes on Thursday, after the next review, to see how it felt."
Trade-offs and pitfalls
- Softening the message until it disappears. The content stays; the delivery adapts.
- Arguing facts in the moment. A pause plus a written summary usually lands better than winning the exchange.
- Treating one tense reaction as a pattern. Look for repetition across several conversations first.
What is the Situation-Behavior-Impact model, and how would you use it to give corrective feedback to a teammate who keeps missing sprint commitments?
Sample Answer
Direct answer
Situation-Behavior-Impact (SBI) is a three-part feedback structure from the Center for Creative Leadership. You name the Situation (when and where, so it is specific), the Behavior (what you directly saw or heard, with no guesses about motive), and the Impact (what it caused for you, the team or the product). Because it describes facts and effects instead of labeling the person, it is harder to argue with and easier to act on.
How to use it for a teammate who keeps missing sprint commitments
A sprint is a fixed work cycle (often two weeks) and a commitment is the set of tasks the team agreed to finish in it. Steps:
- Check the facts first. Pull the last few sprints so you describe a pattern, not one bad week.
- Ask privately, early, and say the purpose. "I'd like to talk about sprint delivery. I think it will help both of us."
- Deliver S, B, I in two or three sentences, then stop and listen.
- Ask for their view. CCL's extended version adds a fourth step, the person's intent, which turns it into a conversation. They may be overloaded, blocked, or under-estimating.
- Agree one concrete next step and a check-in date.
Worked example (illustrative numbers)
- Situation: "In our last three sprint reviews..."
- Behavior: "...you committed to five stories (a story is one small piece of work, written from the user's point of view) each time and finished three, so two were carried over each sprint (six carried-over stories in total)."
- Impact: "QA (quality assurance, the people who test changes) could not start testing the carried-over stories, and Priya's work that depends on yours kept slipping. It also makes our forecast (our estimate of what we will deliver and when) to the product manager unreliable."
- Ask: "What's getting in the way from your side?"
- Next step: "Next planning, let's commit to four and split any story bigger than two days. We'll look again at the next sprint review."
Weak versions to avoid
| Weak | Why it fails |
|---|---|
| "You're unreliable." | A label about character; invites defense. |
| "You always miss sprints." | "Always" is easy to disprove and ends the talk. |
| "You obviously don't care." | Guesses a motive you cannot see. |
Pitfalls
- Skipping the listening step turns SBI into a verdict.
- Impact must be real and specific; vague impact ("it's bad for the team") adds nothing.
- Use it for behavior the person can change; if the cause is unrealistic planning by the whole team, the fix is in planning, not in feedback.
Tell me about a time you gave a peer critical feedback that risked damaging the working relationship. How did you prepare, what did you actually say, and where did the relationship stand afterwards?
Sample Answer
Direct answer
I'll tell this as a story (illustrative skeleton). A peer on my team kept merging changes (adding code to the shared codebase so it goes live) late on Friday afternoons without telling the on-call engineer (the person on the rota who responds to alerts outside working hours), so the weekend pager (the automatic alert that wakes that person) took the hit. We were friendly, so raising it risked the relationship. I prepared the facts, asked permission to talk, said specific words, and agreed a small change we could both check.
Situation and stakes
In three of the last five weekends, a page was traced to a Friday-evening change from this peer. Nobody had complained to him. I was the person on call, so I had standing to speak. The risk: he was senior in tenure, proud of his speed, and likely to hear "you are careless."
Preparation (what I did)
- Listed the three incidents (one per affected weekend) with dates and what each page cost (hours of weekend time), separating what happened from my theory of why.
- Checked my own part: did the team have a "no Friday deploys" norm? No, so he had broken no rule. That changed my goal from "stop doing this" to "agree a norm together."
- Chose a private one-to-one meeting on a Tuesday, not a Friday or in a public channel, and sent a neutral invite: "Want to talk about how we handle late changes and on-call?"
What I actually said
"When changes land after 4pm Friday without a heads-up, on-call finds out from the pager. That happened on three of the last five weekends, including the cache change on the 14th. I'm not saying the changes were wrong. I'm saying I can't be ready for something I don't know about. How do you see it?"
He bristled for a minute ("they were small changes"), so I agreed they were small and asked what would make telling on-call easy. He suggested a one-line note in the on-call channel before merging.
Where the relationship stood afterwards
Slightly awkward for about a week, then normal. We wrote the "tell on-call before a late merge" line into the team's runbook (the shared how-to document). Two weeks later I told him the weekend pages from changes had stopped and thanked him. The follow-up check was simple: count pages tied to late changes each month.
What made it work
- It built psychological safety (people feel safe to speak and be corrected without punishment) by keeping it private, specific, and about the effect on on-call.
- I owned my uncertainty and invited his view.
Pitfalls
Do not deliver it by chat while angry, do not use "always," and do not skip the follow-up; feedback without a check is just a one-time complaint.
You work on a globally distributed team where cultural norms differ on how direct feedback should be. How do you adapt how you give feedback, and how do you check your assumptions?
Sample Answer
Direct answer
I treat what I know about cultural norms as a hypothesis about a person, not a fact about them. I ask people how they like to receive feedback, write feedback so the content is clear regardless of tone, avoid idioms and sarcasm, and check what was understood by asking for the takeaway in their own words. My assumptions get tested by watching what actually happens, not by country.
How I adapt
- Ask early, one to one: "How do you prefer to get feedback: in writing first, live, in private? Anything I should know about how you read direct comments?" and offer my own style: "I tend to be direct. Tell me if that is too blunt."
- Use a neutral structure. SBI (Situation, Behavior, Impact) states a specific moment, what was done, and the effect. It is easy to translate and avoids loaded labels.
- Use plain language in writing. For non-native speakers, avoid idioms ("this is a bit off the mark"). Do not rely on hedges or silence to carry the message.
- Make the ask explicit. Instead of "maybe consider...", say "I would like this changed before merge" or "this is optional".
- Choose the channel on purpose. Some people prefer written first, then discussion; some find public feedback more costly than others do.
Checking assumptions
- Ask: "What are you taking away from this, and what will you change?" Silence or "yes" may mean "I heard you", not "I agree".
- Notice patterns: does someone never raise disagreement in meetings but write a careful note afterward? Give them that route.
- Ask a trusted colleague from that region how a comment would read, and ask the recipient directly afterward: "Was that clear? Too direct?"
- Erin Meyer's The Culture Map includes an "evaluating" scale of direct versus indirect negative feedback across cultures. It is a useful prompt for questions, but individuals vary widely within any country.
Worked example
Two reviewers on one pull request (PR) have the same concern about a missing retry. A direct writer says: "This will fail under load. Add a retry." An indirect writer says: "Perhaps we might think about whether retries are needed?" A teammate used to indirect feedback may read the first as hostile, and a teammate used to direct feedback may miss the second as a requirement. My version: "Observation: this call has no retry, and a timeout in staging last week dropped orders. I'd like a retry added before merge. Does that work for you, or do you see a reason not to?" It is clear, specific and invites a reply.
Pitfalls
- Stereotyping by nationality rather than asking.
- Softening until the message is lost; kind and clear are compatible.
- Assuming a direct culture wants harsh delivery.
A peer habitually uses vague language in stakeholder updates (for example, 'should be done soon'). Give me a short script for telling them, including a concrete before and after rewrite.
Sample Answer
Direct answer
I would talk to them privately, use SBI (Situation, Behavior, Impact: one concrete moment, what they actually wrote, and what it caused), then show a rewrite and offer to help. Vague wording is usually a habit or a way to avoid being wrong, so I ask a question before I prescribe.
Short script (about a minute)
- Ask permission and set the tone: "Can I give you some feedback on your status updates? I think it will make you look more reliable, and I want your read on it."
- Situation and behavior: "In Tuesday's update to the launch group you wrote 'should be done soon'."
- Impact (a fact, not a guess): "Dana asked what soon meant, then scheduled an extra sync to find out, and the partner team could not plan around it."
- Ask: "What makes it hard to commit to a date in those updates?" Listen. Often the answer is fear of being held to a date, and that deserves a real response.
- Offer the pattern: "Try three parts: current state, a date or range with your confidence, and what could move it."
- Close: "Want to draft the next one together, and I'll read it before it goes out?"
Before and after
- Before: "Migration should be done soon, just a few things left."
- After: "Migration status: 4 of 6 tables are moved. The two remaining tables are the largest. Expected finish: Thursday noon, medium confidence. Risk: backfill speed on the big tables. I will post Wednesday end of day with a firm date or flag a slip."
The after version gives a state (4 of 6), a date (Thursday noon), a confidence (medium), a risk, and the next check-in. The reader can plan, and the writer is protected because the uncertainty is stated rather than hidden.
Trade-offs and pitfalls
- A date they cannot hit is worse than a range. Give a range such as "Wednesday to Friday" when the work is truly uncertain, and say why.
- Do not say "you are always vague"; use the single example. One example is observable, a label is an argument.
- If they push back that precision invites blame, agree that status updates should be safe for honest slips, and say you will back them when a flagged risk happens.
Unlock Full Question Bank
Get access to all 19 Giving and Receiving Feedback interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.