Influencing Without Authority

How to show you can get people who do not report to you to adopt a change: understand their incentives, make yes easy, build support, and follow through.

Overview

Influencing without authority means getting people who do not report to you to change what they do: adopt a tool, follow a standard, fund a project, or accept a design. Most engineers need this skill, and it matters more as roles become more senior, because more of the work is changing what other teams do rather than writing the code yourself.

Interviewers probe it with questions about driving a change across teams, getting a standard adopted, changing the mind of someone more senior, or getting help from a team with no reason to prioritize you. They want to hear how you moved people when you could not tell them what to do.

The two common failures are opposite. One is borrowing authority you do not have: 'I told them it had to be done', or going straight to their manager. The other is giving up when the first conversation goes badly. Strong stories sit between those: you learned what the other people cared about, made it easy for them to say yes, built support one person at a time, and kept going until the change was actually in use, not just promised.

  • Their view — Describes the other side's concerns fairly — Calls them resistant or political
  • Tactics — Specific moves that made yes easier — 'I kept pushing'
  • Evidence — Data or a trial, not opinion — Arguments only
  • Follow-through — Measured real adoption — Stopped at verbal agreement
  • Judgment — Knew when to escalate or commit to another decision — Went around people

What you will be able to do

  • Tell an adoption or alignment story built on the other side's incentives.
  • Name the tactics that lower the cost of yes: tooling, pairing, trials, champions.
  • Handle the senior-disagreer and senior-blocker questions with a clear, respectful sequence.
  • Show you followed through to measured adoption, and could commit when you lost.

Interview questions

  • Tell me about a time you drove change across teams without authority over them.
  • How do you convince a senior engineer or manager who disagrees with your proposal?
  • Describe a time you got a new tool or standard adopted across an organization.
  • Tell me about a time you built a coalition to get something done.
  • How do you handle someone more senior who is blocking progress?

Sign up free to read the full topic

More Behavioral topics

Start free on Cariara · Coding problems · System design studio