Latest / The Tech Career Podcast with Fexingo: Engineering Jobs, Interviews, and FAANG Career Strategy / How FAANG Engineers Use Staff Engineers as Career Levers
Transcript
- Lucas: You're a senior engineer at a FAANG company. You've got four years of solid project delivery, your performance reviews are strong, and you've been told you're on the staff track. But you're stuck. And the conventional advice — find a mentor, get more visibility — isn't working. Today I want to talk about why that is, and what you should be doing instead. Luna: I feel like I've heard that exact frustration from a lot of mid-senior engineers lately. They're doing everything right on paper and nothing's moving. Lucas: Right. And the problem is that most engineers treat staff-plus promotion as a skill problem — they think 'if I just write better design docs or ship a bigger project, the title will follow.' But the real bottleneck isn't technical. It's relational. And specifically, it's about how you use the staff engineers already in your organization. Luna: Use them — that's a strong word. You're not talking about networking in the old 'buy them coffee' sense, are you? Lucas: Not at all. I'm talking about treating staff engineers as levers. Not mentors, not friends — levers. A lever amplifies force. A staff engineer can amplify your organizational influence, your visibility, and crucially, your permission to operate at a higher level. But you have to know what to ask for and when. Luna: So what's the typical mistake? I imagine a lot of people go to a staff engineer and ask for generic career advice. Lucas: Exactly. 'How did you get to staff?' is the worst question you can ask. It's too broad, it's self-serving, and it puts the staff engineer in a teaching role — which they're often tired of. A better ask is something like: 'I'm working on project X. I need to understand how this connects to the VP's priorities. Can you help me frame the impact in terms of quarterly business goals?' That's a specific, time-bound, leverageable ask. It gives the staff engineer a concrete way to help that also demonstrates your strategic thinking. Luna: Interesting. So the ask itself is a signal. You're showing you already think at their level, you just need a calibration. Lucas: Exactly. And the best staff engineers recognize that signal immediately. They'll invest in you because you're lowering the cost of their help. Now, the other side of this is something I call 'visibility debt.' Mid-level engineers often accumulate visibility debt — they do great work on a team, but nobody outside that team knows about it. A staff engineer can cancel that debt with a single mention in a leadership meeting. Luna: Visibility debt — I like that. So the lever is essentially a shortcut to organizational credibility. Lucas: Yes. And it's not about name-dropping. It's about having a staff engineer who can say, 'Luna on my team solved a similar latency problem last quarter — her approach might work here.' That kind of organic endorsement is worth more than a hundred self-promotion posts on the internal social network. Luna: How do you actually build that relationship without being transactional? Because it sounds like you're advocating for a pretty direct approach. Lucas: It's not transactional if you're genuinely trying to solve a problem the staff engineer cares about. The best staff engineers are overloaded. They have more asks than hours. So if you can show up with a well-scoped problem that aligns with their interests — maybe it's a scalability issue they've been worried about, or a cross-team dependency they need unblocked — you're not taking, you're offering. You become an asset to them. Luna: So the relationship is built on mutual leverage. You help them extend their reach, they help you extend yours. Lucas: Exactly. And that's the difference between a mentor and a sponsor. A mentor gives advice. A sponsor gives air cover. They put your name forward when you're not in the room. And that's what gets you promoted at the staff-plus level. Luna: I want to talk about the darker side of this. Not all staff engineers are good sponsors. Some are gatekeepers. Lucas: That's a critical point. There's a type of staff engineer who hoards context, who only brings in people who've 'paid their dues' in some opaque way. They'll give you busywork disguised as mentorship. How do you tell the difference early? Luna: I've seen this firsthand. A friend at a large cloud infrastructure company — I won't name the team — spent six months working on a pet project for a principal engineer, thinking it would lead to a staff promo. It never materialized. The principal just kept adding scope. Lucas: That's a classic pattern. The tell is whether the staff engineer is willing to put their reputation on the line for you. A good sponsor will say, 'I'm backing Luna for this initiative. She's ready.' A gatekeeper will say, 'Let's see how this next project goes.' Luna: So basically, if they're not willing to make a small bet on you publicly, within a reasonable timeframe, they're not actually sponsoring you. Lucas: Right. And you should set a time box. If after three months of working with a staff engineer you don't have a concrete example of them advocating for you in a meeting or an email thread, it's time to find a different lever. Luna: That's a hard conversation for a lot of engineers, though. They feel loyal, or they think it'll look bad if they switch sponsors. Lucas: It feels uncomfortable, but it's a normal part of career growth. Staff engineers themselves switch sponsors as they move up. The key is to have multiple relationships so you're not dependent on any one person. Diversify your leverage. Luna: Let's talk about a concrete example. Say you're a senior engineer on a data pipeline team at a FAANG. You want to move to staff. What's your first move with a staff engineer? Lucas: First, identify the staff engineer whose scope overlaps with your team's biggest pain point. Maybe it's a data reliability issue that's been causing incidents. Then, before you approach them, do your homework. Understand what they've worked on, what their current priorities are, and where they've publicly expressed frustration. Then frame your ask around that. 'I've noticed we've had three outages this quarter due to schema changes. I have a proposal for a validation layer that could prevent them. Could I get twenty minutes to walk you through it and get your feedback on the design?' Luna: That's specific, it's low effort for them, and it shows you've already done the thinking. Lucas: Exactly. And if they're interested, they'll often want to be more involved. Then you've got a sponsor who's invested in your success because it's also their success. Luna: One thing I want to push back on — this sounds very individualistic. What about team dynamics? If you're seen as playing politics, it could backfire. Lucas: That's a fair concern. But I'd argue that the alternative — quietly doing good work and hoping someone notices — is a slower path that often leads to frustration. The key is to make your work visible without making yourself seem self-promoting. Having a staff engineer advocate for you is the least political way to get visibility, because it's third-party validation. Luna: I think that's actually a really important point for listeners who are skeptical of 'playing the game.' It's not about gaming the system; it's about making the system work for you. Lucas: Exactly. And the system is designed to reward people who can influence outcomes beyond their immediate team. That's what staff engineer means. So learning to use staff engineers as levers is not just a career hack — it's a core competency for the role you're trying to get. Luna: I want to talk about one more thing before we wrap. The timing. When should you start building these relationships? Lucas: Yesterday. But seriously, don't wait until you're up for promotion. Start when you're a mid-level engineer. The staff engineers you build relationships with early will be principals and directors by the time you're ready for staff. And they'll remember that you were the person who brought a well-scoped problem to them three years ago. Luna: It's like compound interest for your career network. Lucas: Exactly. And the best part is, it's a skill you can practice. Every time you interact with a staff engineer, ask yourself: 'Did I make it easy for them to help me? Did I offer something in return? Did I leave them with a positive impression?' Luna: You know, this kind of conversation is exactly why people tell us they keep coming back to this show. We try to give you something usable, not just interesting. Lucas: And that's only possible because we keep the show ad-free. A couple of bucks a month from listeners is genuinely what makes that sustainable — buy me a coffee dot com slash fexingo, if you've gotten something out of these episodes. Luna: It's a small thing that adds up. We appreciate everyone who chips in. Lucas: Alright, back to the tactical side. One more pattern I see a lot: engineers who approach staff engineers only when they need something. That's a mistake. Luna: Right, you have to maintain the relationship even when you don't have an immediate ask. Lucas: Exactly. Send a quick note when you see a paper or a talk that relates to their interests. Share a small win that their advice helped with. Keep the connection warm. Then when you do need a lever, it's already there. Luna: That's good advice. I think a lot of engineers underestimate how much staff engineers value being kept in the loop on interesting technical work. Lucas: They do. And it's a two-way street. The more you can be a useful node in their network, the more they'll invest in you. Luna: So to sum up: identify the right staff engineers, make specific asks that show strategic thinking, offer mutual value, and maintain the relationship over time. Lucas: That's the framework. And if you do it well, you'll find that the staff-plus promotion comes not because you asked for it, but because people already see you operating at that level. Luna: I think that's a great note to end on. Thanks, Lucas. Lucas: Thanks, Luna. And thanks to our listeners. See you next time.