Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Received Difficult Feedback
Transcript
- Lucas: So Luna, I want to start with something that came up in a conversation I had last week with a hiring manager at a mid-sized tech company. She said the question that trips up more candidates than any other is not 'tell me about a time you failed'—it's 'tell me about a time you received difficult feedback.' Luna: Interesting. Because failure feels like a story you can control, but feedback? That's someone else's perspective coming at you. Lucas: Exactly. And the hiring manager told me that how you answer that question reveals more about your emotional intelligence and coachability than almost anything else in the interview. So today we're going to break down how to answer it well. Luna: What's the typical mistake people make? Lucas: Two big ones. First, they get defensive—even subtly. They say something like 'my manager gave me feedback that I was too detail-oriented, but actually that was just because the project required precision.' And the interviewer hears, 'this person can't take input.' Luna: Right, you're justifying instead of accepting. Lucas: Second mistake: they fake a pivot. They say 'I received feedback that I wasn't speaking up in meetings, so I started speaking up more.' That's too vague—it sounds like you just flipped a switch. Interviewers want to see that you actually processed the feedback and changed your behavior in a specific way. Luna: So what's the right structure? Lucas: I like a three-part framework. First, acknowledge the feedback and your initial reaction—honestly. Second, describe what you did specifically to address it. Third, explain what changed as a result, ideally with a concrete outcome. Luna: Can you give an example? Something real? Lucas: Sure. Let's say a product manager gets told she's not strategic enough—she's too focused on execution. In an interview, she might say: 'My manager told me I needed to think more about the long-term product vision, and honestly, my first reaction was frustration because I thought I was being efficient. But then I realized she was right—I was so busy shipping features that I wasn't connecting them to the roadmap.' Luna: That's a strong start—she's showing self-awareness. Lucas: Then the second part: 'So I asked her if I could spend 20 percent of my week on competitive research and user interviews. I also started writing a one-page strategic memo before each sprint, outlining how the features tied to our quarterly goals.' That shows a specific, measurable action. Luna: And the outcome? Lucas: Third part: 'After three months, my manager said my sprint planning was more aligned with the product vision, and she asked me to present the roadmap to the leadership team. That was a direct result of taking her feedback seriously.' Luna: That's a solid narrative. It also avoids the trap of making the feedback seem trivial. Some people pick something like 'I was told I was too perfectionistic'—which sounds like a humblebrag. Lucas: Exactly. Pick feedback that was genuinely hard to hear, but that you can honestly say made you better. And don't pick something that reveals a fatal flaw—like 'I was told I'm bad at collaboration.' That's too core to the job. Luna: You know, we've been doing this podcast for a while now, and a lot of listeners have told us these episodes help them think through actual career decisions. If that's you, and you'd like to support the show staying ad-free, you can buy us a coffee at buy me a coffee dot com slash fexingo. No pressure, just a way to keep it going. Lucas: Yeah, we really appreciate that. And it helps us keep doing deep dives like this one. So back to the framework—let's talk about what not to do. Luna: One thing I see is people picking feedback that's too old. Like, from college. Hiring managers want to see that you're currently coachable. Lucas: Good point. Ideally, the feedback should be from the last couple of years. And it helps if you can name the context without disparaging the person who gave it. Never badmouth your former manager. Luna: Right, even if they were terrible. The interviewer is thinking, 'will this person talk about me that way someday?' Lucas: Exactly. Another pitfall: having no outcome. If you just say 'I got feedback and I worked on it' but can't point to a result, it sounds incomplete. The outcome doesn't have to be a promotion—it could be that your team's velocity improved, or that your manager trusted you with a bigger project. Luna: Should you ever mention that the feedback was wrong? Lucas: Rarely. If the feedback was truly unjustified, you can acknowledge that you initially disagreed but then found a kernel of truth. That shows you can find value even in imperfect feedback. But don't spend more than one sentence on the disagreement. Luna: Let's try another example. Say someone gets told they're too quiet in meetings. Lucas: Classic. A good answer: 'My manager told me I wasn't contributing enough in team discussions. I was nervous about saying something half-baked. So I started preparing one or two points before each meeting—writing them down. After a few weeks, my manager noticed I was chiming in more, and I even led a brainstorming session.' That works because it shows a system, not just an intention. Luna: What about receiving feedback on a presentation style? Lucas: Sure. 'A stakeholder said my presentations were too data-heavy and not story-driven. I was a bit defensive because I love data. But I asked for examples and then took a storytelling workshop. In my next presentation, I led with the business question and used data to support it. The stakeholder said it was my best presentation yet.' Luna: Notice that each of these follows the same three beats: reaction, action, outcome. Lucas: Exactly. And the reaction should feel human. You can even say 'I felt my face get hot' or 'I was surprised.' That honesty makes you relatable. Then the action shows you're not stuck in that feeling. Luna: One more thing—timing. How long should the answer be? Lucas: About 90 seconds to two minutes. Any longer and you risk rambling. The interviewer wants to see that you can reflect, adapt, and move on. A concise answer signals that you've really processed it. Luna: So to wrap up: pick real feedback, show your honest reaction, describe a specific change, and share a concrete outcome. Lucas: Yeah. And practice it out loud. The more natural it sounds, the more it lands. Most candidates freeze on this question because they've never thought about it before the interview. Prep now, and you'll sound like someone who's genuinely coachable. Luna: Thanks, Lucas. And for anyone listening, we'll be back next episode with another tough question to tackle. Lucas: Take care, and good luck out there.