Tell Me About a Time You Gave Constructive Feedback: How to Answer

Short answer: interviewers ask "tell me about a time you gave constructive feedback" to see whether you can raise a problem directly, tie it to facts rather than personality, and help the other person improve without damaging trust. The best answers show preparation, a specific conversation, a measurable change afterward and what you learned about delivering feedback.

Feedback is one of the most common sources of workplace friction. Many people avoid it entirely, which lets small problems grow, and others deliver it so bluntly that the recipient becomes defensive and nothing changes. An interviewer asking this question wants evidence that you sit in the productive middle: candid enough to speak up, and skilled enough to be heard.

The question appears in interviews for almost every level. For individual contributors it usually probes peer feedback, which is harder because you have no formal authority. For team leads and managers, it probes how you handle underperformance, which is a core part of the job. Large employers that use structured behavioral interviews, including consulting firms, banks and tech companies, often map questions like this to competencies such as communication, collaboration, developing others or leadership.

It also pairs naturally with its mirror image, "tell me about a time you received difficult feedback". Some interviewers ask both in the same session to see whether you hold yourself to the standard you apply to others, so it helps to prepare the two answers together.

The story you pick matters more than the polish of your delivery. A well-chosen example makes the competencies obvious; a weak one forces you to explain why it counts. Look for a situation with three ingredients: a real problem with consequences for the work, some reason the conversation was uncomfortable, and a visible outcome afterward.

Good sources of stories

• A teammate whose work quality, deadlines or communication was affecting the group
• A direct report, intern or new hire you were onboarding or mentoring
• Upward feedback to a manager about a process, meeting habit or decision
• A client, vendor or partner whose behavior was causing delays or rework
• A group project at college where one member was not contributing
• A volunteer, sports or student-society role where you were responsible for others

Stories to avoid

Avoid examples where the feedback was trivial (a typo in a slide deck), where the other person was clearly the villain, or where the matter was really a disciplinary or HR issue such as harassment. Those cases call for escalation, not coaching, and talking about them can raise questions you do not want to answer. Avoid stories where the person you gave feedback to could be identified by the interviewer, such as a well-known colleague at a small firm in the same industry.

Finally, avoid stories where nothing changed. If your feedback genuinely did not land, you can still use it, but only if you frame it around what you learned and how you changed your approach the next time. A story with an honest, imperfect result often sounds more credible than one that ends in instant transformation.

The STAR method (Situation, Task, Action, Result) gives your answer a structure, but for feedback questions it helps to fill the Action step with a recognized feedback model. The Situation-Behavior-Impact (SBI) model, developed by the Center for Creative Leadership, is widely taught in management training and maps neatly onto an interview answer. We extend it with two steps that interviewers specifically look for: the other person's perspective and the follow-up.

Time allocation

Aim for roughly 90 to 120 seconds. A useful split is about 15 seconds on context, 60 to 75 seconds on preparation and the conversation, and 20 to 30 seconds on the result and reflection. Candidates usually overspend on context, explaining the project in detail, and underspend on the conversation, which is the bit being scored.

Why not the "feedback sandwich"?

Many people were taught to wrap criticism between two compliments. Plenty of management writers now argue that this dilutes the message: recipients either miss the criticism or learn to distrust praise. You do not need to criticize the sandwich in your answer, but describing a direct, specific and kind conversation will usually come across as more mature than describing a carefully disguised one. Sincere positive feedback is still valuable; it just works better when it is genuine and separate rather than used as packaging.

Each example below follows STAR with the SBI-plus steps inside it. Use them to see the structure, then replace every detail with your own experience. Interviewers hear sample answers often and can spot a borrowed story quickly.

Example 1: Peer feedback (graduate or analyst role)

Situation: "In my first year as a financial analyst, I shared a weekly reporting pack with another analyst. For three weeks in a row, the numbers in his section arrived the morning of the deadline, which meant I had no time to check them and we sent two corrections to the regional director."

Task: "We were peers, so I couldn't tell him what to do, but the errors had both our names on them and I didn't want to go to our manager before talking to him directly."

Action: "I checked the timestamps on the files first to make sure I wasn't misremembering. Then I asked him for a 15-minute coffee rather than raising it at our team stand-up. I said something like: 'For the last three packs, your section reached me after 8 a.m. on the deadline day, and that's why two errors got through. I don't think either of us wants to keep sending corrections.' Then I asked what was making the timing hard. It turned out the data he needed from another team came in late on Mondays, which I hadn't known. We agreed that he would send me a partial draft on Monday afternoon and the final figures by Tuesday at noon, and I offered to help chase the other team."

