How to Answer "Tell Me About a Time You Had to Give Difficult Feedback" (With Sample Answers)

Receiving feedback tests whether you're coachable. Giving it tests something harder: whether you'll say the uncomfortable thing at all, and whether you'll say it well. Most people fail this question in one of two directions — either they avoided the conversation for months, or they had it so bluntly that the relationship never recovered.

Note that this question is not reserved for managers. Interviewers ask it of individual contributors precisely because giving feedback sideways, without authority, is harder than giving it downwards.

What the interviewer is actually testing

• Will you raise the issue? A team where problems go unspoken is a team that degrades quietly. They want evidence you'll speak up.
• Do you separate the behaviour from the person? The difference between "the estimates have been consistently optimistic" and "you're unreliable" is the whole skill.
• Did you prepare, or did you vent? Choosing the moment and the framing is judgement; blurting is not.
• What happened to the relationship afterwards? The best answers end with the working relationship intact or improved.

A structure that works

1. The situation, and why it mattered. Establish stakes. Feedback about something inconsequential doesn't demonstrate anything.
2. Why it was hard. A power dynamic, a friendship, a personality, your own uncertainty about whether you were right.
3. How you prepared and how you opened. Interviewers listen closely here — the opening line tells them a lot.
4. How they reacted, honestly. Including badly, if that's what happened.
5. The outcome, and where the relationship landed.

Sample answers

Sample 1 — peer to peer, no authority

"A colleague on my team was consistently merging code without waiting for review. Not malicious — he was under pressure and reviews were slow — but we'd had two production incidents that a review would have caught, and other people had started copying the habit.

It was awkward because he was more senior than me and we were friendly. My worry was that it would land as a junior person policing him.

I asked for fifteen minutes rather than raising it in standup, and I opened with the incidents rather than with him: 'we've had two incidents in a month that came from unreviewed merges, and I think our review turnaround is part of why people skip it. Can we fix that together?' That framing was deliberate — the problem was partly systemic and saying so wasn't a concession, it was accurate.

He was defensive for about the first two minutes, then said he'd been frustrated that his own reviews sat for two days. We agreed a rule: reviews under 200 lines get looked at within four hours, and nothing merges unreviewed. I took the first week of enforcing it on myself so it wasn't a rule I'd imposed on him.

We had no further incidents from that cause, and he's a reference of mine now."

Sample 2 — managing someone underperforming

"I had a report whose work quality had dropped noticeably over about two months — missed details, a client-facing error. I'd been softening it in our 1:1s, which I now think was the actual mistake, because by the time I addressed it directly he was genuinely surprised.

What made it hard was that I suspected something personal was going on, and I didn't want to either pry or use it as an excuse to avoid the conversation.

I prepared by writing down three specific examples with dates, so it couldn't turn into a debate about impressions. I opened by naming the pattern and the gap: 'these three things happened, and they're not the standard of work I've seen from you for the last two years — what's going on?' Leading with the fact that this was a change, rather than a verdict on him, was the part I thought hardest about.

He told me his father was ill. We agreed a reduced scope for six weeks and I moved the client work to someone else — but I was explicit that the standard wasn't changing permanently, and we put a date on revisiting it. He came back to full scope after seven weeks and was one of my strongest people the following year.

The lesson I took was about the two months, not the conversation. Saying it earlier would have been kinder."

Sample 3 — upwards, to a manager

"My manager had a habit of restating a decision in a way that made it sound like the team had agreed to it when we clearly hadn't, and two people had told me privately they'd stopped raising objections because of it.

This was uncomfortable for obvious reasons — she wrote my review.

I raised it in a 1:1, framed around a specific meeting rather than her character, and made it about the effect rather than the intent: 'when the roadmap call ended, I think you left believing we'd aligned on Q3 and I don't think we had. I'm worried people are staying quiet rather than disagreeing.' I also came with a suggestion rather than only a complaint — an explicit 'objections?' pause before closing decisions.

She took it better than I expected, and said nobody had told her. She started ending decision meetings by asking each person directly. It didn't fix everything but it changed that specific pattern."

Sample 4 — feedback to a client or stakeholder

"We had a client who kept adding scope mid-sprint through direct messages to individual engineers, bypassing me entirely. The team was drowning and the delivery date was going to slip, and nobody had told him that yet.

Hard because he was the budget holder and because the engineers had been saying yes, so from his side nothing was wrong.

I set up a call, brought a list of the eleven out-of-sprint requests from the previous month with the estimated cost of each, and put the choice in his hands rather than making it an accusation: 'these are the additions, they total about three weeks, so we can move the date or cut something from the original scope — which do you want?'

He hadn't realised the volume. He cut two features himself. We also agreed all requests came through me, which protected the engineers from having to say no to a client.

We delivered on the original date and they renewed."

Common mistakes

• Choosing an example with no discomfort in it. If it wasn't hard, it doesn't answer the question.
• Making the other person the villain. Contempt in the retelling suggests contempt in the conversation.
• The compliment sandwich. Describing it as a technique dates you and, worse, most interviewers know the criticism gets lost in the padding.
• Skipping the preparation. "I just told him straight" isn't courage, it's an absence of judgement.
• Claiming it went perfectly. Difficult conversations are rarely clean. An answer where the person immediately thanked you sounds invented.
• Only ever giving feedback downwards. If every example is to a subordinate, it hints you avoid it with peers and managers.

Follow-up questions to expect

• "What would you do differently?" — Almost always asked. Have a real answer, and "I'd have said it sooner" is the most common honest one.
• "What if they'd reacted badly?" — Or, if they did: what you did next. Interviewers want to know you don't retreat at the first sign of resistance.
• "How do you decide whether feedback is worth giving?" — A good answer has a filter: does it affect the work, is it a pattern rather than an incident, can the person actually change it.