Latest / The Tech Career Podcast with Fexingo: Engineering Jobs, Interviews, and FAANG Career Strategy / How to Ask for a Promotion at FAANG
Transcript
- Lucas: You've been at a FAANG for about a year and a half. Your code ships on time, your bugs are average, you've got a solid relationship with your team. And you walk into your manager's office and say, 'I think I'm ready for promotion.' Luna: And the manager says... 'Show me.' Lucas: Exactly. And most engineers I've talked to don't have a good answer. They've been working hard, sure, but they haven't built the case. Today we're going to walk through exactly how to ask for a promotion at a FAANG company — and get it. Luna: And if this episode gives you something useful, consider supporting the show at buy me a coffee dot com slash fexingo — it keeps us ad-free and lets us do deep dives like this. Lucas: Absolutely. So let's start with a specific case. I've been following an engineer at Google — let's call him Ravi. He went from L4 to L5 in 18 months. That's faster than average, but it's not unheard of. What did he do differently? Luna: I'm guessing it wasn't just coding more hours. Lucas: No. In fact, his output in terms of lines of code was actually lower than some peers. But here's the key: every project he worked on, he made sure it tied directly to a measurable business metric. For example, he optimized a search ranking pipeline that improved click-through rate by 0.3 percent. That's a small number, but at Google's scale, it's millions of extra ad dollars. Luna: So it's about impact, not activity. Lucas: Right. And that's the first rule of the promotion packet. You need to document your accomplishments in terms of metrics that matter to the business. Not 'I wrote a new feature' but 'I shipped a feature that increased user retention by 2 percent over six months.' Luna: And that's the part most engineers skip. They think their work speaks for itself. Lucas: It doesn't, especially at a big company. Your manager might know you're good, but the promotion committee — the calibration panel — doesn't know you. They see a packet. And if your packet is just a list of tasks, you're dead in the water. Luna: Walk us through what a good promotion packet actually looks like. Say I'm a senior engineer at Amazon trying to go from L5 to L6. Lucas: Sure. The standard template at most FAANGs is: for each major project, write a one-paragraph summary that includes four things. What was the problem? What did you do? What was the measurable result? And how did you demonstrate leadership — mentoring, design reviews, setting technical direction. Luna: So it's not just your own work, it's how you elevated the team. Lucas: Exactly. For L5 to L6 at Amazon, they expect you to have influenced at least one team outside your own. So you might write: 'I led a cross-team initiative to reduce deployment failures by 40 percent, which saved an estimated 200 engineering hours per quarter across three teams.' That's concrete. Luna: Let's talk about timing. When do you even start this conversation with your manager? Lucas: Ideally, six months before the promotion cycle. At most FAANGs, there are two cycles per year. So if you're targeting the June cycle, you should have a conversation with your manager in January. Tell them, 'I want to be promoted in the next cycle. Can you help me understand what gaps I need to fill?' Luna: And if the manager says 'not yet'? Lucas: Then you ask for specifics. 'What exactly is missing? Can you point me to a successful L5 packet from someone else on the team?' One engineer I know did that and found out his manager wanted him to lead a design review for a new service. He did it, and got promoted the next cycle. Luna: So it's a negotiation, but a collaborative one. Lucas: It should be. But not all managers are great. Some will string you along. In that case, you need to build your packet yourself and get feedback from mentors or skip-level managers. The promotion process at FAANG is supposed to be objective, but it's still human. Luna: Let's talk about the calibration meeting itself. I've heard those can be brutal. Lucas: They are. Managers sit in a room and argue about who gets promoted. Your manager has to advocate for you against other managers who want their own people promoted. So your manager needs ammunition. That's your packet. If your packet is weak, your manager can't fight for you. Luna: And the current environment — mid-2026 — how does that affect things? Lucas: Headcount growth has slowed across FAANG. That means fewer slots for promotion, especially at higher levels. At Google, L5 to L6 promotion rates have dropped from about 20 percent to maybe 12 percent annually. So the bar is higher. You really need to show impact that's beyond your immediate team. Luna: That makes the packet even more important. But let's be real — some people get promoted anyway. What's the secret? Lucas: The secret is visibility. Not in a political way — but by working on projects that are high-priority for the company. If you're working on a project that's critical to a VP's quarterly goals, your work gets noticed. Your manager can say, 'This person saved the launch of Project X.' That's gold. Luna: So choose your projects wisely. Lucas: Yes. And if you're stuck on a low-visibility project, you need to either reframe it or find a way to add visibility. Write a design doc that gets shared widely. Give a tech talk. Volunteer for a cross-team initiative. Anything that puts your name in front of decision-makers. Luna: Let's give listeners a concrete checklist. If someone is listening and wants to start preparing today, what's the first step? Lucas: Step one: schedule a meeting with your manager this week. Ask point blank: 'What does success look like for the next level?' Write down exactly what they say. Then, step two: audit your last six months of work. For each project, write the impact in numbers. If you can't find a number, that's a red flag. Luna: And step three? Lucas: Step three: identify one gap — something your manager mentioned that you haven't done — and start a project to fill it. That could be mentoring a new hire, or leading a design review, or improving a process. Then you have three months to execute before you need to submit your packet. Luna: That's a solid plan. One thing I've noticed in successful promotion stories is that the engineer often has a champion — someone who isn't their direct manager but who can vouch for them. Lucas: Yes, that's called a 'promotion buddy' or a 'sponsor'. It's not required, but it helps. If you can get a senior engineer or a principal engineer to read your packet and say, 'I've worked with this person, they're performing at the next level,' that carries weight in calibration. Luna: So don't go it alone. Lucas: Exactly. And one more thing: don't be discouraged by a no. Ravi, the engineer I mentioned earlier, actually got rejected on his first attempt. He used the feedback to strengthen his packet, and six months later he got it. Persistence matters. Luna: And if you get the promotion, then what? Do you immediately start preparing for the next one? Lucas: You take a breath first. But yes, the same cycle repeats. The higher you go, the more the criteria shift from individual contribution to organizational impact. But the fundamentals — documenting impact, getting visibility, building relationships — those never change. Luna: Alright, let's wrap with a quick recap. For anyone who wants a promotion at FAANG: start the conversation early, build a metrics-driven packet, find a sponsor, and be persistent. Lucas: And if you want more detailed examples, check out the show notes — we'll link to a sample promotion packet that one engineer shared. Thanks for listening, and we'll be back next week with another deep dive.