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: You're in an interview and the hiring manager asks, 'Tell me about a time you received difficult feedback.' Most of us prep for the reverse — giving feedback to a peer or a direct report. But being on the receiving end? That's the one that catches people off guard. Luna: It really does. And the thing is, hiring managers often care more about how you take criticism than how you dish it out. Because how you receive feedback tells them a lot about your self-awareness and your ability to grow. Lucas: Exactly. There's actually some hard data here. A 2025 survey from the Corporate Executive Board found that 67 percent of hiring managers say a candidate's response to receiving feedback is a stronger predictor of on-the-job performance than their technical skills. Two-thirds. That's huge. Luna: Wow, that's a compelling stat. So you can be the most brilliant analyst in the room, but if you shut down when someone tells you your model has a flaw, that's a red flag. Lucas: Right. And that's what we're going to drill into today. How to actually answer this question in a way that feels genuine and shows growth, not just recites a script. We'll look at a specific case — a product manager at a fintech company who was told she was too dismissive in meetings. Luna: Oh, that's a tough one. Being told you're dismissive — that's not about a technical skill, it's about how you show up as a colleague. That can sting. Lucas: It does sting. And the natural instinct is to defend yourself. 'I wasn't being dismissive, I was just being direct' or 'The meeting ran long.' But the interview is not the place to justify your old behavior. It's the place to show you listened and changed. Luna: So what's the framework? Most people know STAR — Situation, Task, Action, Result. But that doesn't quite work here because the 'result' is usually something internal, like a change in behavior, not a measurable business outcome. Lucas: Right. STAR works great for project-based questions. But for feedback reception, I prefer a twist I call PARAC — Problem, Action, Result, Alternative, Change. Let me walk through it using that product manager's story. Luna: Love it. So what's the problem in her case? Lucas: The feedback came during a one-on-one with her manager after a cross-functional product review. Her manager said, 'Several engineers told me they feel you cut them off and dismiss their input during sprint planning. They're starting to hold back ideas.' That's the Problem piece — specific, concrete, not vague. Luna: And the Action? Did she immediately apologize and say she'd change? Lucas: That's the trap. If you say, 'I apologized and promised to do better,' that sounds shallow. Instead, she asked clarifying questions: 'Can you give me an example of when I did that?' and 'What would a better response have looked like?' That's the Action — you want to show you sought to understand before you committed to change. Luna: That's smart because it shows you're not just accepting feedback passively, you're trying to really get it. What was the Result? Lucas: The manager gave her a concrete example: in a sprint retro, when an engineer suggested a different database approach, she immediately said, 'That won't work because of latency,' without acknowledging the idea. Her manager suggested she try saying, 'Interesting — can you walk me through the latency tradeoff?' So the result was she started using that phrase in meetings. But that's not the end of the story — PARAC adds Alternative and Change. Luna: Alternative meaning what she could have done instead? Lucas: Exactly. She could have gotten defensive, or she could have just said 'Okay' and not actually changed. The Alternative she names is the old pattern: nodding without taking action. And the Change is the deeper shift — she realized her direct style was being read as dismissive because she wasn't pausing to validate the other person's contribution. So she started a habit of paraphrasing the engineer's idea before giving her own perspective. That's the Change — not just a surface fix, but a new mental model. Luna: That is such a great framework. It turns the story from 'I got feedback and did better' into 'I understood why the feedback mattered and rewired how I collaborate.' Hiring managers eat that up. Lucas: They do, because it signals learning agility. And that's the core of this question — it's not about the feedback itself, it's about your relationship with learning. Can you take an uncomfortable truth and actually integrate it, or do you deflect? Luna: What are the biggest mistakes people make when answering this? Lucas: Number one: making the feedback seem minor. 'My manager told me my emails were too long.' That's safe, but it doesn't show real growth. Pick something that genuinely forced you to change how you work. Number two: blaming the giver. 'My coworker was overly sensitive.' That's an instant disqualifier. Luna: Yeah, I've heard people say, 'The feedback was unfair, but I listened anyway.' Even if it's true, it makes you sound defensive. The interview is not the place to litigate whether the feedback was correct. Lucas: Exactly. Always assume the feedback was valid for the purpose of the story. And number three: not showing the Change. If you just say 'I took the feedback and improved,' that's vague. You need to name the specific new behavior. Like the product manager who started paraphrasing before responding. Luna: So what about someone who's early in their career and maybe hasn't had a big feedback moment? Can they still answer this? Lucas: Absolutely. Use feedback from a class project, a volunteer role, or even a coach. The scale doesn't matter as long as the process is there. For example, a college athlete might have been told they needed to be a better team player. The same PARAC structure works. Luna: That's a good point. And it's actually more relatable in some ways because hiring managers know junior candidates haven't had years of performance reviews. Lucas: Right. The key is to show the same arc: you received the feedback, you worked to understand it, you implemented a change, and you reflected on what that taught you about yourself. That reflection piece is what separates a good answer from a great one. Luna: I want to circle back to the PARAC framework. The Alternative and Change — are those meant to be spoken out loud in the interview, or are they more for your own preparation? Lucas: You should say them. The Alternative shows you considered other paths — it signals that you're deliberate, not just reactive. And the Change shows the deeper lesson. In the product manager's case, she might say, 'The alternative would have been to just apologize and go back to business as usual, but that wouldn't have addressed the root issue. The real change was learning that my directness, which I'd always seen as a strength, could have a negative impact if I didn't balance it with validation.' Luna: That's powerful because it shows vulnerability without being weak. It's a sign of maturity. Lucas: And that's what interviewers are listening for. They want to know, 'Can this person take feedback and evolve?' Because in a fast-moving company, the people who can't adapt become bottlenecks. Luna: It reminds me of something I read about the best teams — they're not necessarily the ones with the smartest individuals, but the ones where people can give and receive feedback fluidly. That psychological safety piece. Lucas: Exactly. And your interview is your first chance to demonstrate that you can contribute to that kind of culture. So pick a story that's genuine, use the PARAC structure, and don't be afraid to show a little vulnerability. Luna: Alright, so let's put it all together. If you're preparing for an interview, how would you actually script a 90-second answer? Lucas: I'd say something like: 'In my second year as a product manager, my manager told me that I was coming across as dismissive in cross-functional meetings. Specifically, I would shoot down ideas without acknowledging the person who raised them. I asked for examples and then committed to changing how I responded. I started using phrases like, "Help me understand the tradeoff" before pushing back. The alternative would have been to brush it off, but the real change was realizing that my directness needed to be paired with validation. Now I make a point of paraphrasing the other person's point before offering my perspective.' That's about 90 seconds. Luna: That's tight and it hits every element. And it's honest — it doesn't pretend she was perfect before. Lucas: Exactly. And that honesty is what lands. Listeners, if this episode has helped you think about how you might answer a tough interview question, or if you've ever used the PARAC approach in your own prep, we'd love to hear from you. But more importantly, if you've gotten value from the show — if it's helped you land a job or sharpen your interview skills — a couple of dollars a month is genuinely what keeps these going. You can find us at buy me a coffee dot com slash fexingo. It's a small way to support the ad-free model we have here. Luna: Yeah, and it really does make a difference. Even a few contributions help us keep producing episodes like this one. Lucas: Alright, back to the topic. One more thing I want to cover: how to handle the follow-up question. Interviewers often ask, 'How did that change your approach going forward?' That's your cue to double down on the Change part of PARAC. Luna: So they're basically asking you to prove that the lesson stuck. That's where you can bring in a second example, even a small one, to show consistency. Lucas: Right. Say something like, 'Six months later, I was in a similar meeting with a different team, and I caught myself about to dismiss an idea. I paused, asked the engineer to elaborate, and we ended up incorporating part of their suggestion. That moment confirmed the feedback had truly changed my default behavior.' Luna: That's a nice bookend. It shows the habit became automatic. Lucas: So to recap: when you get the 'tell me about a time you received difficult feedback' question, don't panic. Use PARAC — Problem, Action, Result, Alternative, Change. Pick a story that's meaningful, show you sought to understand before acting, and be specific about the new behavior you adopted. Avoid defensiveness, avoid trivial feedback, and always end with what you learned about yourself. Luna: And if you're practicing, record yourself. Listen for any hedging words like 'sort of' or 'I guess.' Confidence matters. Lucas: Great tip. Next time on Interview Prep, we're going to tackle the question, 'Tell me about a time you had to influence without authority.' That's a classic. Until then, keep preparing, keep practicing, and remember — the best interviews are conversations, not interrogations. Luna: See you next time.