When an interviewer asks you to describe a time you gave difficult feedback, the story they hope to hear has a particular shape: you noticed a problem, you raised it promptly and privately, you described the behaviour rather than judging the person, you listened, and something improved. The question is less about bluntness than about whether people can still work with you afterwards.
The right example depends on your role. A team leader, a peer and a junior employee giving feedback upwards face very different risks. This guide works through four scenarios, each with what the interviewer is checking, an illustrative answer and the trap to avoid.
A tool for describing what you said: SBI
Many candidates lose the interviewer in the middle of this story, at the moment of the conversation itself. A simple fix is to report what you said using the Situation-Behaviour-Impact (SBI) model from the Center for Creative Leadership (CCL):
- Situation: the specific setting. CCL’s example is “This morning at the 11 am team meeting”, not a vague “last week”.
- Behaviour: only what was observable, with no judgement. CCL contrasts “You interrupted me while I was telling the team about the monthly budget” with “You were rude.”
- Impact: the effect it had on you or others.
CCL also describes a fourth step, sometimes called SBII: asking about intent, with questions such as “What were you hoping to accomplish with that?”, then listening. CCL says this turns one-way feedback into a two-way conversation, and warns against assuming negative motives, such as deciding someone is lazy or doesn’t care.
You do not need to name the model in the interview. But if your story includes a sentence like “I told her that in the last two client calls, she had answered questions meant for the client’s technical lead, and that the client had mentioned it to me afterwards”, the interviewer hears precision, fairness and evidence.
Scenario 1: You managed someone whose performance had slipped
What the interviewer is checking: that you dealt with it early, looked for the cause, offered support, and kept a record. This mirrors what Acas, the UK’s workplace advisory service, recommends: employers should try to understand why there is a performance problem, take steps to help the employee improve before starting a formal procedure, and keep a record of conversations about performance.
“I was supervising four warehouse team members. One of my most experienced pickers had started making errors, about one wrong item in every few orders over two weeks, after months of near-perfect work. Customers were receiving wrong items and the returns team had flagged it.
“I asked to speak to him privately at the start of a shift, not at the end when he’d want to leave. I said that over the past two weeks, several orders he’d picked had had the wrong item, that it had caused returns, and that this was unusual for him. Then I asked whether anything had changed.
“He told me the new handheld scanners were hard for him to read, and he’d been guessing at some product codes rather than asking, because he didn’t want to look slow. I arranged for him to try a scanner with a larger display, and asked him to tell me if anything else was getting in the way. I made a short note of the conversation and what we’d agreed.
“His error rate went back to normal within a week. I also realised other people might have the same problem with the scanners, so I asked the whole team, and two more people swapped devices.”
The trap: telling the story as if the conversation was a warning. Unless it was a formal process, the interviewer wants to see support first. Also avoid any detail that might identify a colleague’s health or personal circumstances.
Scenario 2: A peer’s work was affecting yours
What the interviewer is checking: that you raised it with the person directly before going to a manager, that you stayed factual, and that you kept the working relationship.
“I was a junior designer working with a developer on a website project. Twice in one month, the build he shipped didn’t match the agreed designs, and I only found out when the client asked why their buttons had changed.
“I asked if we could talk over coffee. I said that on the last two releases, the client had seen changes to the design before I had, and that it had put me in an awkward position because I couldn’t explain them. Then I asked what had led to the changes. It turned out he’d made them for good accessibility reasons, but under deadline pressure, and he assumed I’d see the build before release.
“We agreed he’d tag me on any visual change in the release notes, and I’d review within a day so I wasn’t a bottleneck. On the next release, he flagged two changes and I agreed with both. Our manager later asked us to share the process with the rest of the team.”
The trap: going straight to the manager without mentioning it to the peer first. Unless it was a safety or misconduct issue, interviewers generally expect you to try the direct route first.
Scenario 3: You gave feedback upwards, to your manager
What the interviewer is checking: courage combined with respect. They are also checking whether you can disagree with a decision while still supporting it.
“In my second year as an accounts assistant, my manager started sending priority requests late on Thursday afternoons, with Friday deadlines. It happened four weeks in a row, and twice I worked late to finish.
“I waited for our regular one-to-one rather than raising it when I was frustrated. I said that the last four Thursday requests had arrived after 3 pm, that I’d stayed late twice to finish them, and that I was worried about making errors when rushed. I asked whether there was something upstream that caused the timing.
“She explained that the requests came from her own weekly meeting on Thursday afternoons. She hadn’t realised how often it was landing on me. We agreed she’d send me a short heads-up on Wednesday if she expected anything. Most weeks after that I had an extra day.”
The trap: making your former manager sound bad. The interviewer is imagining being your manager. Show that you assumed good intent and came with a suggestion.
Scenario 4: The other person wasn’t on your team at all
What the interviewer is checking: commercial judgement. Giving feedback to a supplier, client or senior specialist carries a different risk: you can’t rely on authority, and the relationship may be worth money.
“As a project coordinator, I managed a printing supplier who had delivered late on three event orders. Our events team wanted to switch suppliers immediately, but the supplier was cheaper than the alternatives and their quality was good.
“I set up a call with their account manager and shared the three order dates, the promised and actual delivery times, and the impact: on the last event, our staff had to hand out programmes an hour after doors opened. I asked what was going wrong on their side.
“They explained that our orders were arriving after their daily print cut-off, so they were being pushed to the next day’s run. We hadn’t known there was a cut-off. We agreed to submit orders by noon, and they agreed to confirm a delivery slot in writing for each order. Over the next quarter, every order arrived on time.”
The trap: presenting the story as “I told them off”. In external relationships, interviewers value candidates who solve the problem and keep a useful partner.
All four answers above are illustrative. Your own story will be stronger if it’s real, even if it is smaller.
What makes the difference across all four
| Weak answers | Strong answers |
|---|---|
| “I told him he was being lazy.” | “I said that three of the last five reports had been late.” |
| Feedback given in public or by a long email | A private conversation, often followed by a short written note |
| Waiting months, then raising everything at once | Raising it early, while the examples were recent |
| No question to the other person | Asking what was happening on their side, and listening |
| Ends with “and he accepted it” | Ends with an agreed change and a result you checked |
Picking which scenario to use
- Applying for a management role: use Scenario 1. If you’ve never formally managed, use a time you supervised, trained or led a project. The HR manager resume builder page shows how people-management results can be written up on a CV.
- Applying for an individual contributor role: Scenario 2 or 3 shows you can work well with peers and managers.
- Applying for project, account or procurement roles: Scenario 4 fits best. See the project manager resume builder page for how to show supplier and stakeholder management on paper.
Keep a second story ready. Interviewers often ask, “Tell me about a time you received difficult feedback”, and the two answers together show whether you practise what you preach.
Frequently asked questions
What if the feedback didn’t work?
That can still be a good answer, as long as you explain what you did next (escalating appropriately, trying a different approach) and what you learned.
Should I use the “feedback sandwich” in my example?
You can mention genuine positives, but don’t present wrapping criticism in praise as a technique. Interviewers may see it as softening the message until it’s lost. Clear, specific and kind is the better goal.
How long should the answer be?
About two minutes. Spend most of it on what you said and what happened next.
Is it acceptable to use a story about feedback on a student group project?
Yes, for early-career candidates. Choose one where you spoke to the person directly and something changed as a result.
Sources
- Use Situation-Behavior-Impact (SBI) to Understand Intent, Center for Creative Leadership
- Problems with an employee’s performance, Acas