Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Managed a Difficult Boss
Transcript
- Lucas: We've covered a lot of behavioral questions on this show — conflict, failure, delegation, resilience. But there's one that candidates tell me makes them the most nervous, and we haven't touched it yet. Luna: Let me guess — it's the one about the boss. Lucas: Exactly. 'Tell me about a time you had to manage a difficult boss or supervisor.' It's tricky because if you say anything negative, you look like a complainer. But if you sugarcoat it, the story has no tension. Luna: Right — and most people have at least one difficult boss story. The question is how to tell it without trashing someone. Lucas: So let's start with a specific example. I worked with a product manager at a mid-sized SaaS company — let's call her Priya. Her VP of Product was a classic micromanager. He wanted to approve every wireframe, every email to customers, every slide deck. Priya was spending more time getting sign-off than actually building product. Luna: That sounds exhausting. And the natural instinct is to say 'my boss didn't trust me' or 'he was controlling.' Lucas: Right, but if she says that in an interview, the hiring manager wonders: will you say the same thing about me six months from now? Instead, she framed it around the VP's pressures. He had just been promoted, the board was nervous about a key launch, and he'd been burned before by a junior PM who shipped a buggy feature. Luna: So she made it about his context, not his personality. That's smart. Lucas: Exactly. The STAR story she used went like this. Situation: she was leading a new onboarding flow that had to launch in six weeks. Task: deliver on time while maintaining quality — but the VP was reviewing every detail, causing delays. Luna: And what was her action? Because simply 'I talked to him' isn't enough. Lucas: She proposed a structured weekly check-in: a 30-minute design review on Tuesdays and a 15-minute status update on Thursdays. She also created a one-page brief for each feature that summarized the design rationale, trade-offs, and risk level — so he could see her thinking without reading 50-slide decks. She said, 'I want you to feel informed without needing to be in the weeds.' Luna: That's a great line. It shows empathy and proactiveness. Lucas: Result: the VP agreed, the launch shipped on time, and after that project he gave her more autonomy. She ended the story by saying, 'I learned that difficult bosses are often just under pressure, and my job is to make their job easier while protecting my team's focus.' Luna: That's a really clean arc. And she positioned herself as someone who manages up, not someone who complains. Lucas: Now, let's talk about what not to do. I once heard a candidate say, 'My boss was crazy. He changed his mind every hour.' That's a red flag — even if it's true. Luna: Yeah, I had a sales director once tell me about his CEO who pivoted strategy every quarter. His story was that the CEO was 'visionary' but 'hard to pin down.' But he reframed it as: the CEO was responding to market shifts quickly, and my job was to build flexible sales plans. Lucas: That's a good reframe. The key is to choose a boss whose difficult behavior stemmed from a legitimate business pressure — a new role, a turnaround, a competitive threat — not from malice or incompetence. Luna: What if the boss was genuinely toxic? Should you pick a different story? Lucas: Yes. If the only difficult boss you've had was truly toxic — yelling, undermining, unethical — do not use that story. Pick a different example of managing a difficult situation or stakeholder. The interviewer doesn't need to hear about trauma. They want to see your interpersonal skills. Luna: That's a really important distinction. So the story should show you managed a style difference, not a personality disorder. Lucas: Right. And the best stories involve some introspection. What did you learn about yourself? For Priya, she realized she had been assuming her VP didn't trust her, when really he just needed a different communication rhythm. Luna: I think that's what makes these answers stand out — the candidate shows self-awareness, not just problem-solving. Lucas: You know, this kind of practical advice is exactly why we keep this show ad-free. If it's helped you think through a career move or decision, the best way to keep it going is a small gesture at buy me a coffee dot com slash fexingo. Luna: Yeah, it's a nice way to say the episodes have value without putting up a paywall. No pressure, just appreciation. Lucas: Exactly. So back to the boss question — one more nuance. The story should also show that you can influence without authority, because managing a boss is a form of leading sideways. Luna: Right — you're not their manager, but you're guiding their behavior. That's a skill every hiring manager wants to see. Lucas: Let's quickly walk through a template. Situation: one sentence about the boss's style and the business context. Task: what you needed to accomplish despite the friction. Action: two to three specific steps you took to adapt the relationship — not to change the boss, but to work with them effectively. Luna: And the result should be measurable. Did the project succeed? Did the relationship improve? Did you get more autonomy? Lucas: Yes. And a great closing line is something like, 'Looking back, I'd handle it the same way, because I learned that understanding someone's constraints is the first step to building trust.' Luna: That's a strong statement. It shows maturity and a growth mindset. Lucas: One final pitfall: don't make the boss the villain of the story. Even if you use neutral language, if the arc is 'boss was bad, I fixed it,' it still sounds negative. Instead, frame it as 'we had a misalignment, and I bridged it.' Luna: I like that reframing. It's collaborative, not adversarial. Lucas: Alright, let's wrap with a practical exercise. Think of a boss you've had who was challenging. Write down the pressure they were under — not just their behavior. Then write what you did to make the relationship work. If you can't find a story that passes the 'no villain' test, pick a different stakeholder. Luna: And practice it out loud. The tone matters as much as the content. Lucas: Great point. Next episode we'll tackle a related one — 'Tell me about a time you had to manage a difficult stakeholder who wasn't your boss.' That adds another layer. Luna: I'm already thinking of examples. See you next time.