To answer "tell me about a time you gave difficult feedback," pick a real moment when you told a peer, a direct report or your manager something they did not want to hear, describe exactly how you delivered it, and finish with what changed afterward. Interviewers want to see that you raise problems early, stay specific and respectful, and follow up until the behavior or outcome actually improves.
This page is about giving feedback. If the question is about taking it, see our guide to answering "tell me about a time you received critical feedback". Both belong to the wider set of "tell me about a time" interview questions.
What is the interviewer really testing with this question?
Most people avoid hard conversations. The question checks whether you can have one without damaging the working relationship, and whether you do it soon enough to matter. It commonly appears in loops for managers and team leads, but individual contributors get it too, often phrased as "tell me about a time you had to tell a colleague something difficult."
| Signal | A strong answer shows | What weakens it |
|---|---|---|
| Courage | You raised the issue yourself, early, without waiting to be asked | You complained to others first, or waited for a performance review |
| Specificity | You described observable behavior and its effect | "I told him his attitude was a problem" |
| Empathy | You asked for their view and listened before deciding what to do | A one-way lecture |
| Follow-through | You checked back and can point to a change | The story ends when the meeting ends |
| Judgment | You picked the right setting: private, timely, prepared | Feedback given in a group chat or in front of a client |
A short answer frame: STAR with SBI in the middle
Use the STAR method (Situation, Task, Action, Result) for the overall story. For the Action step, borrow a feedback model so the interviewer hears how you actually phrased it. A widely used one is the Situation-Behavior-Impact (SBI) model from the Center for Creative Leadership. In our words: name the specific moment, describe what the person did in terms anyone could have observed, and explain the effect it had. CCL's extended version adds a fourth step, asking about the person's intent, which turns the talk into a two-way conversation.
| Part | What to say | Rough length |
|---|---|---|
| Situation | Who the person was, your relationship, and what was at stake | 2 sentences |
| Task | Why it fell to you to say something | 1 sentence |
| Action | How you prepared, the situation-behavior-impact wording you used, what you asked, and the plan you agreed | Most of the answer |
| Result | The measurable change and the state of the relationship afterward | 2 to 3 sentences |
Aim for about two minutes. Quote one or two lines of what you actually said; it makes the story concrete and shows your tone.
Three example answers we wrote
These are example answers we wrote to show the shape of a strong response. The people, details and numbers are invented. Use your own story and your real results.
Example answer we wrote: feedback to a peer
Situation. I was a backend engineer on a team of six. A senior peer reviewed most pull requests, and his comments were often blunt one-liners like "this is wrong, redo it." Our newest engineer had gone from three or four pull requests a week to one, and told me she was nervous about submitting anything.
Task. I had no authority over him, but I had a good working relationship with him and I did not want the problem to sit until a retro or a review cycle.
Action. I asked him for fifteen minutes one-on-one and brought two specific comments. I said: "On Tuesday's caching pull request, the comments were 'wrong' and 'redo,' without saying what to change. Since then, Priya has been holding her work for days before submitting it." Then I asked what he was aiming for. He said he was short on time and thought short comments were efficient. We agreed he would add one line of reasoning or a link to each blocking comment, and I offered to pair with Priya on her next two reviews.
Result. Within a month, Priya was back to three or four pull requests a week, and her average time from opening a pull request to merging it fell from four days to under two. He later added a "how we review" section to our team wiki, and he still asks me for feedback on his reviews.
Example answer we wrote: feedback to a direct report
Situation. As a product manager leading two associate PMs, I noticed one of them, Marcus, had missed three of the last four weekly status updates to our sales stakeholders. The sales director had started emailing me directly to ask what was shipping.
Task. Marcus was strong on discovery work, and I wanted to fix this without making him feel micromanaged.
Action. In our next one-on-one I said: "In the last four weeks, three status updates didn't go out. Sales planned a customer call without knowing the export feature had slipped, and their director is now coming to me instead of you." I asked what was getting in the way. He said writing updates felt like busywork and kept falling to the bottom of his list. We agreed on a ten-minute template, a fixed Thursday slot on his calendar, and that I would read the first two before they went out.
Result. He sent the update on time for the next ten weeks straight. The sales director stopped escalating to me, and in Marcus's next review she named him as her main product contact. He told me later he preferred hearing it directly over finding out at review time.
Example answer we wrote: feedback to a manager
Situation. I was a data analyst producing a weekly revenue report for leadership. My manager regularly sent new requests late on Friday afternoon for the Monday deck.
Task. Rushed changes were causing errors, including one wrong regional total that reached the executive team. I needed to raise it without sounding like I was refusing work.
Action. I booked time early in the week, not on a Friday. I said: "Over the last six weeks, four of the Monday reports had requests come in after 3 p.m. on Friday. Two of those reports went out with errors, including the regional total the CFO flagged." I asked what was driving the timing. Her own requests were arriving late from leadership. I proposed a Wednesday cutoff for changes, with anything later going into the following week's report unless she marked it urgent.
Result. She agreed and explained the cutoff to her own stakeholders. Over the next quarter, report errors went from about three a month to zero, and she asked me to set up the same cutoff for a second report.
Weak vs strong answers
| Weak answer | Strong answer |
|---|---|
| "I told her she needed to be more professional." | "In Monday's client call, you interrupted the client twice while they were describing the bug, and they asked me afterward to run the next call." |
| Feedback delivered by email or in a group setting | A private conversation, prepared in advance, close to the event |
| You did all the talking | You asked for their view and adjusted the plan |
| "It went fine." | A number or a visible change, plus how the relationship held up |
| The other person is the villain | The other person is reasonable and had a reason for the behavior |
What follow-up questions should you expect?
- "How did they react?" Be honest. If they were defensive at first, say so, and explain what you did next.
- "What would you do if they disagreed?" Describe how you would look for shared facts, and when you would involve a manager.
- "Why didn't you raise it sooner?" If you waited, own it and say what you do differently now.
- "Tell me about a time feedback didn't land." Prepare a second story where it took two conversations, or where you changed your approach.
- "How do you give positive feedback?" The same specificity applies: name the situation, the behavior and the impact.
If the feedback turned into a real disagreement, your story may fit "tell me about a conflict with a coworker" better. Feedback to a manager also overlaps with disagreeing with your manager.
Mistakes to avoid
- Making it about personality. "He's lazy" is a judgment. "He missed the last three handoffs" is feedback.
- Picking a story where you were harsh. If the person cried and quit, the interviewer will question your judgment, even if you were right.
- Skipping the listening step. The best stories include something you learned from their side.
- No follow-up. Feedback without a check-in is only half the job. Mention when and how you followed up.
- Sharing private details. Leave out health, family or performance-plan specifics, and do not use real full names.
Giving feedback often leads into coaching. If your story continued into weeks of support, consider telling it as a time you mentored someone instead.
Practice it
Feedback stories go wrong in tone more than in content, so say yours out loud. Run a free AI mock interview built from your résumé and the job description, answer the question as if the interviewer were in front of you, and get each answer scored out of 10 with what to fix. It is free for 15 minutes a day, with no account. Draft the story first with the STAR story builder, then rehearse until you can deliver the key line naturally. Follow each employer's rules on AI tools, and use AI to prepare beforehand.
Rehearse your feedback story tonight
Answer behavioral questions out loud, get a score out of 10 and specific fixes, and repeat until it sounds like you. Free for 15 minutes a day.
Try a free AI mock interviewFAQ
What if I have never managed anyone?
Use feedback to a peer, a manager, a vendor or a classmate on a group project. Interviewers ask individual contributors this question to see how they handle hard conversations, not to check a management title.
Can I use feedback I gave to my manager?
Yes, and it can be a strong choice because it shows courage. Keep the tone respectful, show you understood their constraints, and end with a change that helped the team.
What is the SBI feedback model?
SBI stands for Situation, Behavior, Impact. It comes from the Center for Creative Leadership: you name the specific moment, describe the observable behavior and explain its effect, then ask about the person's intent.
How long should my answer be?
About two minutes. Spend most of it on how you prepared and delivered the feedback, and keep the setup to two or three sentences.
What if the feedback did not work?
You can still use the story if you show what you learned and what you did next, such as changing your approach or escalating appropriately. Be clear about the outcome rather than implying a success.
Is this the same as "tell me about a time you received feedback"?
No. That question tests how you take criticism. This one tests how you give it. Prepare a separate story for each.