How to answer "Tell me about a time you persuaded someone" — understand the objection first

The candidates who struggle with this question usually tell a story about explaining themselves really clearly — as if persuasion is just a matter of stating your point well enough. Real persuasion almost always starts somewhere else: understanding why the other person disagrees in the first place. You can't change someone's mind if you don't know what's actually holding it in place.

Why interviewers ask it

Almost every job eventually requires getting someone — a stakeholder, a teammate, a customer — to agree to something they didn't start out wanting. This question checks for influence without authority (can you move someone who doesn't report to you?), empathy in an argument (do you actually engage with the other side, or just repeat your own point louder?), and judgment about when you're right (was the thing you persuaded them of actually a good idea?). A story that's really about winning an argument, rather than genuinely understanding and addressing someone's concern, misses what's being tested.

The framework: Read → Case → Shift

1. Read. What the other person's real objection or hesitation actually was — not the surface-level disagreement, but what was underneath it.
2. Case. How you built your argument specifically around that objection, using evidence or reasoning that spoke to their actual concern rather than a generic pitch.
3. Shift. What specifically changed their mind, and what happened as a result. A persuasion story needs a real, visible change in someone else's position.

The Read beat is what separates genuine persuasion from stubbornness. Anyone can repeat their opinion with more conviction. Understanding the actual, sometimes unstated reason someone is resisting — and building your case to address that specifically — is the harder and more convincing skill.

A worked example

"I wanted to move a manual weekly report to an automated dashboard, but a stakeholder who relied on it kept pushing back, and at first I assumed it was just resistance to change. When I actually asked why, it turned out her real concern wasn't the format — it was that the manual version let her ask me follow-up questions in the moment, and she was worried a dashboard would leave her stuck with no way to get context. Once I understood that, I stopped pitching the automation on speed and instead proposed keeping a fifteen-minute weekly sync alongside the new dashboard, specifically for those follow-up questions. That addressed the actual worry, not the one I'd assumed she had. She agreed to try it, the sync turned out to be useful for about six weeks before she stopped needing it, and the dashboard is still how that reporting gets done two years later."

Read (the real objection, discovered by asking, not assumed) → Case (an argument built specifically around that concern) → Shift (a real change in position, plus what happened afterward). The persuasion worked because it addressed the actual reason for resistance, not a guessed-at one.

Choosing the right story

Avoid a story where you were simply the loudest or most senior voice in the room — that's authority, not persuasion, and interviewers can usually tell the difference. The strongest choice is a moment where someone had a genuine, reasonable objection, and you changed their mind by actually engaging with it rather than overriding it. If you're deciding between a few options, the same test that helps pick a disagreed-with-your-boss story applies here — the version where the other person's perspective gets real airtime in your retelling, not just your own.

Common mistakes to avoid

• Skipping the other person's actual objection. A story that jumps straight to your argument, with no sense of what you were actually up against, is hard to evaluate.
• Confusing authority with persuasion. "I was the manager, so they went along with it" isn't a persuasion story — there was no mind actually changed.
• An argument that ignores their concern. Repeating your original pitch louder or with more data, without addressing what they were actually worried about, rarely works and reads as one-note.
• No real shift. A story where the other person's position never visibly changed isn't evidence of persuasion, however good the argument sounded.
• Picking a case where you were wrong. If hindsight shows the thing you persuaded them of was a mistake, it undercuts the story — pick one where the outcome actually held up.

The bottom line

"Tell me about a time you persuaded someone" rewards understanding over volume. Find out what the other person's real objection was, build your case specifically around it, and show the concrete shift that followed. That's a far more convincing demonstration of influence than any story about simply making your point well.

Related: What is your management style? · How do you handle criticism and feedback? · Why should we hire you?