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 Convince Someone
Transcript
- Lucas: So we've covered a lot of behavioral questions on this show, but there's one that keeps coming up in mock interviews and real ones too that we haven't drilled into yet. 'Tell me about a time you had to convince someone.' Luna: That's a good one. It's not just about conflict or disagreement, it's about persuasion. And that's a skill every hiring manager wants to see. Lucas: Exactly. And the reason it's a favorite is that it tests a few things at once. Can you influence without authority? Do you understand other people's motivations? And can you tell a story that shows your approach, not just the outcome. Luna: So what's the biggest mistake people make when they answer this? Lucas: The biggest one? They frame it as a battle. 'My manager wanted X, I wanted Y, and I won.' That's not persuasion, that's a power struggle. The interviewer doesn't care who was right; they care how you navigated the situation. Luna: Right. It's about showing you can move someone because you brought them along, not because you steamrolled them. Lucas: So here's a framework I like. Structurally, you still use the classic situation, action, outcome. But the action part is where you need to be really specific about your tactics. What did you actually do to bring that person around? Luna: Can you give us an example? Lucas: Sure. Let's say you're a product manager, and you need to convince a skeptical engineering lead to prioritize a new feature that you believe is critical for the next release. The situation is that there's a limited sprint capacity and she's not convinced this feature is worth the time. Luna: Okay, that's a classic tension. Lucas: So what do you do? First, you don't just push your opinion. You schedule a one-on-one to understand her concerns. You ask questions like, 'What would need to be true for this to feel like a priority to you?' And you listen. She might say something like, 'I'm worried about the technical debt, and we've got a big migration coming up.' Luna: So you're not leading with your own agenda. You're trying to see the situation from her seat. Lucas: Right. Then you can bring data to the table. Maybe you pull up a customer survey showing that this feature is the second most requested item, and you project that it could reduce churn by maybe five percent. But you don't stop there. You also address her concern directly. You say, 'I hear you on the technical debt. What if we scope it to a smaller first release, and we schedule a follow-up to tackle the refactor right after?' Luna: So you're offering a compromise that respects her priorities. Lucas: Exactly. And then you ask for a small trial. 'Can we do a one-day spike, just to see how it goes?' That gives her an easy yes. A small commitment is easier to give than a full-on sprint. Once the spike shows promise, she's more likely to buy into the larger effort. Luna: And the outcome? You can say, 'The feature shipped two weeks later, and early metrics showed a measurable drop in support tickets.' That's specific and shows business impact. Lucas: Exactly. And the key is that you changed the dialogue from 'my idea vs. yours' to 'how can we solve this together?' That's what you want to convey in your answer. Luna: That's a solid example. I have my own story from a while back that shows a different angle. I once had to convince a hiring manager to let me work remotely for a role that was strictly in-office. At the time, remote was not the norm. Lucas: Oh, that's a tough one. How did you approach it? Luna: Well, I didn't just say, 'I want to work from home.' I did my research. I found that the company had a project that would require late-night calls with a team in Asia, and I suggested that being remote would actually help with those hours. I also offered to come in twice a week for key meetings. Lucas: So you tied your request to a business need, not just your personal preference. That's a great move. Luna: Right. And I made it easy for him to say yes by proposing a trial period of a month. He agreed, and after that month, he saw that my productivity didn't dip. It actually became the norm for the team. Lucas: That's exactly the kind of story that shows adaptability and emotional intelligence. You're not just selling an idea; you're building a bridge to the other person's concerns. Luna: And you know, when I'm on the other side of the table now, I love hearing answers like that. It tells me the candidate knows how to communicate and collaborate under pressure. Lucas: So here's a quick tip for anyone preparing for this question: think of a time when you changed someone's mind on something important. It could be a colleague, a boss, a client, even a family member. The key is that you used a strategy, not just persistence. Luna: And maybe it's not always about winning. Sometimes the best outcome is a compromise that incorporates both perspectives. Lucas: Absolutely. And that's what we're here for, to help you think through these career moves and decisions. And we do this without any ads, which is a choice we've made from the start. If you find these episodes useful, and you'd like to support that ad-free mission, the link is buy me a coffee dot com slash fexingo. It's a small way to keep this going. Luna: Yeah, it really helps us keep the focus on the content, not on selling you something. So if you're in a position to do that, we appreciate it. Lucas: But back to the interview question. One thing I want to stress is that you should avoid the 'I was right and they were wrong' narrative. That's a red flag for interviewers. Luna: So what's the best way to frame a situation where you actually were right? Lucas: You can acknowledge the other person's perspective. Say something like, 'I understood why they were hesitant, given the risk, but I felt we could mitigate it with a phased approach.' That shows respect for their viewpoint while still making your case. Luna: And you should always end with a reflection. What did you learn from the experience? That's something we haven't mentioned yet. Lucas: Good point. Interviewers love seeing self-awareness. You could say, 'I learned that taking the time to understand the other person's constraints made my pitch stronger.' That little gem can set you apart. Luna: So to recap: use a specific story, focus on the tactics, show a collaborative spirit, and end with a lesson learned. That's a winning formula. Lucas: And if you're not sure which story to pick, think of one where you had to convince someone who was initially resistant. That resistance is what makes the story interesting. It shows you can handle pushback. Luna: And don't forget to quantify the outcome if you can. Did you save time, money, or improve a metric? Numbers make your story more credible. Lucas: Alright, so next time you're in an interview and they ask about a time you convinced someone, you'll be ready. Practice your story out loud, keep it under two minutes, and remember: it's not about winning an argument, it's about building alignment. Luna: And if you're on the other side of the table, you might just hear a great example of persuasion in action. Lucas: Thanks for listening, and we'll catch you next time on Interview Prep with Fexingo.