How to Answer "Tell Me About a Time You Influenced Without Authority"

Influencing without authority is the defining skill of modern knowledge work, where collaboration crosses team boundaries and most of the people you need to align don't report to you. This question tests whether you can drive change through persuasion, relationship-building, and strategic communication rather than formal power.

Your answer should demonstrate that you understand what motivates different stakeholders and can craft approaches that align their interests with your objective.

What Interviewers Are Really Assessing

• Persuasion skills: Can you make a compelling case that changes minds?
• Empathy and perspective-taking: Do you understand what motivates others and tailor your approach accordingly?
• Coalition building: Can you assemble supporters rather than going it alone?
• Strategic communication: Do you know when to use data, stories, or relationships to influence?
• Persistence without pushiness: Can you maintain influence efforts over time without alienating people?

How to Structure Your Answer

Cover: (1) the change you wanted to drive and why you lacked formal authority, (2) your understanding of the stakeholders' motivations, (3) the influence strategy you used, and (4) the outcome.

Sample Answers by Career Level

Entry-Level Example

Situation: Convinced the engineering team to prioritize a bug fix your department cared about. Answer: "A recurring bug was causing our customer success team to spend 10 hours per week on manual workarounds, but engineering kept deprioritizing the fix because it wasn't a customer-facing issue. I had no authority over the engineering backlog. I started by understanding engineering's perspective: they were measured on customer-facing bugs and feature velocity, and internal tools weren't in their OKRs. I reframed the problem in their language. I calculated that the bug indirectly caused 15% of support escalations because our manual workarounds sometimes introduced errors. I presented this to the engineering manager as a customer-facing issue, not an internal one. I also offered to write the bug report with exact reproduction steps and acceptance criteria—reducing the engineering effort needed. The engineering manager moved it into the next sprint, and the fix eliminated both our 10-hour workaround and the customer-facing escalations. The key was speaking engineering's language and removing friction from their path to yes."

Mid-Career Example

Situation: Drove adoption of a new tool across three departments that didn't report to you. Answer: "I identified that our project management was fragmented—engineering used Jira, marketing used Asana, and sales used spreadsheets. This caused constant miscommunication and duplicate work. I had no authority over any department's tool choices. I used a three-step influence strategy. First, I built relationships with one champion in each department by understanding their specific pain points—engineering hated status update meetings, marketing couldn't get visibility into engineering timelines, and sales needed real-time project updates for client conversations. Second, I set up a pilot using a unified tool with five volunteers (not management—frontline contributors who felt the pain daily), demonstrating that it solved each department's specific frustration. Third, I had the pilot participants present results to their own departments—peer influence is stronger than outsider advocacy. Within two months, all three departments had voluntarily migrated. I never asked anyone's manager to mandate the change; I made the new approach so clearly better that adoption was voluntary."

Senior-Level Example

Situation: Convinced the board to change the company's pricing model. Answer: "As VP of Product, I believed our per-seat pricing model was limiting growth—large enterprise prospects balked at the cost projection for 500+ users. I had no authority over pricing; that was jointly owned by the CEO and CFO. I built my influence campaign over three months. First, I gathered data: I analyzed every lost enterprise deal and identified pricing model (not price level) as the top objection in 60% of cases. Second, I found external validation—I interviewed pricing consultants and brought in a benchmark study showing that usage-based pricing increased enterprise close rates by 40% in comparable SaaS companies. Third, I built an internal coalition—I got the VP of Sales to co-sponsor the proposal because her team was losing deals, and I got the VP of Engineering to confirm that usage metering was technically feasible within one quarter. When I presented to the CEO and CFO, it wasn't my idea—it was a cross-functional recommendation supported by data, industry benchmarks, and an implementation plan. They approved a pilot, and within six months the new pricing model had increased enterprise deal size by 35%."

Common Mistakes to Avoid

• Using manipulation instead of influence: Influence is transparent and respectful. If your approach involved deception or political maneuvering, choose a different example.
• Ignoring stakeholder motivations: Pushing your idea without understanding what the other person cares about is advocacy, not influence.
• One-and-done approach: Significant influence usually requires sustained effort over time—multiple conversations, building evidence, and earning trust.

Practice This Question

Ready to practice your answer with real-time AI feedback? Try Revarta's interview practice to get personalized coaching on your delivery, structure, and content.