To answer “tell me about a time you persuaded someone,” pick a story where you changed a decision you had no authority to make, show that you understood the other person's concerns before you made your case, and back that case with evidence they cared about. Interviewers are testing influence without authority: whether you can move people with listening, data and a low-risk proposal rather than pressure or escalation. End with a measurable result and what happened to the working relationship afterward.
What is the interviewer really testing when they ask this?
Almost every job involves getting people you do not manage to do something differently. A peer owns the code you need changed, a manager controls the budget, a client signs off on the plan. This question checks how you handle that, and it usually appears under labels like influence, communication, collaboration or leadership.
Some companies spell the value out. Amazon's Leadership Principles, for example, include “Have Backbone; Disagree and Commit,” which asks people to challenge decisions respectfully and then commit fully once a decision is made (as of October 2026). Most interviewers listen for five signals:
| Signal | A strong answer shows | What sinks it |
|---|---|---|
| Empathy | You found out why the other person held their view, and you say why it was reasonable | The other person is described as stubborn or clueless |
| Evidence | Numbers, a pilot or an example that addressed their specific worry | “I explained my point of view several times” |
| Influence, not authority | You changed the decision through the merits and the framing | You went over their head or leaned on your title |
| Judgment | The change was worth the effort and you lowered the risk of saying yes | A trivial win, or a fight you picked for its own sake |
| Relationship | The person stayed an ally, or became one | You won the point and lost the colleague |
If the question is specifically about pushing back on your own boss, the emphasis shifts toward respect and commitment; our guide to answering “tell me about a time you disagreed with your manager” covers that version.
How do you answer “tell me about a time you persuaded someone”?
Use the STAR method, but put most of your time into the Action, because that is where the persuasion happens. This six-step frame keeps the story focused:
- The decision and the stakes. One or two sentences: who, what they wanted to do, and why it mattered.
- Their position, stated fairly. Why their view made sense from where they sat.
- How you learned what they cared about. A question you asked, a conversation you had before pitching anything.
- Your evidence, framed in their terms. Data, a prototype or a comparison that answered their concern, not just yours.
- A low-risk way to say yes. A pilot, a reversible first step, a compromise, or work you took on yourself.
- The result and the relationship. A number, plus how you work together now.
Aim for about two minutes. Our guide on how long a STAR answer should be breaks down the timing for each part.
Three example answers we wrote
These are examples we wrote to show the structure, not real candidates' answers. Swap in your own story, numbers and wording.
Example answer we wrote: persuading a peer (software engineer)
Situation: I was a backend engineer on a six-person payments team. A senior engineer who owned our deploy pipeline preferred one large weekly release. Our last two releases had each needed a rollback that took around three hours.
Task: I had no authority over the pipeline, but I wanted us to move to smaller daily deploys behind feature flags.
Action: Before pitching anything, I asked him what worried him about smaller deploys. His concern was fair: more deploys could mean more on-call pages, and he carried the pager most weeks. So I pulled six months of incident history and showed him that 9 of our 11 rollbacks came from releases with more than 20 changes. Instead of asking for a full switch, I proposed a four-week pilot on one low-risk service, offered to build the flag tooling myself, and agreed in advance that we would go back if pages increased. I posted weekly numbers in the team channel so he did not have to take my word for anything.
Result: The pilot service shipped 19 small deploys with zero rollbacks and no rise in pages. He presented the results at our planning meeting and proposed extending the approach to every service himself. Within a quarter, our average rollback time fell from about three hours to under 20 minutes, and we now co-own the deploy runbook.
Example answer we wrote: persuading a manager (data analyst)
Situation: I was a data analyst at an online retailer. My manager wanted to launch a redesigned checkout to all customers before the holiday season, based on a handful of positive usability sessions.
Task: I believed we needed an A/B test first, and I had to make that case without looking like I was blocking a launch he had already promised to leadership.
Action: I asked him which date actually mattered. It was having the new checkout live by November 15. So I built a plan around his deadline rather than against it: a 50/50 test starting October 20, one agreed success metric (checkout conversion) and one guardrail (refund rate). I showed him a one-page estimate that two weeks of our traffic was enough to detect a 2% change. Then I framed it in his terms: if the design won, he would walk into the leadership review with proof instead of a prediction.
Result: He agreed. The new design raised desktop conversion by 3.1% but cut mobile conversion by 4.2%, because a key address field fell below the fold on smaller screens. We shipped desktop on time, fixed mobile within a week and then shipped it too. He now asks for a test plan on every checkout change, and he asked me to write the team's experiment checklist.
Example answer we wrote: persuading a senior stakeholder (product manager)
Situation: I was a product manager at a B2B software company. Our VP of Sales wanted my team of five engineers to build a custom reporting feature for a single prospect. It would take about eight weeks and delay a roadmap item that 60 existing customers had requested.
Task: I needed to persuade her to accept an alternative without putting the deal or our relationship at risk.
Action: I met her one-on-one and asked what the prospect needed the report for. It turned out their buyer had to show monthly usage to their CFO. I checked with engineering and confirmed that a scheduled CSV export plus a template dashboard would cover that need in under two weeks. I brought her a side-by-side comparison: time, cost and the 60 waiting accounts for each option. I also offered to join the prospect call myself to walk the buyer through the export, so the risk of the switch did not sit only with her.
Result: She agreed to pitch the export. I joined the call, the buyer accepted it, and the deal closed a month later. The roadmap feature shipped on schedule, and the export became a standard feature that the sales team has since used in other deals.
Weak vs strong answers
| Part of the answer | Weak | Strong |
|---|---|---|
| Opening | Three minutes of background on the project | The decision, the person and the stakes in two sentences |
| Their view | “He just didn't get it” | “His concern was fair: he carried the pager” |
| Evidence | Your opinion, repeated more firmly | Data or a pilot aimed at their specific worry |
| The ask | All or nothing | A reversible first step with an agreed exit |
| Result | “Eventually they came around” | A number, plus what the other person did next |
| Tone | Victory lap | Credit shared; the other person looks good too |
Follow-up questions to expect
Interviewers often probe one layer deeper. Have a sentence ready for each:
- What would you have done if they had still said no?
- How did you find out what they actually cared about?
- Was there a point where you considered escalating? Why didn't you?
- Tell me about a time someone persuaded you to change your mind.
- Tell me about a time you tried to persuade someone and failed.
- Looking back, what would you do differently?
The “what if they said no” follow-up matters most. A good answer shows you would have committed to their decision, asked for a checkpoint to revisit it, and kept the relationship intact. For the failure version, our guide to answering “tell me about a time you failed” shows how to own an outcome that did not go your way.
Mistakes to avoid
- Winning by escalation. “I took it to their manager” is authority, not persuasion. If escalation was part of the story, it should be a last resort you agreed on together.
- Making them the villain. If the other person sounds foolish, the interviewer wonders how you will describe them next year.
- Persuading by persistence. Repeating your view until someone gives in is not a skill worth showcasing.
- Any hint of manipulation. Leaving out inconvenient data or overstating a benefit damages trust in your whole answer.
- A trivial topic. Convincing a teammate to try a new lunch spot will not show the skill. Choose something with real stakes for the team or the business.
- Ending at “they agreed.” Agreement is not the result. What changed because of it?
Persuasion stories overlap with leadership and conflict stories, so keep them distinct in your story bank. See how to answer the leadership question and how to describe a conflict with a coworker, and browse the full list of “tell me about a time” questions to see where each story fits. Related answers in this cluster: managing stakeholder expectations and explaining something complex to a non-technical person.
Practice it
Persuasion stories tend to run long, because the setup feels essential when you tell it. Say your story out loud, time it, and cut the background until the Action starts within 30 seconds. Draft the four parts in the free STAR story builder first if you are starting from scratch.
Then rehearse it under realistic conditions. A free AI mock interview built from your résumé and the job description asks the question out loud, listens to your spoken answer and scores it out of 10 with what to fix, so you can see whether your evidence and result land. It is free for 15 minutes a day with no account, which is enough to run this answer and two follow-ups.
Rehearse your persuasion story out loud
Answer the question by voice, get a score out of 10 with what to fix, and try again. Free for 15 minutes a day, no account needed.
Try a free AI mock interviewFAQ
What is a good example of persuading someone at work?
A good example is one where you changed a real decision you did not control, such as convincing a peer to adopt a new process, a manager to test before launching, or a stakeholder to accept a different solution. It should involve listening to their concerns, evidence and a measurable result.
Is "tell me about a time you persuaded someone" the same as the influence question?
Mostly. "Tell me about a time you influenced someone without authority" and "tell me about a time you convinced someone" test the same skill. The same story and structure work for all three.
Can I use a story where I persuaded my manager?
Yes, as long as you show respect for their position and their final call. Persuading a manager with evidence and a low-risk proposal is a strong story. Going around them is not.
What if I did not fully persuade the other person?
A partial win or a compromise can still make a strong answer, especially if you explain what you learned and how the relationship held up. If they said no outright, the story fits "tell me about a time you failed to persuade someone" better.
How long should my answer be?
Aim for about two minutes. Keep the situation to two or three sentences and spend most of your time on how you learned their concerns and made your case.
Should I use a story from outside work?
Only if you have little work experience, such as a student or new grad. A school, volunteer or club example works if the decision had real stakes and you can show a clear result.