Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Had to Persuade a Skeptical Stakeholder
Transcript
- Lucas: So you're in an interview and the hiring manager says — 'Tell me about a time you had to persuade a skeptical stakeholder.' That is one of the most common behavioral questions for mid-to-senior roles, and it's also one of the most frequently botched. Luna: Botched how? Like the candidate just doesn't have a good story ready? Lucas: Partly, yeah. But more often, they have a story but they tell it wrong. They focus on how right they were instead of how they brought the other person along. And that's a subtle but critical difference. So today, let's unpack exactly what hiring managers are looking for and build a repeatable answer. Luna: Alright. I'm thinking about this from the hiring manager's seat — why ask this question at all? Lucas: Good question. The core competency being tested is influence without authority. In most roles — product, finance, operations, marketing — you will regularly need to get buy-in from people who don't report to you. And they might be skeptical because of budget constraints, competing priorities, or past experiences. The interviewer wants to see that you can navigate that tension without burning bridges. Luna: So it's not about winning an argument. It's about building alignment. Lucas: Exactly. The best answers show empathy for the stakeholder's position, a structured approach to understanding their concerns, and a willingness to adapt your proposal. Let's look at a concrete example. Imagine a product manager who needs to convince a skeptical engineering VP to prioritize technical debt over new features. Luna: That's a classic tension. The VP is probably measured on shipping new stuff, not on refactoring old code. Lucas: Right. So the candidate's story needs to show they understood that. A weak answer would be: 'I explained why technical debt was slowing us down and the VP eventually agreed.' That tells me nothing about how they persuaded. A strong answer uses the STAR framework — situation, task, action, result — but with extra emphasis on the action part. Luna: Specifically, what does the action part look like for persuasion? Lucas: It should include three elements. First, how you prepared — did you gather data, talk to other stakeholders, anticipate objections? Second, how you framed the conversation — did you start with shared goals rather than demands? Third, how you adapted when the stakeholder pushed back. Let me give you a quick example from a real candidate I coached. Luna: Please. Lucas: She was a senior analyst at a consumer goods company. Her CFO was skeptical about switching from a cost-plus pricing model to value-based pricing. The CFO's concern was margin volatility. So she didn't just show him a new model. She first ran a side-by-side simulation on their top ten SKUs using historical data, and she modeled the worst-case downside under the new approach. Then she scheduled a 30-minute meeting focused on risk mitigation, not revenue upside. Luna: Smart. She addressed his fear directly. Lucas: Right. And she didn't stop there. She proposed a phased rollout — start with just three SKUs, measure for two months, then reassess. That gave the CFO an off-ramp if things went badly. He agreed to the pilot. The result? Margins improved by 4.5 percent on those SKUs without any volatility spike, and the company eventually rolled it out across the whole portfolio. Luna: That's a great story because it shows preparation, empathy, and flexibility. Now, what are the common mistakes you see? Lucas: Three big ones. First, the candidate presents themselves as the sole hero — the stakeholder is portrayed as unreasonable or slow. That signals poor relationship awareness. Second, they skip the 'adaptation' step — they just bulldozed through. Third, they get too technical or too abstract. The story becomes about the pricing model or the tech debt, not about the human dynamics of persuasion. Luna: So the story needs to be about the interaction, not the idea. Lucas: Exactly. And one more thing — the best answers include a specific phrase that shows active listening. For example, 'I heard your concern about X, so I adjusted Y.' That phrasing signals that you didn't just talk at them. You listened and adapted. Luna: Let's talk about structure for a moment. How long should the story be? Lucas: Aim for 90 to 120 seconds. That's roughly 20 to 30 seconds for situation and task combined, 60 seconds for action, and 15 to 20 seconds for result. The action chunk is where you really differentiate yourself. Luna: And if the interviewer asks a follow-up? Like 'What if the stakeholder still said no?' Lucas: That's a gift. It means they're engaged. You can then talk about how you would escalate constructively or find a compromise. But the key is to stay collaborative, not adversarial. Say something like, 'I would acknowledge their decision respectfully and ask if we could revisit in three months after I gather more data.' That shows emotional maturity. Luna: Alright, I want to try building one from scratch. Let's say I'm a marketing manager who needs to convince a skeptical VP of sales to allocate budget for a new content channel. Lucas: Great scenario. The VP of sales is probably skeptical because they've seen content initiatives before that didn't directly lead to pipeline. So start with the situation — the company was relying too heavily on outbound, and inbound was underinvested. Luna: For the task, I need to get the VP's buy-in to shift 10 percent of their budget to a podcast series targeting enterprise buyers. Lucas: Good. Now action — how do you prepare? You might interview three of their top reps to understand what questions prospects are asking, then map those to potential podcast topics. Then you run a small pilot — maybe two episodes with paid promotion — and track how many demos come from that channel. Luna: So I'm coming with data, not just a pitch. I like that. Then in the meeting, I start by acknowledging the VP's concern about measurable ROI. Lucas: Perfect. And you propose a test — four episodes, eight weeks, with clear metrics. If it generates at least as many qualified leads per dollar as a trade show, you scale. If not, you kill it. That makes the decision low-risk for the VP. Luna: Right. And the result — the pilot generates 12 qualified leads at a cost per lead 30 percent lower than the average trade show. The VP agrees to a six-month trial. Lucas: That's a solid answer. And notice the phrase: 'I understand your concern about ROI, so I designed a pilot with a clear off-ramp.' That's the listening and adapting language we talked about. Luna: This is genuinely useful. If listeners want to take this further, what's one thing they should do tonight? Lucas: Pick one professional situation where you persuaded someone. Map it to the STAR framework, but write out the action section with those three sub-elements: preparation, framing, adaptation. Practice it aloud twice. That's it. Luna: And if you found this episode helpful, the way we keep the show free and ad-free is through listener support. If today's tips saved you some prep time, buy me a coffee dot com slash fexingo helps us keep doing these deep dives. Lucas: Yeah, it really does. Even the price of a coffee goes directly into keeping production going. And we appreciate every single one. Luna: Alright, back to the STAR framework — let's talk about one more nuance. What if your story involves a stakeholder who was genuinely hostile? Lucas: That's a tough one. The key is to depersonalize. Never describe the person as 'difficult' or 'unreasonable.' Instead, focus on the situation: 'There was a tight deadline and the stakeholder had been burned by a similar proposal before.' That frames it as context, not character. Luna: And the action — how do you handle hostility? Lucas: You listen first. Let them vent. Then you reflect back what you heard: 'It sounds like your concern is that we'd be repeating a past mistake.' That defuses tension. Then you can address the specific concern with data. I had a candidate once who used that exact approach and turned a shouting match into a productive 30-minute conversation. Luna: That's a powerful skill. So the through line here is empathy plus preparation. Lucas: Exactly. And that's what the interviewer is listening for. They don't care if you convinced someone — they care how you did it. Because that tells them how you'll operate in their organization. Luna: Great point. One last thing — any advice for virtual vs. in-person persuasion? Lucas: Yes. In virtual settings, over-communicate. Send a pre-read with your key data points. Use the chat to summarize agreements. And always turn on your video — facial cues help build trust. In person, you have more room for informal conversations before the meeting. Use that to gauge temperature. Luna: So the medium changes the tactics, but the core skill is the same. Lucas: Exactly. Alright, let's wrap with a quick recap. To answer 'tell me about a time you persuaded a skeptical stakeholder,' use STAR with a beefed-up action section: prepare, frame around shared goals, and adapt based on listening. Avoid painting the stakeholder as the villain. Keep it 90 to 120 seconds. And use that phrase 'I heard your concern, so I adjusted.' Luna: That's a solid framework. Thanks, Lucas. Lucas: Thanks, Luna. See you next time.