# Internal Mobility: Switching Teams as an EM Source: https://www.techinterview.org/post/3233475186/em-internal-mobility-switching-teams/ Updated: 2026-06-30 · techinterview.org Internal mobility is one of the most-underused career levers for engineering managers. Switching teams within the same company can give you a fresh challenge, broaden your scope, and avoid the comp/title compression of changing jobs. The interview increasingly probes how you have navigated this — and how you would handle it if asked. ## Why move teams - Career growth in your current team has plateaued - You want to learn a new domain - The new team needs your skills - Your manager / VP changed and the fit is different - The company is reorganizing ## When NOT to move - Less than 18 months in current role — looks like instability - You are running from a hard situation rather than to opportunity - Your team is in a critical moment that needs you - The new team is in trouble and you are being recruited as savior without authority ## The conversation flow - Internal posting or recruiting outreach - Informal conversation with the hiring manager - Get aligned on scope, level, comp before formal application - Inform your current manager (timing matters) - Formal interview process (varies by company) - Transition planning: handoff timeline, knowledge transfer ## Telling your current manager Tricky. Best practices: - Don't apply formally without telling them — they will find out - Have the conversation early, before things are real - Frame as growth ("I want to learn X") not flight ("I want out") - Discuss timing — a quick exit during a crisis is bad form Most reasonable managers support internal moves; some retaliate. Read your manager. ## Handoff The transition out of your current team is a final test: - Identify your replacement (internal candidate or kick off external hiring) - Document key knowledge — strategic context, customer relationships, ongoing risks - Transition each direct report's relationship to the new manager - Be available for questions during the first 30 days post-move Sloppy handoffs damage your reputation across the org. ## The first 90 days in the new team Same playbook as a new external EM: - Listen first; don't prescribe - 1:1 with everyone - Read the team's docs, OKRs, post-mortems - Identify quick wins and longer-term risks Caveat: as an internal mover, you may be tempted to compare to your old team. Resist. Each team has its own context. ## Comp and level Most companies preserve level on internal moves. Comp: - Same base salary - Equity grant typically not refreshed for moves - Some companies offer a small "transition bonus" If the new role is a stretch (more scope), negotiate. "I am taking on X more reports / more strategic scope" can warrant a bump. ## Cross-org politics If you move from one VP's org to another, your old VP loses. Some take this gracefully; some hold a grudge. Smart move: keep the relationship intact. You may need them as a reference; they may need you in the future. Industry is small. ## The "boomerang" within a company Sometimes engineers move out and come back. Internal mobility makes this normal at large companies. ## The "stuck" pattern Some EMs have been at the same company 5+ years on the same team. Common. Usually a sign of: - Comfort over growth - Fear of starting over - Missing the strategic skill of identifying when to move If you have stayed too long, internal mobility is often easier than external job change. ## Frequently Asked Questions ### How do I know if I should move teams or change companies? Move teams if you like the company, comp, and overall culture. Change companies if those are the issue. ### Can I move into a different domain (e.g., backend EM to ML EM)? Yes — internal moves are good for domain shifts. You bring management skill; the team brings domain context. ### What if my company does not support internal mobility? Look for companies that do. Lack of internal mobility is a flag for a mediocre engineering culture.