The people who built your last platform are choosing the exits

Something is moving through the tech org charts right now, and it isn't only layoffs. Longtime builders are taking buyouts. Product chiefs are resigning. New CEOs are gutting their reporting lines. The common thread is AI pressure, but the reactions are all over the map. Let me catch you up on what changed and what to do with it.

When the veterans pick the door themselves

Microsoft opened a first-ever voluntary retirement program to about 7% of its U.S. workforce, an estimated 8,750 employees. The package runs up to nine months of pay, plus a year of full health coverage. For people whose age and years of service add up to 70, it was a clean way to leave on their own terms instead of waiting for a cut with their name on it.

What stands out is who left and why. Shawn Mrzena, after nearly 25 years, is trading "the AI firehose for a welding torch." Denise Hazlick, with almost three decades tied to the company, said the industry is changing and "I just don't have the energy or desire to shift yet again." These are not burnouts. These are people who lived through every prior platform shift and decided this one wasn't theirs to chase.

The knowledge walking out the door

Here is the part that should worry a team leader. The people taking the buyout shipped the products your company runs on. Scott Thurlow was one of the original program managers behind Outlook. Justin Long touched every version of Office since Office 2000. Briand Sanderson shipped Internet Explorer 5 and 6. When they go, the memory of why things were built a certain way goes with them.

Microsofties themselves flagged this: the loss of institutional knowledge as so many long-timers head out at once. Add the reorg churn they described, "the constant churn of managers and reorgs that made it hard to finish anything," and you get a real risk. The AI push is speeding people out faster than the docs can capture what they knew.

Reorgs that reset the whole leadership table

While the veterans leave, the top of the org chart is being redrawn. Microsoft reshuffled Copilot to build a "super app," moving Jacob Andreou to executive vice president of Copilot and bringing in Peter Sellis from Discord to lead design, growth, and engineering. In the same shuffle, Trevor O'Brien, former VP of product for M365 Copilot experiences, resigned.

Lucid went further. Its new CEO cut the number of people reporting to him in half and hired five new chiefs at once: CFO, CTO, chief customer officer, chief digital officer, and chief transformation officer. That came weeks into his tenure and right after hundreds of job cuts. The pattern is the same on both ends: leaders are betting that a leaner, resorted team executes faster under AI pressure. The tradeoff is disruption, and a lot of it.

The skill the new org charts are actually hunting for

Watch what the reshuffled teams say they need. Five9's new CTO framed his job around "one of the most important shifts in customer experience as AI reshapes how companies engage." Synthesia's new Seattle office is recruiting AI video engineers for product, infrastructure, and systems roles. The demand is not for more of the same engineers.

The clearest map of the new role comes from the AI architect path: someone who designs the end-to-end system and owns the tradeoffs, not just the code. The pitch is that companies now sit on piles of AI prototypes and need people who can turn them into governed, cost-aware production systems. That is a different skill than building the prototype, and it is the one the new org charts are wired to reward.

The standards fight nobody is scheduling for

There is a longer game hiding under the reorgs. Vint Cerf, retiring after more than 20 years at Google, made a prediction worth writing down. As AI agents from different vendors start talking to each other, that model "is going to force composability, and a requirement for interoperability and standardization." He doesn't think plain English will do the job between agents. Too much ambiguity, he said, like a game of telephone.

The man who co-built TCP/IP knows a protocol war when he sees one coming. If he's right, the companies that define agent interoperability early get outsized influence, the same way early internet protocols did. That is not a Monday problem, but it should shape what you build to last.

The deep cut

The Microsoft leavers gave you a free warning: reorg churn made it "hard to finish anything." If you are about to redraw your own org chart to chase AI, you are buying that same churn. So do two things before you reshuffle. First, capture what your longest-tenured people know while they are still in the room, in writing, in decision records, not in someone's head. Second, if you are hiring for the AI wave, hire for the architect skill Cerf's protocol point implies: people who can design systems that swap models and stay interoperable, not people who can only ship one clever prototype. The leaders cutting reporting lines in half are betting speed beats memory. Make sure you don't lose the memory you can't rebuild.

Three questions for your team

1. Which of our longest-tenured people hold knowledge that lives only in their heads, and what would it cost us if they took a buyout next quarter?
2. When we hire for AI work, are we hiring architects who own tradeoffs and design for change, or engineers who can only build the demo?
3. If agent-to-agent standards become a real fight, are we building anything now that locks us into one model or vendor we'd struggle to swap?