Influence and Persuasion Questions
Moving others toward a decision or direction through reasoning, evidence, and framing rather than positional power. Covers building an evidence-based argument and appealing to the other party's motivations, influencing peers and stakeholders over whom you have no formal authority through coalitions, credibility, and traded priorities, and driving organization-level direction across multiple teams as a technical or people leader. Spans the full spectrum from individual persuasion through lateral influence-without-authority to org-scale influence and leadership altitude.
Tell me about a time you needed another function to change its plan or invest time in your initiative, but you did not have formal authority over them. How did you learn what mattered to them, and what did you do to earn their support?
Sample Answer
Situation: I needed the Support team to invest time in a new escalation process, but I had no formal authority over them.
Task: My job was to earn their support instead of asking for compliance.
Action: I started by learning what mattered to them. I met with the support manager and a few frontline agents to understand their pain points. The main issue was that they were already overloaded, so any new process had to save time, not add work. I then reframed my initiative in their language. Instead of talking about my project milestones, I showed how the change would reduce repeat tickets and make it easier to resolve customer issues on the first contact. I also offered a small pilot so they could test the idea before committing fully.
Result: Because I tied the request to their goals and reduced the burden, they agreed to participate and became active partners in the rollout.
What I learned is that influence comes from understanding the other function’s priorities, showing respect for their constraints, and making the benefit concrete.
Think of a time you tried to persuade someone of something and it didn't work. What happened, and what did you take away from it?
Sample Answer
A strong answer here names a persuasion attempt that genuinely failed, not a near-miss that secretly worked out, and shows real self-awareness about which specific part of the approach was wrong. The most useful version separates whether the argument itself was flawed from whether the delivery, timing, or audience was wrong, and ends with a concrete change in habit, not a vague lesson like 'communicate better.'
What makes this answer land
| Weak pattern | Strong pattern |
|---|---|
| A "failure" that quietly turned into a win by the end | A genuine failure with a real cost, acknowledged plainly |
| "They just didn't get it" | Names the specific gap in the argument or delivery |
| "I learned to communicate better" | Names one concrete habit that changed afterward |
| Blames the audience's receptiveness | Owns the specific move that didn't land |
- Pick something real. Interviewers can usually tell when a "failure" is a disguised success story, and it undercuts exactly the self-awareness signal this question is testing for.
- Diagnose the layer that actually failed: was the underlying analysis incomplete, or was the argument sound but delivered to the wrong audience, at the wrong time, or without the stakeholder who actually needed to be in the room?
- Separate content failure from relationship failure. Sometimes the analysis holds up fine but the way it was delivered damaged the relationship; sometimes the analysis itself was missing something the audience cared about.
- Show the specific, durable change: a new step you now take before making this kind of case, not a general resolution.
Worked example
A proposal to delay a planned platform investment, based on a sensitivity analysis (testing how much the projected return changes if you vary each key assumption one at a time, to see how dependent the conclusion is on any single guess) showing the near-term return was marginal and dependent on assumptions that hadn't been stress-tested, is presented to the finance and marketing leads. They prefer to proceed as planned, because a related campaign is already scheduled and partially committed.
What failed: the presentation covered the numbers thoroughly but never addressed the operational cost of delay (the campaign disruption, the vendor commitments already in motion) that actually mattered most to the people in the room. It was treated as a numbers argument when, for this audience, it was really a timing and operational-risk argument.
After the decision goes ahead as originally planned, the presenter requests short one-on-ones with both decision-makers, acknowledges directly that the proposal hadn't accounted for the operational costs they cared about, and asks what evidence would have actually been persuasive. Both say, essentially, "show me the two paths side by side, including what breaks if we shift the timeline," not just a return estimate.
The concrete change: the presenter builds a revised model that explicitly includes rollout timing and a phased option, and adopts a standing habit of mapping each audience's specific operational constraints before making a numbers-only case in the future. On a later, related decision, the phased framing is adopted from the start.
Trade-offs and pitfalls
- Choosing a "failure" that's really a near-win undercuts the whole point of the question; interviewers are listening for a real cost, not a happy ending in disguise.
- Blaming the audience's receptiveness instead of naming what was actually missing from the case reads as a lack of self-awareness, which is the opposite of what this question is testing for.
- Being genuinely honest about what went wrong carries some risk in the room, but a story with no real cost to the narrator tends to read as evasive rather than reassuring.
You are leading a strategic initiative with multiple executives sponsoring different parts of the work, and they disagree on success criteria halfway through. How would you bring them back to alignment, make decision rights explicit, and keep the teams executing while the debate is resolved?
Sample Answer
I would first separate disagreement on the outcome from disagreement on the method. Then I would bring the executives into a short decision session with a one-page brief: the business goal, the options, the trade-offs, and the decision needed. I would make decision rights explicit using RACI, which means Responsible, Accountable, Consulted, and Informed. That way, everyone knows who recommends, who decides, and who simply needs to stay informed.
For example, if one sponsor wants speed, another wants cost savings, and a third wants risk reduction, I would ask which metric is the tie-breaker if they conflict. I would propose a shared scorecard with 2 or 3 measures, such as revenue impact, operational risk, and delivery date, then ask the accountable executive to make the final call in writing.
While the debate is happening, I would keep teams executing on work that is not dependent on the unresolved choice, pause only the parts that could be wasted, and communicate a clear interim plan. The goal is to prevent thrash, protect momentum, and get everyone back to one set of success criteria.
For example, on a customer-onboarding automation initiative, three executives disagreed about halfway through: the VP of Engineering wanted to prioritize system reliability given a recent outage, the VP of Finance wanted to prioritize cost savings from reduced manual onboarding labor, and the VP of Risk wanted to prioritize compliance controls given a pending audit. In the decision session, the RACI mapping made the VP of Product the accountable decision-maker, with all three VPs as consulted. The proposed scorecard used three metrics: onboarding error rate (tied to reliability), manual labor hours saved per month (tied to cost), and number of unresolved audit findings (tied to risk). The accountable VP decided that the audit-findings metric was the tie-breaker for this quarter, since the audit deadline was fixed and immovable, while the reliability and cost metrics would be weighted equally starting the following quarter. While that decision was being finalized in writing, the teams kept building the shared onboarding data pipeline, which every option needed regardless of the outcome, and paused only the specific reporting dashboard whose design depended on which metric ultimately won.
A launch depends on a partner company or external vendor, and they are missing deadlines that put your roadmap at risk. You do not have direct authority over them. What would you do in the first week to protect the launch, rebuild alignment, and decide whether the original plan is still realistic?
Sample Answer
In the first week, I would focus on protecting the launch while testing whether the plan is still realistic.
Day 1 and 2: I would get the facts. What is late, what is truly on the critical path, and which milestones depend on the partner. I would also ask for a written status update so there is one shared view of the problem.
Day 3 and 4: I would reset alignment with the partner and internal leaders. I would make the risk visible, propose a recovery plan, and define what needs to happen by when. If needed, I would narrow scope, add internal backup work, or create a phased launch so the entire roadmap is not blocked by one dependency.
Day 5: I would decide whether the original date is still credible. If the partner has recovered, I keep the plan. If not, I recommend a revised timeline with clear trade-offs, rather than hoping the delay disappears.
The key is to avoid passive waiting. Even without direct authority, I can protect the launch by clarifying ownership, escalating early with options, and keeping leadership informed with facts instead of optimism.
For example, in a case like this, the launch depended on a third-party payments provider delivering a new API endpoint that a checkout redesign needed to go live. On Day 1, the written status update from the vendor's account manager revealed the endpoint was not late by a day or two, it was still in the vendor's own internal QA with no committed date, three weeks past their original commitment. By Day 3, resetting alignment meant a joint call with the vendor and internal engineering leadership where the risk was made explicit: without the endpoint, the full checkout redesign could not ship on the original date. The recovery plan split the work: internal engineering built a fallback that used the vendor's existing, older endpoint for most transaction volume, while the new endpoint's remaining edge cases, a smaller set of international payment methods, were scoped out of the initial launch and phased in once the vendor delivered. On Day 5, the vendor still had no firm delivery date for the new endpoint, so the recommendation was to launch on the original date with the phased fallback rather than slip the whole roadmap, with a follow-up launch for the remaining payment methods once the vendor's endpoint actually shipped.
Tell me about a time you influenced a peer, another team, or a stakeholder you don't manage, without relying on your title or position. What was the situation, what tactics did you use, and what was the outcome?
Sample Answer
Direct answer
Influencing without authority means moving a decision using credibility, evidence, and reciprocity instead of a title. It's the same underlying competency whether the question calls it "influence" or "persuasion": build credibility before you need it, lead with the other person's problem, bring evidence or a low-cost prototype instead of an opinion, and find an ally rather than going in alone.
Structured elaboration
Core tactics:
- Build credibility before you need it. A track record of reliable delivery makes the ask land differently than the same ask from a stranger.
- Lead with their problem, not yours. Frame the ask around what the other person is trying to accomplish.
- Bring evidence or a prototype, not an opinion. A small, low-cost demonstration beats an argument every time.
- Trade, don't demand. Small, genuine reciprocity works better than a favor you feel owed.
- Find one ally before the room. A two-person ask lands differently than a solo one.
Where this shows up. The same competency gets asked about in several shapes:
| Framing | Same underlying ask |
|---|---|
| "Define influence vs. persuasion, give one example of each" | A conceptual wrapper around the same no-authority competency; don't overthink the definitional split |
| A PM adds a complex metric to the roadmap you don't control prioritization over | Influencing a decision you don't own uses the same tactics |
| "List four methods of influence without authority" | Answered directly by the tactics above |
| An IC earning a seat at product discussions | Through data, a prototype, or direct outreach, not through title |
| An IC building a case to a hiring manager or recruiter to change interview criteria | Influence without authority applied to a hiring decision |
| A mid-level engineer with limited formal authority | Mobilizing resources and buy-in for a small cross-functional improvement |
| A mid-level analyst's plan to influence roadmap decisions | Using analytics as the lever, with measurable signals of growing influence over time |
Worked example
Situation. On a platform team, a senior engineer with no authority over product prioritization noticed a shared upload flow causing repeated failures in a "quick-share" feature product wanted to ship as-is to hit a deadline.
Stakes. Shipping as-is risked a visible failure at launch, but the prioritization decision belonged to product, not engineering.
The influence moves.
- Led with credibility already in the bank: a track record of shipping reliable pieces of the same service, so the ask wasn't coming from a stranger.
- Brought evidence, not opinion: existing logs showing the retry-failure rate on the current flow.
- Built a small, low-cost prototype of just the two risky steps instead of asking for a full rewrite.
- Found an ally: a designer who had already flagged the same UX friction independently, turning a solo request into a two-person, cross-functional ask.
- Framed the pitch around product's incentive (a clean launch) rather than engineering's preference for correctness.
Resolution. Product accepted a scoped fix instead of the full reuse plan, without needing an executive to force the decision.
What a senior candidate does differently. Names the specific tactic used (evidence, prototype, ally, incentive-framing) rather than saying "I just talked to them and they agreed," and can say what they'd have done if it hadn't worked, since escalation is a last resort, not a first move.
Trade-offs and pitfalls
- Persistence is not influence. Repeating your opinion louder doesn't count.
- One tactic alone is weaker than combining them. A common weak answer only ever mentions "I built a good relationship" with nothing concrete behind it.
- Escalating too early burns the informal-influence capital that made the peer relationship work in the first place.
Unlock Full Question Bank
Get access to all 23 Influence and Persuasion interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.