Tell Me About A Time You Persuaded Someone: The Influence Story

You have a story ready for this one. You pushed an idea, someone pushed back, and eventually they came around. So you tell it that way: here is what I wanted, here is why they were wrong, here is how I got my way in the end.

And the interviewer's face goes flat.

Here is the problem. When you frame a persuasion story as a fight you won, you tell the interviewer exactly what they are afraid of: that you are the person who wears people down until they give up arguing. That is not influence. That is attrition. And nobody wants to hire the colleague who turns every decision into a standoff.

The reframe: Persuasion is not winning an argument. It is helping someone see that what you want and what they want are the same thing. The candidates who nail this question do not sound like they won. They sound like they built agreement.

Let me show you how to tell an influence story that makes an interviewer think "I want this person in the room when we disagree."

What This Question Actually Tests

"Tell me about a time you persuaded someone" is a proxy for a real workplace fear. Most work does not happen through authority. You need the budget owner to fund your project, the engineer to prioritize your ticket, the skeptical VP to back your recommendation. None of them report to you. So the interviewer wants to know: when you do not have the power to force a decision, can you still move it?

That means this question is about three things:

• Do you understand what other people care about, or only what you care about?
• Can you make your case in their language, not yours?
• Do you build durable buy-in, or temporary compliance that unravels the moment you leave the room?

Notice what is not on that list: being right. Being right is table stakes. The interviewer assumes your idea had merit. What they are testing is whether you can get merit adopted.

The Unlock: Start With Their Incentives

Before you pick a story, learn the question that separates strong influence answers from weak ones. Weak answers start with "I believed X, so I set out to convince them of X." Strong answers start somewhere else entirely.

The question to ask first: What would success look like to them? Not to you. To them. If you cannot answer that, you are not persuading. You are just repeating your opinion louder.

The person you are trying to move has their own scoreboard. The budget owner is measured on cost control. The business-unit head is measured on hitting a number this quarter. The engineer is measured on system stability. When your ask threatens their scoreboard, no amount of logic will move them, because you are asking them to lose so that you can win.

The unlock is to find the version of your idea that helps them win too. Once you understand their incentives, persuasion stops being a battle and becomes a translation problem.

Three Approaches To Influence

There is no single right way to persuade. The approach depends on why the person is resisting. Here are the three that cover most situations, and I coach candidates to name the one they used so the interviewer sees deliberate judgment, not luck.

1. Data-Driven Persuasion

Use this when the resistance is about uncertainty. The other person is not opposed to your idea, they are unconvinced it will work. Your job is to lower their risk with evidence: a small pilot, a benchmark, a proof of concept they can inspect. You are not arguing. You are showing.

The trap here is drowning them in numbers. Data persuades when it is aimed at the one question keeping them up at night, not when it is comprehensive.

2. Empathy-Driven Persuasion

Use this when the resistance is about the person, not the idea. Maybe they feel ownership over the current approach. Maybe a past project burned them. Maybe they were not consulted and the resistance is really about respect. Here, more data makes it worse. What moves them is being heard first: acknowledging their concern out loud before you make your case. People say yes to those who make them feel understood.

3. Stakeholder Alignment

Use this when no single person can say yes, or when the decision touches several teams. Here persuasion is less about one conversation and more about assembling agreement piece by piece: talking to each stakeholder in their own terms, surfacing the shared goal, and letting momentum build so that saying yes becomes the safe choice. This is closely related to how you answer a leadership interview question through influence, where you lead without formal authority.

An Example: Winning Over A Data-Resistant Stakeholder

Here is an anonymized story from a candidate I coached, an analyst on a revenue team at a large company. Early in their career, junior, no authority. They had spotted that the company was throwing away a category of data after a short window, and that keeping it would unlock better forecasting. The problem: storing it cost real money, and the business-unit head who controlled that budget had already said no. His scoreboard was cost. Their ask was a cost. A non-starter.

