This one sounds friendly until you try to answer it. A hiring manager asks you to describe a time you persuaded someone, and every story you reach for sounds either too small (you got a teammate to switch tools) or too aggressive (you “won” an argument). Both fail the same way — they show you talking, not listening, and influence at work is mostly the second thing. This guide walks through how to answer describe a time you persuaded someone using an influence STAR structure, with 15 sample answers built around the move interviewers actually score: understood the other side first, then changed the frame.
Why interviewers ask this
Persuasion questions look like communication questions. They are not. They are influence-without-authority probes — the interviewer wants to know whether you can move a decision when you do not control the budget, the org chart, or the calendar. Cross-functional roles live or die on that skill. PMs persuade engineers, engineers persuade PMs, designers persuade execs, account managers persuade procurement. The candidate who can describe a clean version of this move will not need three escalation calls to unblock a roadmap.
There is a second test running underneath: whether you treat persuasion as manipulation or as a conversation. Adam Grant’s HBR piece “Persuading the Unpersuadable” puts it bluntly — effective persuasion is not strong-arming someone into a new view, it is establishing common ground, listening to their position, and finding ideas that resonate with both sides. Robert Cialdini’s research catalogs six principles — reciprocity, commitment, social proof, authority, liking, and scarcity — but the operative insight across forty years of his work is that people change their minds when they feel understood, not when they feel cornered. Skip the listening step and the interviewer reads “I steamrolled someone.”
The STAR framework
STAR works here, but the action beat looks different from a “challenge” question. The move you are narrating is a sequence: listen, pivot, agree. Roughly 15% situation, 10% task, 60% action, 15% result.
Situation (two sentences). Who was the person, what were they resisting, and what did you need from them. Skip the org chart trivia and name the stake — what would have broken if they had not moved.
Task (one sentence). Your specific lift. “I needed our CFO to approve a 30k tooling spend mid-quarter.” Without the specificity the example feels like a group effort and the signal evaporates.
Action (four to six sentences). Where the influence move shows. The structure that lands: I started by understanding their position (one sentence — what were they actually worried about?), I changed the frame using data, a story, or a small commitment (two to three sentences — Cialdini’s reciprocity and commitment principles live here), and I gave them an off-ramp so saying yes did not cost them face (one sentence). The interviewer is listening for the listening step. Skip it and you lose the question even when the outcome was a win.
Result (two sentences). What they decided, what changed downstream, ideally one number. End with the follow-through — “I sent a one-pager after the call” — because persuasion without follow-up reads as luck.
15 sample answers
Each example leads with the listening step, then the pivot, then the agreement. Aim for 60–90 seconds spoken, roughly 75 words on the page. Pick the persona closest to your own and rewrite around your story.
PM persuading a skeptical exec. “Our VP wanted to kill a discovery sprint because nothing had shipped in six weeks. I asked what she would need to see to keep it alive — she said pipeline impact. I dropped the broader research and ran two customer interviews she could attend personally, framed as a ‘sanity check.’ She heard one quote that lined up with a deal she was closing. The sprint got another quarter, and the feature landed in three of the four next-quarter renewals.”
Engineer persuading a PM on tech debt. “My PM kept deprioritizing a refactor because it had no user-facing outcome. I stopped pitching the refactor and asked which features on his roadmap were running late. Two of the three depended on the module I wanted to rewrite. I rebuilt the proposal as ‘unblock Q3 features’ with the dependency map on one slide. He moved it to the top of the next sprint and both features shipped on time.”
Designer persuading a founder. “Our founder wanted a dense, text-heavy homepage. I did not argue. I asked which three competitor sites he admired, screenshotted the white-space ratio on each, and put them next to a mock of our page in his preferred style. He saw the gap himself in the meeting. We shipped the lighter design and homepage conversion went up 22% in the first month.”
Account manager persuading a customer. “A renewal contact wanted to drop two seats because his team was not using the AI features. I asked which workflows his team actually ran daily, mapped three of them to features they had not turned on, and offered a 30-minute training instead of a discount. He kept all seats, training hit 80% attendance, and the account expanded by four seats the next quarter.”
Engineer persuading a vendor. “Our cloud vendor kept pushing a more expensive ‘reliability’ tier. I asked their SE which specific incidents in our account would have been prevented by the upgrade. He could name two. I built a smaller mitigation plan that addressed those two, ran it past their architect, and got it signed off as ‘equivalent reliability.’ We stayed on the lower tier and saved $84k for the year.”
Marketing lead persuading legal. “Legal wanted to kill a campaign over an ambiguous claim. I went in assuming they were right and asked what wording would work. They flagged exactly two phrases, not the whole creative. I rewrote both lines in front of them, got verbal approval on the call, and launched two days behind schedule instead of two weeks. Pipeline target landed at 108%.”
Career switcher persuading a hiring manager. “Switching from teaching to product, the hiring manager kept circling back to my lack of B2B SaaS experience. I asked which part of the job worried her most. She said stakeholder management. I walked her through a parent-teacher-admin conflict I had mediated and mapped each role to a SaaS counterpart. She offered me the role the next day with a note that the mapping had made the difference.”
Recent graduate persuading a senior engineer. “As an intern I needed a senior engineer to review a PR he kept deprioritizing. Instead of pinging him a fourth time, I asked which of his tickets I could take off his plate. I picked up a docs ticket, finished it in a morning, and pinged him after. He reviewed my PR that afternoon and became my mentor through the rest of the internship.”
Engineering manager persuading a director. “My director wanted to pull two engineers off my team for a ‘critical’ side project. I asked what success looked like in 30 days. He could not name it. I offered one engineer for two weeks with a clear deliverable instead. He took the deal, the deliverable shipped, and my team kept the other engineer for a launch that hit on time.”
Data scientist persuading a CFO. “Our CFO would not approve a $40k experimentation tool. I stopped citing features and asked what ROI threshold would unlock the budget. He said 3x in six months. I ran one manual A/B test that quarter without the tool, showed the result, and extrapolated the cost of doing ten more by hand. He approved the tool the same week.”
Sales rep persuading procurement. “Procurement pushed for a 12-month deal instead of the 24 my champion wanted. I asked the buyer what the renewal risk concern was — turnover on their side, not us. I rebuilt the proposal with a six-month opt-out clause inside a 24-month term. Procurement signed in three days and the account renewed in full at month 24.”
Support engineer persuading product. “A bug kept getting deprioritized because only three customers had reported it. I pulled the support ticket data myself and showed it correlated with a churn risk flag CS already trusted. I sent the join in a 200-word Slack message, not a doc. Product moved the fix to the next sprint and two of the three accounts gave us a renewal commitment within the month.”
Operations lead persuading a CEO. “Our CEO wanted a new-market launch in six weeks. I did not push back on the timeline. I asked which of the three workstreams he would be most embarrassed by if it slipped publicly. He named one. I ran a six-week plan on that workstream only and scoped the others to a fast-follow. Launch hit the date, the fast-follow shipped four weeks later, no public commitment slipped.”
Designer persuading research. “Research wanted four weeks of generative interviews before a redesign. We had two. I asked the lead researcher what minimum sample would still defend the recommendation. She said eight across three personas. We ran eight in nine days, the redesign shipped on date, and the method became the team default for tight-timeline projects.”
Engineering lead persuading a peer team. “Another team kept pushing back on a breaking API change my team needed. I dropped my proposal and asked their tech lead to walk me through their migration cost. It was lower than I had assumed. I offered to write the migration PR for their largest service myself. He agreed in the call, the API change shipped on schedule, and the two teams ran joint design reviews for two quarters.”
What NOT to say
The bad answers to this question all have one thing in common — they cast the interviewer as the next person you would steamroll.
- "I just told them they were wrong." The "I marched into the meeting and corrected them" opener tells the interviewer you mistake volume for influence. Even if you were right on the facts, the answer reads as someone who will be hard to manage.
- Manipulation framing. "I made them think it was their idea" or "I played to his ego" turns persuasion into a power move. Cialdini's principles work because they describe what already happens between trusting peers — not because they are tricks. If your story sounds like a trick, the interviewer hears red flag.
- No listening step. If the action paragraph never includes a sentence like "I asked them what they were actually worried about," the answer is broken. The listening sentence is the load-bearing beat of the entire move.
- No follow-through. "They agreed in the meeting" is not a result. Did the decision hold a week later? Did you document it? Did the metric move? Without follow-through, the interviewer assumes they would have changed their mind in the parking lot.
- Persuading someone with no real disagreement. "I persuaded my teammate to use the same naming convention" is not persuasion, it is alignment. Pick a story where the other person had a real reason to say no.
- The "stubborn boss" villain story. If 40 seconds are spent explaining how unreasonable the other person was, the interviewer notes how you will talk about them after the offer.
- No quantified result. "It went well" is not enough. A number — pipeline saved, hours unblocked, conversion lifted — turns the story from anecdote into evidence.
Closing move and practice routine
The line that converts a good persuasion answer into a great one: “and here is the rule I now follow when I need someone to move.” Something concrete — “I never pitch a solution before I have heard the actual objection,” or “I always offer the other side an off-ramp so saying yes is cheap.” That sentence is the operating-system upgrade the interviewer writes down. It tells them you have done this enough times to extract a pattern, not just remembered one story.
To practice: pick two real persuasion moments from the last 12 months — one senior, one peer. Draft the four STAR beats on an index card and circle the listening sentence. If you cannot point to a sentence that names what the other person was worried about, the story is not ready. Rewrite the action beat until the listening step is the first thing in it. Time the action paragraph out loud — under 30 seconds is too thin, over 90 is over-explaining.
Finally, rotate the same two stories against adjacent prompts — “tell me about a time you influenced without authority,” “tell me about a time you disagreed with a senior leader,” “tell me about a time you changed someone’s mind.” A clean influence story answers all three. Two well-rehearsed stories carry you through the behavioral loop; memorizing a fresh answer for each framing is the route candidates regret on the day.