The Internal Transfer Market

Inside every big company there is a labor market; mobility is leverage, and staying put earns you a loyalty discount.

Big tech companies are not monoliths. They are collections of hundreds of teams competing for a scarce resource: proven engineers who already have badge access, security training, and context on internal tooling. That competition is a market, with prices (level, comp, scope), buyers (hiring managers), and sellers (you). Most engineers never notice it exists. They treat their current team as the whole economy, and they get priced accordingly.

The loyalty discount

Compensation, level, and scope do not adjust smoothly over time. They adjust in jumps, and the jumps cluster around moments of movement: an external offer, an internal transfer, a competing team expressing interest. Between those moments, the system defaults to the cheapest thing that keeps you from leaving — which, if you show no signs of leaving, is approximately nothing beyond the standard refresh.

This is not malice. It is budget mechanics. Retention money is a reactive instrument: it exists to counter flight risk, and it is released when flight risk becomes legible — an offer letter, a transfer conversation, a skip-level hearing that another org wants you. Gratitude does not trigger it. Tenure does not trigger it. A manager can genuinely value you and still be unable to unlock the budget, because the budget answers to risk, not appreciation.

The result is measurable in any long-tenured org: the engineer who spent six years on one team, doing solid work the whole time, typically trails peers who moved two or three times in the same window — in level, in comp, and in scope. Each of those moves was a repricing event. The stayer never had one.

Mechanics

Why does movement reprice you? Two mechanisms.

First, your current chain prices you by your history. The people who decide your level and scope remember the junior engineer you were three years ago, and reputations update slowly (see Reputation Forms Early and Updates Slowly). Every promo conversation about you starts from that old anchor and argues incrementally upward. A new team has no anchor. They evaluate the engineer who shows up today — your current market value, with a fresh label. This is why the same person can struggle to make senior on their home team and get hired at senior by the team next door.

Second, transfers compound assets that staying cannot. Each team you pass through adds a layer to your shadow org chart: people who know your work firsthand, who will vouch for you, loop you into opportunities, and warn you about bad teams. A one-team engineer's network is one manager deep. A three-team engineer has references and allies across the org, which also de-risks the single biggest hazard in a corporate career: a manager who leaves, gets reorged, or turns against you. If your entire reputation lives in one person's head, you are one bad quarter of theirs away from starting over.

When to move, when to stay

Move when:

You've outgrown your label. The team still treats you as the person you were at arrival, and the promo case keeps stalling on old impressions.
Your manager is weak or blocked. A manager without political capital cannot spend any on you, no matter how much they like you.
Your project is dead or peripheral. If the work is off the critical path or politically dead, no quality of execution will make it matter (see Be on the Critical Path and Politically Dead Projects).
The promo queue is congested. Three people ahead of you at the same level on the same team is arithmetic, not a judgment of your work. A team with a vacuum at your target level is a faster path.

Stay when:

A sponsor is actively spending capital on you. Sponsorship is rare and non-portable. If someone senior is putting your name in rooms, that is worth more than a repricing.
Your scope is still growing. Movement is a tool for breaking plateaus. If you're not on one, the tool costs more than it returns.
A promo is genuinely close. Transfers reset narratives — that is their power and their cost. A promo case that is two quarters from landing does not survive a move; you'd restart the evidence-gathering on a new team with people who haven't seen your work.

Working the market

You can engage the market without ever transferring. Most of its value is informational.

Browse internal listings periodically, even when happy. It costs nothing and calibrates you: what's being built, what levels are open, what your skills fetch. You cannot know you're underpriced if you never look at prices.
Take the coffee chat. When another team asks about you, that is data about your market value delivered for free, and flattery costs nothing to receive. Declining tells you nothing; listening tells you what you're worth.
Never bluff a departure. A threatened exit you don't execute is spent capital that never returns — you will be remembered as a flight risk and a bluffer simultaneously, the worst of both. Only surface competing interest that is real.
Time moves after landings, not mid-project. The last ten percent of a project is where reputations are made, and abandoning it is the story that travels with you. Leave on a shipped thing.
Leave every team clean. Document, hand off, finish the review cycle, say thank you. The internal market is small, references are checked informally and forever, and the manager you leave gracefully today is the director deciding your fate in four years.

Diagnostic test

If you cannot name your current market price — what level and scope another team would hire you at today — you are almost certainly being paid the loyalty discount.