Result: "We sent the next eight packs with no corrections. What I took from it was to ask about the cause before assuming it was about effort; if I had opened with 'you're always late' we would never have found the upstream problem."

Example 2: Manager to direct report

Situation: "I led a team of five customer support specialists. One of my strongest people technically started closing tickets with very short replies, and her customer satisfaction scores dropped from around 92 percent to 78 percent over a month."

Task: "I needed to address the drop before it became a performance issue, without demotivating someone who was otherwise one of our best."

Action: "In our regular one-on-one, I shared three anonymized ticket examples and the score trend, and said: 'In these tickets the fix was right, but the reply was one line, and in two of them the customer wrote back asking for more detail. That's pulling your satisfaction scores down.' I asked what had changed. She told me she was trying to hit a personal target for tickets closed per day because she wanted to be considered for a senior role. I explained that the senior role is assessed on quality as much as volume, and we agreed she would use a short template for explanations and that I would review five of her tickets a week for a month."

Result: "Within six weeks her scores were back above 90 percent and her volume stayed high. She was promoted the following quarter. I also realized I had never explained the promotion criteria clearly to the team, so I wrote them up and shared them with everyone."

Example 3: Upward feedback to a manager

Situation: "My manager often changed project priorities in our team chat late in the evening, and people were starting work at 9 a.m. on tasks that had already been deprioritized."

Task: "I wanted to raise it respectfully, without making it sound like I was criticizing her leadership."

Action: "I asked for ten minutes in our one-on-one and framed it around the outcome we both wanted. I said: 'When priorities change in the chat after 8 p.m., about half the team doesn't see it until mid-morning, and last week that meant two of us spent a morning on the old version of the client deck.' I suggested a short priorities message at 9 a.m. instead, and offered to put together a shared tracker."

Result: "She agreed to try it for a month, and then kept it. She also told me later she appreciated that I had brought it to her privately with a solution rather than complaining to the team."

Example 4: Group project (no work experience)

Situation: "In a four-person capstone project, one teammate missed two planning meetings and hadn't started his part of the literature review a week before our first draft was due."

Action: "Rather than message the group, I called him. I said the draft was due Friday, his section was the only one not started, and the rest of us were worried we would need to rewrite our sections around a gap. He told me he was working extra shifts and had felt embarrassed about falling behind. We split his section into two smaller parts, I took one and he committed to the other by Wednesday."

Result: "He delivered on Wednesday, we submitted on time and earned an A-minus. I learned that calling, rather than messaging, makes it much easier for someone to be honest."

The difference between an average and an excellent answer is rarely the story itself. It is usually the level of detail in the conversation and whether the candidate takes some responsibility for the outcome. Compare the two versions below of the same situation.

The self-check

Before your interview, run your answer against five questions. Could a stranger picture the exact behavior? Is it clear why it mattered? Did the other person get to speak? Is there a number or concrete change in the result? Is there one sentence about what you learned? If any answer is no, that is the part of your story to rework.

It also helps to say your answer out loud and time it. Most first drafts run to three minutes or more, and the excess is almost always background about the project. Cut the context ruthlessly and keep the dialogue.

Most weak answers to this question fall into a handful of predictable traps. Avoiding them will put you ahead of a large share of candidates.

Over-claiming the result

Claims like "she completely turned her career around" or "he thanked me and we became best friends" can sound exaggerated. A modest, specific result is more believable: scores recovered, deadlines were met, the process changed. If the relationship was a little awkward for a week afterward, saying so honestly can actually add credibility.

Forgetting the "why now"

Interviewers often probe why you chose that moment to say something. If you waited months, they may ask why. Prepare a short explanation: perhaps you wanted to confirm it was a pattern, or the impact had only just become visible. Showing that the timing was deliberate turns a potential weakness into evidence of judgment. For more on how this competency is assessed in leadership roles, see our leadership interview questions guide.

Structured interviewers often follow the main question with probes designed to test whether the story is real and how deep your skill goes. Expect at least one or two of the following, and prepare a short answer for each from the same story.

Questions that use the same answer

• "Tell me about a time you had to give someone difficult feedback."
• "Describe a time you addressed a performance issue."
• "Tell me about a time you had a difficult conversation with a coworker."
• "How do you handle a team member who is not pulling their weight?"
• "Give an example of when you challenged a colleague's work."

Aptitude tests and situational judgment tests used early in many hiring processes also touch on this competency. A situational judgment item might ask which response is most effective when a colleague repeatedly submits work late, and the options usually reward a private, direct and constructive conversation over ignoring the issue or escalating immediately. Our situational judgment test guide explains how those items are scored.