Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Influenced Without Authority Question
Transcript
- Lucas: So you walk into a job interview, the hiring manager looks at you, and asks, 'Tell me about a time you influenced a decision when you didn't have formal authority.' Luna: That one always gets people. It's a top-three toughest behavioral question, right up there with failure and salary expectations. Lucas: And unlike the classic failure question, which we covered in episode 112, this one doesn't let you pivot to a lesson learned from a mistake. It's asking for pure persuasion skill when your title gave you no leverage. Luna: So what's the structure? I know listeners expect the STAR approach, but it can feel flimsy here if you don't pick the right story. Lucas: Right. The key is choosing a story where you genuinely had no authority — not a situation where you could have pulled rank but didn't. The algorithm that picks the strongest story has two parts: first, you were the most junior person in the room, or you were outside the reporting line. Second, you used something other than hierarchy — data, a prototype, an ally, or a clear business case. Luna: Can we walk through a real example? Something concrete that happened in the last year or two? Lucas: Sure. Let's use a product manager at a mid-sized SaaS company called BeaconPay. I'm anonymising it, but the core is real. The PM was about two years out of business school, working on the billing platform. The engineering team was building a new dashboard feature that the VP of Product really wanted — flashy, visible, could go in the release notes. Luna: Classic pet feature. Lucas: Exactly. But the PM had been digging through support tickets and discovered that a compliance update for payment data retention was about to become mandatory in three months. If they missed it, the company could face fines from the payment card networks — roughly fifty thousand dollars per violation. The dashboard feature had no revenue attached. Luna: So the PM needed to convince engineering to drop the shiny thing and do the boring compliance work. But they weren't the engineering manager's boss. Lucas: Right. So we can map this to the STAR framework. Situation: The company had a fixed roadmap for the quarter, and the engineering team had already committed to the dashboard. The PM discovered a compliance deadline that would create real financial risk. Task: They needed to get the team to reprioritize and slot the compliance work into the same sprint, even though the VP of Product was publicly excited about the dashboard. Luna: This is where action gets interesting. What did the PM actually do? Lucas: Three things. First, they gathered data — they pulled the actual compliance language from the card network, calculated the fine amount, and documented how many customers would be affected if data wasn't retained. Second, they found an ally — the head of legal, who had been quietly worried about the same deadline but hadn't raised it because legal isn't in the product prioritization meeting. Third, they presented a tradeoff, not a demand. They went to the engineering lead and said, 'Look, I know the dashboard is the priority. If we do the compliance work first, it's two weeks. Then you still have six weeks for the dashboard before the next release. Here's the data on the risk if we don't.' Luna: And did it work? Lucas: Yes. The engineering lead agreed to slot the compliance work into the next sprint. The dashboard shipped one sprint later than planned, but the VP of Product didn't care because the PM had already briefed her on the risk — so she was on board too. The PM effectively pre-sold the decision to everyone who mattered before the formal meeting. Luna: That's a great result. But what about the 'no authority' part? The PM was still a product manager, not a junior intern. Lucas: Fair point. But in that organization, PMs don't tell engineering what to build — they recommend. The engineering lead had the final say on sprint content. The PM had no dotted line, no budget authority, no ability to override. So it's a legitimate influence without authority story. And the STAR result is concrete: the compliance work was completed on time, zero fines were incurred, and the dashboard shipped the following release with no customer complaints. Luna: I like that the PM didn't just say 'I convinced them.' They built a coalition, used data, and framed it as a tradeoff. Lucas: One thing I'd add for listeners: the PM also admitted what they didn't know. They said to the engineering lead, 'I'm not a compliance expert, so I checked with legal to confirm the timeline.' That actually built trust. Acknowledging the limits of your expertise can make you more persuasive, not less. Luna: That's a smart counterintuitive point. So when you're crafting your own story, you want to show you did your homework but also that you knew when to ask for help. Lucas: Exactly. And speaking of homework, if this show has helped you think through a career move or an interview approach, we keep it going because listeners support us at buy me a coffee dot com slash fexingo. No pressure — just a low-key way to keep the episodes free for everyone. Luna: Yeah, it's how we stay ad-free. And we appreciate every single person who chips in. Lucas: So back to the STAR framework. One mistake I see candidates make is skipping the 'Task' part. They jump from 'here was the situation' straight to 'and then I did this.' But the task is what makes your actions make sense. Without it, the interviewer doesn't know what you were trying to achieve. Luna: Can you give a bad example? Lucas: Sure. 'In my last job, the team was working on a new feature, and I noticed we might miss a compliance deadline. So I talked to legal and engineering, and we reprioritized.' That's a story skeleton with no context. The interviewer hears it and thinks, 'Okay, but what were you responsible for? What was the specific ask?' Luna: Right. The task frames your personal accountability. Lucas: Exactly. So in the BeaconPay story, the task was clear: 'I needed to get the engineering team to reprioritize a sprint without having authority over them, and I had to do it in a way that didn't alienate the VP who wanted the dashboard.' That tells the interviewer exactly what you were up against. Luna: What about the 'A' in STAR? Action should be specific. The PM did three things — data, ally, tradeoff. That's much better than 'I communicated the issue.' Lucas: Yes. And the 'R' — the result — should answer the 'so what' question. Not just 'we shipped on time,' but 'we avoided fifty-thousand-dollar fines and shipped the dashboard without customer impact.' Numbers matter. If you saved money, say how much. If you influenced a decision that changed a process, say what changed. Luna: One thing I want to flag: the influence without authority question often comes up for roles that require cross-functional work — product management, program management, consulting, even some engineering roles. So if you're in any of those, you should have a story ready. Lucas: Absolutely. And don't be afraid to use a story from outside work if it's stronger. A volunteer project, a student organization, even a family situation — as long as it demonstrates the same skills. The interviewer mostly cares about the architecture of your thinking. Luna: But keep it professional if you can. A story about convincing your parents to let you study abroad might not land in a corporate interview. Lucas: Fair. Let's give listeners one more framework twist. There's a variation of this question that goes, 'Tell me about a time you had to persuade someone who disagreed with you.' That's a different flavor, but the same muscle. Luna: What's the difference? Lucas: The persuasion question implies active opposition, not just absence of authority. So your story should include a moment of direct disagreement. For example, maybe a stakeholder wanted to launch a feature with known bugs, and you had to convince them to delay. That takes more backbone. Luna: And you'd use the same STAR structure, but the action would emphasize how you handled the conflict. Lucas: Right. You'd say something like, 'I acknowledged their point first — I said, I understand why speed matters here. Then I showed the data on customer impact. And I offered a compromise: we launch to a small subset of users first.' That shows you can disagree without being disagreeable. Luna: So the key takeaway for today: when you get the influence without authority question, pick a story where you genuinely had no formal power, frame it in STAR, and be specific about your actions and results. Lucas: And practice it out loud. Your brain processes stories differently when you speak them versus when you write them. Record yourself on your phone, listen back, and cut any word that doesn't add value. Most people's first drafts are thirty percent too long. Luna: Good advice. I'd add one more thing: don't try to memorize a script. Know your bullet points — situation, task, action, result — and let the language come naturally. If you sound rehearsed, you lose the authenticity that makes the story believable. Lucas: That's the note. Next episode we will tackle another tough behavioral question — the one about dealing with a difficult stakeholder. Until then, keep practicing.