Writing

I changed employers four times without changing jobs

Jun 25, 2026

I spent years on a single platform, and over that stretch I worked for several different companies without ever changing what I actually did. The platform got acquired, rebranded, folded into a larger org, and acquired again. Same codebase, same systems, the same desk. Different email signature, different name on the paycheck, different leadership chain to learn.

If you’ve only ever experienced “changing companies” as a thing you choose, this is a different animal. The company changes around you. And it comes with a whole genre of noise most career advice never mentions.

The noise is real, and it’s a tax

Every ownership change drags in its own overhead. Retention bonuses to keep people from bolting during the uncertainty, or in a lot of cases just the promise of one. Equity that gets converted, replaced, or re-vested under new terms. Transition-service exits where you have to disentangle your stack from the former parent on a deadline. Reorgs that reshuffle who you report to and who owns what. New tools, new processes, new acronyms for the same old things.

None of that ships product. All of it competes for your attention with the work that does. And the people around you are doing the same nervous math you are: is my role safe, is my team intact, is this a good time to leave. The churn is a drag coefficient on the whole org, and pretending it isn’t just means you handle it badly.

What actually carries you through

The skill, it turns out, is treating the org-chart churn as weather rather than identity. The logos change; the platform still has to stay up, the customers still expect their service, the team still needs someone keeping them pointed at real work instead of spiraling on rumors. So you protect the platform, you protect the team, and you let the reorg happen around a stable core.

Practically that means being the calm in the middle: keeping the systems running through the transition, shielding your people from as much of the chaos as you can, and staying focused on the work that’s the same regardless of who owns the company. Your loyalty ends up being to the platform and the team, not to whichever entity currently holds them, and that’s what lets you stay effective while everything around you is in flux.

The takeaway

A lot of careers include changes you didn’t choose: acquisitions, reorgs, rebrands. The engineers who come through those well aren’t the ones who ignore the churn or the ones who get swept up in it. They’re the ones who treat it as weather, keep the platform and the team stable through it, and stay anchored to the work that doesn’t change no matter whose name is on the building.