Latest / The Tech Career Podcast with Fexingo: Engineering Jobs, Interviews, and FAANG Career Strategy / How FAANG Engineers Use Mentorship to Accelerate Their Careers
Transcript
- Lucas: So we talk a lot on this show about getting into FAANG — interview prep, negotiating offers, surviving the first ninety days. But there's a topic we've danced around without directly addressing, and it's one of the biggest levers for actually growing once you're inside. Luna: Let me guess — mentorship? Lucas: Exactly. And I don't mean the generic 'find a mentor' advice you see on LinkedIn posts. I mean a specific, repeatable system for using senior engineers to shortcut your own learning curve. Because the truth is, at companies like Google or Meta, the people who advance fastest aren't always the ones who code the most — they're the ones who learn the unwritten rules fastest. Luna: Right. There's a huge gap between what's in the onboarding docs and what actually gets you promoted. And a mentor can bridge that. Lucas: Yeah. Let me give you a concrete example. When I joined Google as a software engineer, I was assigned a 'peer buddy' — essentially someone to help with logistical stuff. But my real mentor was a staff engineer named Priya who I reached out to on my own. I'd noticed her code reviews were incredibly thorough, and she had a reputation for shepherding projects through the launch process. Luna: How did you approach her? I imagine senior engineers are busy. Lucas: They are. So I did two things. First, I spent two weeks reading through her past design docs and code reviews. I wanted to show I'd done my homework. Then I sent her a short email — three sentences — saying I admired her work on the storage layer, and asking if she'd be open to a thirty-minute chat about how she approaches system design. I made it clear I wasn't asking for a long-term commitment upfront. Luna: That's smart. You're respecting her time and proving you're serious. Lucas: Exactly. She agreed, and that thirty-minute chat turned into a monthly meeting that lasted two years. And the single most valuable thing she taught me wasn't about code — it was about how to frame my work for promotion. She showed me how to write a promotion packet that tells a story, not just a list of features shipped. Luna: Can you share an example of that framing? Lucas: Sure. I had built a tool that automated a bunch of manual testing. I thought the impact was obvious — saved hundreds of engineer-hours per quarter. But Priya pointed out that my packet sounded like a maintenance task. She helped me reframe it as a reliability initiative that reduced production incidents by forty percent. Same work, completely different narrative. Luna: That's a huge difference. And that's exactly the kind of insight you can't get from a book or a blog post. Lucas: Right. And the interesting thing is, the best mentors often come from outside your immediate team. Because they have no stake in your internal team politics — they can give you brutally honest feedback. Luna: I've heard that called 'career sponsorship' versus 'mentorship' — someone who actively advocates for you when you're not in the room. Lucas: That's a crucial distinction. A mentor gives advice. A sponsor puts their reputation on the line to recommend you for a promotion or a stretch assignment. The best relationships evolve from mentor to sponsor over time. Luna: So for someone listening who's at a FAANG or a large tech company — how do they actually find that person? Cold emailing a staff engineer can feel intimidating. Lucas: It is intimidating. But here's a framework I've seen work. Start by identifying three engineers whose work you genuinely admire. Not just because they're famous — because their projects align with what you want to learn. Then do reconnaissance: read their design docs, look at their recent code reviews, check if they've given internal tech talks. Luna: So you're basically building a case for why that specific person is a good fit. Lucas: Exactly. Then you reach out with a very specific ask. Not 'will you be my mentor?' — that's too vague and too heavy. Instead, 'I'm working on X problem and saw how you handled Y in your project Z. Could I buy you coffee for twenty minutes to ask about your approach?' It's low commitment and targeted. Luna: And if they say no? Lucas: That's fine. Move to the next person. But in my experience, senior engineers are surprisingly open to these conversations — as long as you've done your homework. The ones who say no are usually too swamped, not uninterested. Luna: There's also the reverse mentorship angle, which I think is underrated. I've seen junior engineers mentor senior folks on new technologies or different perspectives. It can be a great way to build relationships upward. Lucas: Totally. I had a colleague at Amazon who was an L4 engineer but knew Kubernetes inside out. He started a lunch and learn series, and pretty soon senior engineers from other teams were coming to him for advice. That visibility helped him get promoted faster than anyone expected. Luna: So mentorship doesn't have to be hierarchical. It's really about exchanging value. Lucas: Right. And I think that's the part that gets lost in the typical career advice. People think mentorship is about finding a wise elder who dispenses wisdom. But the best mentor-mentee relationships are genuinely reciprocal. Even if you're junior, you bring energy, new ideas, and sometimes a fresh perspective on problems the senior engineer has been staring at too long. Luna: If today's tech conversation gave you something usable — that idea of targeting specific mentors with specific asks, or the reframing trick for promotion packets — and you'd like to help keep this show ad-free and independent, listeners can support us at buy me a coffee dot com slash fexingo. It's a small gesture that goes a long way toward keeping these deep dives coming. Lucas: Yeah, we really appreciate that. And it helps us spend more time researching episodes like this one. Luna: Alright, back to the nuts and bolts. Let's talk about how to structure a mentorship meeting once you've landed one. Lucas: Good. Because the first meeting sets the tone. I recommend coming with a one-page document — not a slide deck, just a simple doc — that outlines what you're working on, where you're stuck, and what you want to learn. Send it to the mentor at least twenty-four hours in advance. Luna: That shows respect for their time and makes the conversation productive from the first minute. Lucas: Exactly. Then during the meeting, take notes. Actual notes — not just mentally. I used to type bullet points into a private doc. And at the end, I'd always ask: 'What's the one thing you think I should focus on between now and our next chat?' That gave me a clear action item. Luna: And then you actually do it, right? That's the part people skip. Lucas: Absolutely. Nothing kills a mentorship faster than showing up next time having ignored the previous advice. You don't have to follow it blindly, but you should at least try it and report back on what happened. That shows you value their input. Luna: I've also seen people use mentorship meetings as accountability check-ins. Like, 'I said I'd refactor the module by this week — here's how it went.' That builds trust. Lucas: Totally. And over time, that trust can turn the relationship into sponsorship. I've seen mentors write strong promotion recommendations for mentees who consistently followed through. Luna: Let's talk about the other side — being a mentor. What do you get out of it as a senior engineer? Lucas: A lot, actually. First, teaching forces you to articulate your own knowledge, which deepens it. I've had moments where explaining a design pattern to a junior engineer made me realize my own understanding had gaps. Luna: That's the Feynman technique in action. Lucas: Exactly. Second, mentoring is one of the fastest ways to build a network across the company. People remember who helped them early in their career. And third, it's explicitly valued in promotion criteria at most FAANGs. Being a 'force multiplier' — someone who grows others — is a key signal for senior and staff levels. Luna: So it's almost a no-brainer. If you want to get promoted, start mentoring. Lucas: Within reason. Don't take on so many mentees that your own work suffers. But one or two focused mentoring relationships can absolutely accelerate your career as much as the mentee's. Luna: What about mentorship programs that companies run formally? Are those worth joining? Lucas: Mixed bag. Formal programs are great for getting started — they remove the awkwardness of cold outreach. But they often pair people based on availability rather than genuine interest. I'd use them as a starting point, but don't stop there. The most impactful mentorships are the ones you build yourself. Luna: So the takeaway is: be proactive, be specific, and be reciprocal. Lucas: Exactly. And don't forget that mentorship can happen in both directions. If you're a junior engineer, you have things to offer too. And if you're a senior engineer, investing in mentorship is one of the highest-leverage things you can do for your own growth. Luna: Great episode. I think we've given listeners a concrete playbook. Lucas: Yeah. Next time, let's talk about something we get asked a lot — how to handle the situation when your mentor leaves the company. That's a whole other dynamic. Luna: Sold.