Latest / The Tech Career Podcast with Fexingo: Engineering Jobs, Interviews, and FAANG Career Strategy / How FAANG Engineers Navigate Political Landmines in Cross-Team Projects
Transcript
- Lucas: You can be the best engineer on your team — write the cleanest code, ship the most features — and still get stuck at senior. The thing that unlocks staff level is almost never more technical skill. It is learning how to navigate the political landscape of a large organization. Luna: That's a bold claim. Are we talking about office politics in the cynical sense, or something more structured? Lucas: More structured. I want to talk about what I call 'influence without authority' — the skill of getting things done when you don't have formal power over the people you need to collaborate with. And I have a recent case from Meta that makes it concrete. Luna: I'm listening. What happened at Meta? Lucas: Early this year, a team inside Meta needed to migrate a core data pipeline from one internal infrastructure system to another. Sounds like a straightforward engineering project. But the migration touched five different teams — each with their own roadmap, their own deadlines, their own incentives. The lead engineer on this was a senior named Priya, and she had zero authority over any of those teams. Luna: So she's stuck. She needs other teams to change their priorities for her project, but their managers are measured on their own deliverables. Lucas: Exactly. And this is where the framework comes in. Priya used a four-step approach. Step one: map the stakeholders. Not just who's on the other teams, but what each person cares about — their incentives, their fears, their career goals. Step two: find the win-win. For one team, the migration actually fixed a performance issue they'd been complaining about for months. For another, it reduced their on-call burden. Priya identified those overlaps. Luna: That sounds like basic project management, but also… it's not. Most engineers skip the mapping part because it feels like gossip or manipulation. Lucas: Right. But if you frame it as a design problem — you're designing a system of human incentives — it becomes engineering-adjacent. Step three: build coalitions. Priya didn't try to convince everyone at once. She started with the team that had the most to gain, got them on board, and used that momentum to sway the next team. Step four: communicate with data. Luna: What does that look like in practice? Lucas: She created a shared dashboard showing each team's migration status, including the concrete benefit they'd see — like latency reduction or fewer pager alerts. So when she asked for a meeting, she led with the data that mattered to that team. Not 'help me because my project is important,' but 'your team will get a 20 percent reduction in weekly incidents.' Luna: That's a lot better than asking for a favor. But is this really political? Sounds more like good communication. Lucas: It's both. The political part is the unavoidable truth that different teams have competing priorities. Pretending that doesn't exist is naive. The skill is aligning those competing priorities with your own goal — and doing it transparently. Priya never hid her agenda. She just framed it in terms of shared value. Luna: So what was the outcome of the migration? Lucas: It shipped two weeks ahead of schedule. And Priya got promoted to staff a few months later. Her promotion packet specifically highlighted her ability to lead cross-team initiatives. That's not a coincidence. Luna: I buy that this works inside Meta, but what about smaller companies where the politics are less formal? Lucas: Actually, it's even more important in smaller companies. At a startup, you might have to convince the CTO and the VP of Product without any organizational structure to fall back on. The same framework applies — map, find win-wins, build coalitions, use data. The difference is the scale of the stakeholders, not the approach. Luna: Let's talk about a common pitfall. I've seen engineers try this and come off as manipulative. Where's the line? Lucas: The line is intent. If you're genuinely trying to find outcomes that benefit everyone, that's not manipulation — that's collaboration. The problem is when you frame a win-win that only benefits you, or when you hide the real cost to the other team. Priya was honest about the migration effort required from each team. She just also showed them the upside. Luna: So transparency is the guardrail. Lucas: Exactly. And it's also a forcing function for yourself. If you can't honestly articulate why this project helps the other person, maybe you shouldn't be asking them to prioritize it. Luna: That's a good rule. So for someone listening who's a senior engineer gunning for staff, what's the one takeaway? Lucas: Start practicing influence without authority now. Look for a cross-team project — even a small one — and deliberately apply this four-step framework. The technical work is table stakes. Your ability to align people is the differentiator. And if today's conversation gave you something useful, honestly, that's the kind of thing that makes this show worth supporting. Luna: Yeah, if you found value in this episode, consider throwing a coffee our way at buy me a coffee dot com slash fexingo. It keeps the show ad-free and focused on content like this. Lucas: Anyway, back to the practical side. One more thing about the mapping step — I recommend using a simple spreadsheet. List each stakeholder, their primary incentive, their potential resistance points, and the win-win you can offer. Keep it updated as the project evolves. Luna: That's surprisingly concrete. I might try that myself. Lucas: Do it. And next episode, I want to talk about something that came up on the listener feedback line — how to handle the politics of performance reviews. Because that's another place where influence matters more than your actual output. Luna: Looking forward to it. For now, start mapping those stakeholders.