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: You've been at a FAANG for eighteen months. You're solid, your reviews are good, but the work has gotten predictable. You don't want to quit — you like the compensation and the brand — but you're bored. What do you do? Luna: You start looking at internal transfer postings, right? That's the obvious answer, but I think a lot of engineers don't actually know how that pipeline works. They treat it like applying to a new company — same anxiety, same prep. Lucas: Exactly. And that's the wrong mental model. Internal mobility at a place like Meta or Google is structurally different from an external hire. For one, the interview process is usually lighter — you might skip the full loop of system design and just do a one-hour chat with the new team lead. But the real difference is cultural. Lucas: When you transfer internally, you bring institutional knowledge: how the codebase works, who the stakeholders are, how to navigate performance review season. That's hugely valuable to the receiving team. They're getting a known quantity, not a resume. Luna: And you retain your vesting schedule, your level, your tenure. That's a big deal. I've talked to engineers who took a pay cut to switch companies because they undervalued their unvested equity. Internal move? You keep the clock running. Lucas: Right. So let's talk about how the mechanics actually work. At Amazon, the internal transfer process is called 'Internal Mobility' — it's literally a section on the jobs portal. You apply, your current manager gets notified, and then there's a negotiation window where the new team and your current manager figure out a start date. Lucas: At Google, it's more structured. You have to be in your current role for at least eighteen months — that's the hard gate. Then you enter something called a 'transfer conversation' where both managers discuss your move. Google actually tracks transfer success rates by team. Luna: Meta is the most flexible of the bunch. I read a case study — I think it was in a leaked internal document — where an engineer who had been on the ads team for two years decided she wanted to work on VR hardware. She reached out to a manager in Reality Labs, had a thirty-minute call, and within six weeks she was on a new team. No formal interview. Lucas: Six weeks is fast. But that's the exception, not the rule. Most internal transfers take three to six months, depending on how critical you are to your current team. If you're the only person who knows how a legacy service works, your manager has leverage to delay. Luna: That's actually the biggest friction point — the manager. Some managers are supportive because they see it as a positive career move. Others get defensive because they don't want to lose a high performer. I've heard of managers giving bad recommendations or creating busywork to stall. Lucas: So you need a strategy. The first step is to have an honest conversation with your manager early — say, at the one-year mark — about your growth goals. 'I'm excited about what we're building, but I also want to explore X area in the next six to twelve months.' That way, when you eventually apply, it's not a surprise. Lucas: Second, you need to network inside the company before you apply. Go to tech talks in other orgs. Join internal Slack channels for the domain you're interested in. Volunteer for cross-team projects. You want the new manager to know your name before they see your application. Luna: Let me add a data point here. Google did an internal study a few years ago — and I think it's still relevant in 2026 — that found engineers who transfer internally once are 40 percent less likely to leave the company within two years compared to engineers who never transfer. Luna: Forty percent. That's huge. It suggests that internal mobility isn't just a nice perk — it's a retention tool. Companies that make it easy to move around actually keep their talent longer. And the inverse is also true: if you feel stuck, you're more likely to start interviewing elsewhere. Lucas: That lines up with something I heard from a recruiter at Apple. She said that the 'boomerang hire' — someone who left Apple and later returned — used to be rare, but now it's almost common. Apple relaxed its rehire policy in 2024: you can come back within two years without re-interviewing for the full loop. Luna: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Lucas: Yeah, it's a small way to keep the conversation going without ads. Because we want to keep digging into these mechanics. Luna: So back to the boomerang — Apple's policy change is interesting because it signals that the company recognizes the cost of losing institutional knowledge. Even if you leave, they'd rather have you back than train someone from scratch. Lucas: But let's talk about the downside. Internal transfers aren't always a panacea. You might move to a team that has a toxic culture, or a manager who doesn't support your growth, or a project that's even more boring than the one you left. You need to do due diligence. Luna: So what's the due diligence process? How do you evaluate a team internally when you can't exactly ask for external references? Lucas: You talk to people who used to be on that team. You attend their stand-ups or sprint reviews as a guest. You ask the new manager specific questions: 'What does success look like in the first quarter? What's the on-call rotation like? How often do you do one-on-ones?' Treat it like you're interviewing them. Luna: And check the team's churn rate. If a team has had three different managers in two years, that's a red flag. You can usually find that info through the internal org chart or by asking around. Lucas: Another thing: understand how your move will affect your promotion timeline. Some FAANGs require you to be in a role for at least a year before you're eligible for promo. If you transfer every twelve months, you might stall your level growth. Luna: Right. So internal mobility is a tool, not a strategy in itself. You want to use it to get exposure to different domains — maybe start in infrastructure, move to machine learning, then to product — so that you build a broader skill set. Lucas: And that breadth can make you more valuable when you eventually do go for a senior staff role. At that level, you're expected to influence across teams. Having worked in three different orgs gives you credibility. Luna: I want to zoom out for a second. There's a broader trend here: FAANG companies are investing in internal mobility as a retention lever because the external hiring market is still competitive in 2026. It's cheaper to retain than to recruit. Lucas: Yeah, the cost of replacing a senior engineer is easily six to nine months of their salary when you factor in recruiting fees, onboarding time, and lost productivity. So companies are building better internal tools. Meta has an internal platform called 'Workplace' where teams post open roles. Google has 'gCareer'. Luna: And some companies are gamifying it. I saw that Amazon now gives badges to managers who have the highest internal transfer 'send rates' — meaning they're good at developing talent that then moves elsewhere. It's supposed to encourage managers to be supportive. Lucas: That's smart. Because the biggest blocker is almost always the manager. So if you're an engineer listening, and you're nervous about having that conversation, here's a script: 'I want to develop in X area, and I think that team would give me exposure. I'd love your advice on how to make this move successful for both me and the team.' That frames it as a collaborative decision. Luna: And if your manager is still resistant? Then you have a signal about the broader culture. Maybe it's time to consider an external move after all. Lucas: But before you jump ship, try the internal route first. Even if it doesn't work out, you've made connections and learned about other parts of the company. Worst case, you have a better sense of what you want elsewhere. Luna: One last thing: if you do transfer, document everything. Your old manager might be a reference for future moves. Send a thank-you note. Help with the transition. Don't burn that bridge. Lucas: And that's the thing about internal mobility — it's not just about moving laterally. It's about building a career lattice, not a ladder. You might go sideways twice before you go up. But the data says it pays off. Luna: Yeah. So if you're feeling stuck, the answer isn't always to leave. Sometimes it's to look across the hall. Lucas: Exactly. Thanks for listening, and we'll be back next episode with another angle on navigating FAANG careers.