Most candidates would keep re-explaining the analytical upside. My client did something better. They asked themselves what success looked like to the business-unit head, and the answer was not "better data." It was hitting his forecast without surprises, the thing his own boss judged him on.

So the analyst did not argue. They ran a small proof of concept on their own, collected a limited sample of the data quietly, and built a working demonstration of the forecast the retained data would produce. Then they went back, not with a request, but with a picture: here is the number you are accountable for, here is how much tighter we can call it, here is what it costs to get there. Same data. Completely different frame. Reframed from "an expense for my project" to "a tool for the outcome you are judged on."

The shift that changed the outcome: The analyst stopped selling their idea and started selling his result. The cost did not change. The story about the cost did. That is the whole game.

He said yes, brought it to leadership, and the change became standard practice across the org. Notice the shape of this: it is not a story about a stubborn person being defeated. It is a story about finding the frame in which everyone wins.

One coaching note that matters for how you tell it: describe the other person coming around, not getting crushed. When you frame the stakeholder as finally seeing the light or being unhappy about it, you throw them under the bus, and the interviewer wonders how you will talk about them one day. Say "he bought into why this mattered," not "he finally admitted I was right."

The Full Sample Answer

Here is how that story sounds in an interview, structured as Context, Actions, Results. Keep the context tight, spend your time on the actions, and land a measurable result.

"Early in my career I was an analyst on a revenue team, and I noticed we were discarding a category of data after a short window. Keeping it would have made our forecasts meaningfully tighter, but storing it carried a real cost, and the business-unit head who owned that budget had already turned the request down.

My first instinct was to make the analytical case harder, but I stopped and asked what success looked like from his seat. He was accountable for hitting his forecast without surprises. So the data was not the thing he cared about. Forecast accuracy was.

Rather than ask again, I ran a small proof of concept on my own. I collected a limited sample, built the forecast the retained data would produce, and showed side by side how much tighter we could call his number. Then I met with him and framed it entirely around his goal: here is the accuracy you are accountable for, here is what it costs to get there. I also acknowledged his original concern about spend directly, because it was a fair one.

He bought into it and took it to leadership, and we made retaining that data standard practice. Within two quarters the team's forecast error dropped by a meaningful margin, and the approach was adopted across other business units. I am happy to share more on how we ran the pilot."

That answer works because the persuasion is invisible. There is no argument, no winner, no loser. There is a person who understood what someone else needed and built the case in those terms. The overlap with a good conflict resolution story is not accidental: both come down to empathy plus a shared goal, not force.

The Traps That Sink Persuasion Stories

Even a real influence story falls apart when it hits one of these. Watch for all three.

Steamrolling. If your story is about how you kept pushing until the other side gave up, the interviewer hears "hard to work with." Persuasion that relies on persistence alone is just pressure. Show that the other person's mind changed, not that their resistance ran out.

Making it about being right. The moment your story becomes "and I proved them wrong," you have lost. Nobody wants a teammate whose wins require someone else's public loss. Frame the outcome as shared: we found the better path, they came around, the org benefited.

No measurable outcome. "So eventually they agreed with me" is not a result. It is where the interviewer stops listening. What did the agreement produce? A number, a shipped project, a policy that stuck. Persuasion without a result is just a conversation. Persuasion with a result is impact.

The bottom line: A strong influence answer proves you can move a decision you do not control, in a way that leaves the other person on your side afterward. Understand their incentives, translate your ask into their language, and end on a measurable result.

Your Next Step

Pick one story where you moved someone who did not have to say yes. Before you rehearse it, write one sentence: what did success look like to the other person? If you can answer that clearly, you have an influence story. If you cannot, pick a different one.

Then build it into your broader prep, because the same story often doubles as a leadership or collaboration example depending on how you frame it. The five-story method shows you how to prepare a small set of versatile stories that cover persuasion, leadership, conflict, and more without memorizing a script for every question.

If you want a second set of eyes on your influence story before the interview, book a consultation and we will pressure-test it together, so you walk in sounding like the person other people want in the room when they disagree.