OfferDrill.

Interview questions

The hard ones

How to answer "tell me about a time you influenced someone without authority."

This is a story question, and most people answer it with a philosophy instead. Here's what the interviewer is listening for, the four things that sink the answer, and a structure you can fill with something that actually happened to you.

Why they ask it

Senior work almost never comes with the power to make people do things. You need the data team to prioritize your request. You need a peer in another department to change a process that's costing you two days a week. You need your own manager to back a decision they didn't think of. Nobody reports to you. The interviewer wants proof you can move things anyway.

Underneath that, they're checking two specific things. First, how you think about other people — do you see them as obstacles, or as people with their own pressures and goals? Second, whether you can hold a position without turning it into a fight. Someone who only wins by escalating to a boss is expensive to manage. So is someone who folds the moment they meet resistance.

There's a quieter reason too. This question is hard to fake. Anyone can say "I build relationships." Very few people can name the person, the disagreement, what they said on Tuesday that changed the person's mind, and what happened after. The detail is the test.

What not to say

"I believe influence is about building trust and relationships over time."

That's a philosophy, not a story. They asked for a time. An answer with no name, no date, and no specific request scores zero, and now you've used ninety seconds getting nothing.

A story where you eventually got your boss to force the outcome.

You just described using authority. It's the opposite of what they asked. If escalation was genuinely part of the story, that's fine, but the answer has to be mostly about what you did before that.

Making the other person sound stupid or obstructive.

Interviewers hear this more often than you'd think, and it lands badly every time. They don't know your old colleague, but they do know they might be your next colleague. Give the other person a real reason for their position, even if you disagreed with it.

A story with no resistance in it — you suggested something, everyone said yes, it worked.

That's not influence, that's a meeting. If nobody hesitated, there was nothing to overcome, and the story proves nothing. Pick one where somebody actually said no first.

How to build a strong answer

  1. Pick a story where someone genuinely disagreed with you.
    Go through your last two or three years and look for a moment you wanted something and a specific person didn't want to give it. A peer who wouldn't prioritize your ticket. A vendor who wouldn't change a term. A senior person who thought your approach was wrong. The disagreement is the whole point. If you're stuck, look for the times you were frustrated — frustration is usually a sign you were trying to influence someone and it wasn't working yet.
  2. Say what they wanted and why it was reasonable.
    This is the step almost everybody skips, and it's the one that separates a senior answer from a junior one. One sentence: "She was protecting her team's quarter, and she had three other requests ahead of mine." Now the interviewer knows you understood the other side. Everything you did next reads as strategy instead of pestering.
  3. Name the specific move that changed things.
    Not "I built consensus." What did you actually do? Did you bring numbers? Did you shrink the ask to a two-week pilot? Did you find out their real objection was something they hadn't said out loud? Did you go to someone they trusted first? One concrete action, described in plain words. That's the heart of the answer, and it should take about fifteen seconds to say.
  4. End with the outcome and stop talking.
    Say what happened and what it produced. Use the real number if you have one and say "I don't have the exact figure" if you don't — made-up metrics fall apart under one follow-up question. If the outcome was partial, say so. "I got about half of what I asked for, and that was enough to prove the case" is a strong ending. Then stop. Don't add a lesson unless they ask.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Mid-career, needed another team's engineering time and had no claim on it.

Last year I owned [the reporting project], and it was blocked on a data pipeline that only [the platform team] could build. Their lead told me no twice. He wasn't being difficult — his team was already committed for the quarter and my request would have cost them about three weeks. So I stopped asking for the full build. I went back and asked him what the smallest useful version looked like, and he said a manual export could work as a stopgap. I took that, ran it for a month, and brought him the usage data — [the actual number] of people pulling it weekly and two teams asking for more. At that point the build was easy to justify, and he put it in the next quarter's plan himself. It shipped in [month]. I think what worked was that I stopped arguing about priority and started making the case with something real.

The other person has a legitimate reason. The move is specific and repeatable — shrink the ask, gather evidence, come back. And the win ends with the other person choosing it, which is what influence actually looks like.

Early career, one internship or a first job, convinced someone more senior.

During my internship at [the company], I was doing [the data entry task] and noticed we were re-checking the same records twice because two people were working from different lists. I brought it up with my manager and she said it was fine, it had always worked that way, and she didn't want to change a process mid-quarter. Which was fair — she'd seen changes go badly before. So I tracked it for two weeks and found we were duplicating roughly [the number] records a week. I brought her the log, not an opinion, and suggested trying one shared list for a single week to see what happened. She agreed to the test. Duplicates dropped to almost nothing, and she kept it. I was there eight more weeks and it stuck.

Small stakes are fine. Nobody expects an intern to have moved a budget. What this shows is the same instinct: understood the objection, gathered evidence, asked for a test instead of a commitment.

You only partly won, or the story is about a peer who outranked you in practice.

At [the company] I pushed to change how we handled [the escalation process], because we were losing about [the number] of cases in handoffs. The person who owned that process was a peer, but she'd built it and she'd been there nine years. She thought the problem was training, not the process. I disagreed, but I couldn't prove it, so I asked if I could sit in on her team's handoffs for a week. I found she was partly right — about a third of the cases were training. So I went back with a proposal that covered both, and I let her own the training piece because that was her call to make. We got the process change through in [month]. I didn't get everything I wanted, and honestly I was wrong about some of it. But the fix held because she was behind it.

Admitting you were partly wrong is not a weak move here. It's the clearest possible proof you were listening rather than lobbying, and shared ownership is the most honest description of how these things usually end.

What comes next

Answer this one well and the interviewer usually goes here:

  • What would you have done if they'd still said no?
  • Have you ever tried this and failed to change someone's mind?
  • How did you handle the relationship afterward?
  • Tell me about a time you were the one who got persuaded.
  • How do you know when to stop pushing and escalate?
  • How would you do this with someone who's actively hostile to you, not just busy?

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

You've almost certainly done this — most people just don't recognize it as influence because it felt like a normal frustrating week at work, so go find that week and tell it plainly.