A good answer to “Tell me about a time you persuaded someone” shows a method, not a victory. Interviewers want to hear that you understood the other person’s position, built your case around what they cared about, made it easy for them to agree, and respected their decision. Whether you “won” matters less than how you went about it.
Below are three illustrative answers at different career stages, each annotated, followed by the patterns they share and the follow-up questions to prepare for.
What interviewers are listening for
The UK Civil Service, which assesses this behaviour under the heading Communicating and Influencing, defines it as: “Communicate purpose and direction with clarity, integrity and enthusiasm. Respect the needs, responses and opinions of others.” Its indicators for Executive Officer roles include “listen to and value different ideas, views and ways of working”, “respond constructively and objectively to comments and questions” and “handle challenging conversations with confidence and sensitivity”.
That last word, sensitivity, is the one many candidates miss. A story about outlasting someone in an argument shows persistence, not persuasion. In most strong answers you can hear four moves:
- Understand: you found out why the other person held their view.
- Frame: you made your case in terms of their priorities, not only yours.
- Lower the risk: you offered a trial, a fallback or a smaller first step.
- Respect the decision: you left the choice with them and accepted the outcome.
The Association for Project Management makes a related point about stakeholders: “Project success means different things to different people.” Persuasion usually starts by finding out what success means to the person you need to convince.
Example 1: early career, persuading a manager to change a routine
Illustrative answer for an administrative or receptionist role:
“At the clinic where I worked on reception, visitors signed a paper book. It was often illegible, and when we had a fire drill nobody could quickly see who was in the building. I thought we should use the visitor sign-in feature in the building system we already had.
My manager wasn’t keen. When I asked why, she said many of our visitors were elderly and she worried they’d find a tablet confusing. That was a fair point, so I suggested a two-week trial in which I would sign in anyone who preferred not to use the tablet, and keep the paper book as a backup. I also printed the fire-drill list from both systems so she could compare them.
After two weeks, most visitors had used the tablet without help, and the digital list took seconds to print. She agreed to switch, and we kept a small paper form for anyone who asked for it.”
What makes it work:
- The candidate asked why the manager objected before pushing harder. The objection then shaped the proposal.
- The trial lowered the risk and left the final decision with the manager.
- The evidence (the fire-drill list) mattered to the manager’s own responsibilities, not just to the candidate’s convenience.
- The paper form shows the candidate kept something of the manager’s concern in the final solution.
A weaker version would say: “I explained the benefits several times until she agreed.” It shows persistence, not influence, and tells the interviewer nothing about method.
Example 2: mid-career, persuading a senior stakeholder with data
Illustrative answer for a business analyst role:
“Our sales director wanted to run a 20% discount across all regions to lift a slow quarter. My analysis of the last two promotions suggested discounts had mostly pulled forward sales that would have happened anyway, and had reduced margin.
I knew a slide headed ‘Why this is a bad idea’ wouldn’t get far. His target was revenue, so I started there. I showed him the revenue in the month after each previous promotion, when sales had dropped below normal, and what that did to the quarter overall. Then I suggested a test instead of a straight no: run the discount in two regions for three weeks and compare them with two similar regions without it.
He agreed to the test. The discount regions sold more during the promotion but the gap closed within a month, and margin was lower. He decided not to roll it out nationally and asked me to look at a targeted offer for lapsed customers instead.”
What makes it work:
- The candidate framed the evidence around the director’s goal (revenue), not their own concern (margin) alone.
- Proposing a test turned a confrontation into a shared experiment, and the director kept control of the decision.
- The result is specific, and the follow-on request shows the relationship survived the disagreement.
MIT’s career advisers recommend that most of a STAR answer focus on your actions and that you use “I” statements to show ownership. This example does both: the situation takes two sentences, and every step after that is something the candidate did.
If you are applying for analytical roles, the business analyst resume builder shows how to describe recommendations that changed a decision as measurable achievements.
Example 3: when persuasion only partly worked
Illustrative answer for a customer service team leader:
“We were getting around forty calls a week from customers who couldn’t reset their passwords, because of a fault in the reset email. I wanted IT to fix it in the next release, but their queue was full and they’d rated it low priority.
I asked the IT lead how they scored priorities. It was mostly on how many users were affected and whether there was a workaround. Our call logs only showed ‘login problem’, so I spent a week tagging the calls properly and calculated how much agent time they used. I also pointed out that our workaround meant agents resetting passwords by hand, which the security team didn’t like.
He moved it up, but not into the next release; it was scheduled for the one after. In the meantime he gave us a safer manual process. I’d hoped for a faster fix, but I understood his other items were affecting more customers. Since then I tag our call reasons more precisely, so I have the data ready before I ask.”
What makes it work:
- The candidate learned the other team’s decision rules and gathered evidence in that form.
- The outcome is honest: a partial win, accepted with good grace and a reason.
- The final line shows a lasting change in how the candidate works.
Partial wins often make better answers than complete ones, because they show you can influence without needing to win every point. They also prepare you for the follow-up question “What would you have done if they had said no?”
Customer service candidates can back up this kind of story on their CV; the customer service resume builder includes ways to describe call-reason analysis and cross-team fixes.
What different audiences tend to care about
The table below is general editorial guidance for planning your example, not a rule. Its purpose is to remind you to frame your case for the person in front of you.
| Who you are persuading | What they often care about | Evidence that tends to help |
|---|---|---|
| Your manager | Team targets, risk, their own reporting upwards | A small trial, a clear plan, what it means for their targets |
| A peer in another team | Their own workload and priorities | How it saves them effort, data in the format they use |
| A senior leader | Outcomes, cost and timing | A short summary, one key number, a recommendation with options |
| A customer or client | Their problem, budget and confidence in you | Their own situation reflected back, a fair comparison of options |
What does not count as persuasion
Some stories sound like persuasion but show the opposite. Avoid examples that rely on:
- Rank or pressure: “I told the junior staff it was mandatory.”
- Going over someone’s head first: escalating before you have tried to understand the other person.
- Wearing someone down: repeating the same argument until they give in.
- Selective evidence: leaving out data that weakened your case. If the interviewer asks a probing question, this will show.
- Pressure sales: for customer-facing roles, closing a sale the customer later regretted is not an example to use.
Is this the same as “Tell me about a time you disagreed with your manager”?
The two overlap, but the emphasis differs. The disagreement question is mostly about how you handle conflict with authority, including how you behave when the decision goes against you. The persuasion question is mostly about your method of influence, and the person you persuaded can be anyone: a peer, a customer, another department. If you are likely to face both, prepare separate examples. Example 1 above would suit either question; Example 3 is a better fit for persuasion because the person was outside your reporting line.
Follow-up questions to prepare for
- “What would you have done if they had said no?”
- “Were you ever wrong about something you persuaded someone to do?”
- “How did you know what mattered to them?”
- “Tell me about a time someone persuaded you to change your mind.” Interviewers sometimes use this to check that influence works in both directions for you. Have a short example ready.
Frequently asked questions
Does the person have to have agreed with me in the end?
No. A partial agreement, or a respectful “no” after a well-made case, can be a strong answer if you show a sound method and accept the result. A complete win achieved by pressure is a weaker answer.
I work in sales. Can I use a sales example?
You can, but sales interviewers hear many of them. Consider an internal example as well, such as persuading a product team or a manager, to show you can influence people who are not buying from you.
What if I persuaded someone and it turned out to be the wrong call?
It can still be a useful story if you describe what you learned and how you put things right. Keep it for the follow-up question about being wrong, rather than leading with it.
Sources
- Success Profiles: Civil Service behaviours (UK Cabinet Office, GOV.UK)
- 10 key principles of stakeholder engagement (Association for Project Management)
- Using the STAR method for your next behavioral interview (MIT Career Advising and Professional Development)