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

Show how you got people who didn't report to you to adopt your idea — through data, building a coalition, prototyping, or framing it around their goals, not commands. Interviewers assess persuasion and cross-team effectiveness. Avoid stories where you simply had the authority or the manager decided.

What the Interviewer Is Really Assessing

As engineers grow, impact increasingly comes from driving decisions across teams where you have no formal power. This question tests persuasion, building trust, and stakeholder management — Amazon's "Earn Trust" and "Ownership." It's especially common in senior and staff loops.

They want evidence you can change minds without a title: using data, prototypes, and a clear narrative; understanding what the other party cares about; and building a coalition rather than mandating. Stories where you had authority, or where a manager forced the outcome, miss the point entirely.

The STAR Structure

Influence runs on the other party's incentives, not yours. The Action section should show you framed the idea around what they cared about and lowered their cost of adopting it.

Situation: A decision needing buy-in from people you couldn't direct — another team, a skeptical senior engineer, a PM.
Task: The change you wanted to drive and why you lacked authority over it.
Action: Your influence tactics — data, a working prototype, framing around their incentives, recruiting an ally, lowering their adoption cost.
Result: They adopted it, and the measurable impact.

Sample Answer Outline

This outline leads with a working prototype and incident data, then frames adoption around each team's on-call pain — shifting the pitch from opinion to evidence so no mandate is needed.

S: "I believed three teams duplicating their own auth logic was causing bugs, but I owned none of those services."
T: "I wanted them to adopt a shared auth library I'd prototyped — without any authority to mandate it."
A: "Instead of pitching abstractly, I built a working prototype and migrated one team's lowest-risk service myself to prove the integration cost was ~2 hours. I quantified the duplicated bug count from incident history and framed adoption around each team's on-call burden, which is what they cared about. I got one respected senior engineer to champion it first."
R: "All three teams migrated within a quarter, auth-related incidents dropped noticeably, and the library became the org default. No mandate was ever needed."

Mistakes to Avoid

The disqualifying mistake is a story where you actually had authority or a manager forced the outcome. The whole point is persuading people you couldn't direct.

A story where you actually had authority or your manager forced the decision.
Persuading with opinion alone — strong answers use data or a prototype.
Ignoring the other party's incentives; influence requires framing around what they care about.
No measurable adoption or outcome.
Going over people's heads instead of winning them over.

ResuMax tailors your resume to each role, scores it like a recruiter, and preps you for interviews.

Practice with the interview coach

Frequently asked questions

How is this different from the leadership question?

Leadership can include authority; this specifically requires influencing people you couldn't direct. Cross-team or peer persuasion is the core.

What's the single most effective influence tactic?

For engineers, a working prototype plus data is hard to beat — it shifts the conversation from opinion to evidence and lowers the other side's adoption cost.

What if they ultimately said no?

A partial win works — one team adopting, or shifting the conversation. But the strongest stories end in real adoption you drove through persuasion.

Can a new grad answer this?

Yes — convincing teammates to adopt a tool, change a process, or accept a design in a project all count, even without seniority.

All behavioral questions