Latest / The Tech Career Podcast with Fexingo: Engineering Jobs, Interviews, and FAANG Career Strategy / How FAANG Engineers Leverage Internal Mobility for Career Growth
Transcript
- Lucas: So there's this assumption in tech that if you want to grow fast, you have to leave. Change companies every two years, get the big comp bump, reset your equity. That path works — but it's not the only fast track. Luna: And it carries risk. You lose context, you have to prove yourself from scratch, and your first six months are basically zero productivity. Lucas: Exactly. That's why I want to talk about internal mobility today — specifically the mechanics of moving teams inside a FAANG company without quitting. There's a version of this that most engineers leave on the table because they don't know how to navigate the politics. Luna: Can we anchor with a real example? I find it hard to visualize otherwise. Lucas: Yeah, let's use someone I'll call Priya. She was an SDE 2 at Amazon working on AWS billing infrastructure — think high-traffic, high-observability, but frankly kind of boring backend work. She wanted to move into Alexa AI, which is much more product-facing and ml heavy. Luna: That's a big jump. Different org, different tech stack, different manager power structure. Lucas: Right. And the standard approach — applying through the internal jobs portal — would have triggered a formal transfer process. Her current manager would get a notification, and if he didn't want to lose her, he could block the move for up to 90 days under Amazon's policy. Luna: So she needed a stealthier path. Lucas: Exactly. What she did instead was build what I call a 'brag doc' — a living document listing her biggest contributions, with metrics and links to code reviews. She didn't send it to anyone. She used it to prep for informational interviews with engineers on the Alexa team. Luna: Informational interviews inside the same company? That's smart. It's not applying — it's just asking questions. Lucas: Right. She reached out to five people on the Alexa AI team, said she was exploring the space, and asked about their day-to-day. During those calls, she mentioned her own work when it was relevant — not pitching herself, just building rapport. Two of those engineers later told their manager about her. Luna: So the manager reached out to her? Lucas: He did. He invited her for a casual chat, then a proper interview loop — but it was framed as a 'team fit' session rather than a formal interview. That's the key: when the hiring manager comes to you, the power dynamic shifts. You're not a supplicant. You're someone they already want. Luna: And her current manager? He found out eventually, I assume. Lucas: He did, but by the time he did, Priya had already had the informal conversation with the new manager. The new manager reached out to the old manager and said, 'Hey, we'd love to have Priya, can we work out a transition?' The old manager could have said no, but because the new manager was initiating, it felt like a done deal — and blocking it would have looked bad. Luna: So she essentially built her own internal network before triggering any formal process. I love that. Lucas: And it paid off. She moved within six weeks, and within 18 months she got promoted to SDE 3 — which is faster than the average on the billing side. There's actually data on this: a 2024 internal analysis at Google showed that engineers who made one internal move within their first three years got promoted 1.8 times faster than those who stayed put. Luna: That's a huge difference. But is that because moving itself makes you better, or because the people who move are already more ambitious? Lucas: Both, probably. But there's a structural advantage too: when you move, you get a fresh performance review cycle. Your new manager has no preconceptions, so you can make a strong first impression. And you're exposed to new problems, which forces you to grow faster. Luna: Still, in this market — we're recording at the end of June 2026 — a lot of FAANG companies have tightened their internal transfer policies. I've heard that Meta requires you to stay in your role for at least 18 months now, and hiring freezes mean there are fewer open seats. Lucas: That's true. The 18-month rule is standard at Meta and Apple now. But even with those constraints, the stealth approach works because it's about building relationships before the role opens. Priya started building her network nine months after she joined Amazon — way before the 18-month mark. When she eventually hit 18 months, she already had an offer in hand. Luna: So the timeline is: start early, plant seeds, and wait for the right moment. That requires patience. Lucas: It does. But the alternative — quitting, interviewing externally, losing equity — is also a long process. Internal moves are often faster if you do them right. One thing I'd add: the brag doc is critical because it forces you to articulate your value in terms that another team cares about. AWS billing infrastructure might sound boring, but if you frame it as 'I optimized a high-throughput pipeline that handles 50,000 transactions per second with 99.99 percent uptime', suddenly that sounds relevant to an Alexa team working on latency-sensitive speech recognition. Luna: Right — you're reframing your experience, not just listing your duties. That's a skill in itself. Lucas: And it's a skill that pays off in performance reviews too. Actually, that's a connection I want to make: the same brag doc you use for internal mobility is exactly what you need for promotion packets. So you're essentially doing prep work for two goals at once. Luna: That's efficient. I've seen engineers keep a 'career journal' where they write down one win each week — it becomes this repository of evidence. If you do that consistently, you're never scrambling at review time. Lucas: Exactly. And that journal — or brag doc — also makes you visible to internal recruiters. At most FAANG companies, there's an internal talent marketplace where recruiters can search for skills. If your profile is up-to-date with concrete metrics, you might get approached without doing any outreach at all. Luna: So there's a passive version of internal mobility too. Update your internal profile, wait for the right ping. Lucas: Yeah, but the active version is more reliable. I'd say the biggest mistake engineers make is assuming that because they're at the same company, they don't need to 'apply' internally. They just wait for their manager to create opportunities. That's a losing bet — your manager's incentives are about team stability, not your personal growth. Luna: Right — your manager wants you to stay on their project. They might even give you a good rating to keep you happy, but they won't proactively find you a new role. Lucas: Exactly. So you have to own your career. And internal mobility is one of the best ways to do that because it lets you change your trajectory without the transaction costs of leaving — no lost tenure, no stock vesting cliffs, no new probation periods. Luna: You mentioned stock vesting — that's a huge deal. If you leave, you typically forfeit unvested shares. An internal move keeps everything intact. Lucas: Huge. And at companies like Apple and Amazon, where refresher grants are tied to performance, moving to a high-visibility team can accelerate your grant size. Priya told me her first annual refresher after moving to Alexa was about 40 percent larger than what she'd have gotten on the billing team, just because the new org had more budget for senior talent. Luna: That's a concrete number. Forty percent more equity just by changing teams. That's a strong incentive. Lucas: It is. And I think that's the bottom line: internal mobility isn't just about finding more interesting work — though that's important — it's about optimizing your growth trajectory financially and professionally. If you're a mid-level engineer at a FAANG company right now, and you're feeling stuck, ask yourself: have I actually tried to move, or have I just assumed it's too hard? Luna: That's a good challenge. I think a lot of engineers feel like they're at the mercy of their manager or the org chart. But Priya's story shows there's agency. Lucas: Yeah, and that's the kind of practical takeaway we try to bring on this show. If today's tech conversation gave you something usable — a tactic, a reframe, a concrete example — that's exactly why we do this. We keep the show ad-free because we want it to be a resource, not a revenue stream. A couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo, if you've gotten something out of them. Luna: It really does make a difference. Even small contributions add up and let us keep digging into these stories without interruption. Lucas: Exactly. So back to Priya — after she made the move, she told me the hardest part wasn't the technical ramp-up. It was learning a new set of social norms. The Alexa team had a very different culture from the AWS billing team. Luna: What was different? Lucas: She said the billing team was very process-heavy — every change went through a design review, a security review, a load test requirement. The Alexa team was more experimental: they'd ship a minimum viable feature, measure, and iterate. She had to unlearn the instinct to over-document and instead focus on speed. Luna: That's a real cultural shift. But that's also growth — being forced to adapt to a new environment. Lucas: Absolutely. And she said the first six months were humbling. She was a senior engineer on her old team, but on the new team she was the junior person again. That's a price of internal mobility — you lose some status temporarily. But if you can tolerate that, the long-term payoff is big. Luna: So it's not a free lunch. You have to be willing to start over a bit. Lucas: Right. But starting over inside a company where you already know the benefits system, the performance review process, the internal tools — that's easier than starting over at a new company. You keep your context about how the organization works. That alone saves months. Luna: So the advice would be: if you're thinking about leaving, first exhaust your internal options. Build your brag doc, network inside, and see what's possible before you start sending out external resumes. Lucas: That's exactly it. And if you do decide to leave, that same brag doc and network will help you externally too. So there's no downside. Alright — next episode, I want to talk about something that came up in the comments last week: how to handle a manager who actively blocks your growth. That's a different beast. Luna: That's a hot topic. I've got stories for that one. See you next time.