Free Intensive Nov 21–22Free 2-day hands-on Vibecoding Intensive on Nov 21–22 at 16:00 MSK (Sat–Sun) · Live Cohort 3 starts Nov 23Join Free →Cohort 3 (Nov 23)

Nadella Explains Why Microsoft Asked 60,000 Employees to Leave Voluntarily

Microsoft offered about 60,000 employees the chance to leave voluntarily, on generous terms. Satya Nadella insists this is not about replacing people with agents but about restructuring, with each person's work reduced to managing AI agents. Those for whom the new role won't suit can decide now, he says. Developers should prepare to work not on code itself, but on the system that writes it.

AI-processed from TG: @techsparks (TechSparks (Андрей Себрант)); edited by Hamidun News
Nadella Explains Why Microsoft Asked 60,000 Employees to Leave Voluntarily
Source: TG: @techsparks (TechSparks (Андрей Себрант)). Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceTG: @techsparks (TechSparks (Андрей Себрант)) ↗
Editor-in-Chief
Key metric #1The Cowork team has just 11 people, and they are building a "software factory" rather than the product itself
Key metric #2Nadella says the developer role will remain and become more important, but the work will change
Key metric #3The main challenge is turning the 51-year-old Microsoft into a truly AI-first company

When it became known that Microsoft had offered about 60,000 employees the chance to leave voluntarily on very attractive terms, the headlines wrote themselves: "AI is pushing people out." CEO Satya Nadella, in a conversation reported by TechCrunch, disagreed with that interpretation and explained what is actually happening inside the company. For anyone building products on agents or managing development teams, it is a rare chance to hear the logic of a major player without press-release gloss.

Not replacing people, but changing roles

According to Nadella, the goal is not simply to replace employees with agents. Microsoft is restructuring so that everyone's job becomes managing agents rather than personally carrying out tasks. Put simply: previously a specialist wrote code, prepared a report or handled requests themselves; now they assign tasks to AI agents, check the results and take responsibility for the outcome.

He acknowledges that this role won't suit everyone. Some people enjoy hands-on coding, craftsmanship and personal contribution; others prefer organization and oversight. So, in Nadella's logic, it is more honest to give people the chance to decide their own future now, rather than postpone the choice and end up a victim of circumstances. He framed the aim this way: each person should keep the sense that they made the choice themselves. In English this touches on "agency", and the wordplay is hard to miss: the company is shifting toward agent-driven work while wanting to preserve people's own agency.

Cowork: 11 people and a "software factory"

Nadella's main example is the team behind the Cowork product. It has just 11 people. He describes their work as building a software factory that creates the product, rather than building the product itself.

This is a useful picture for practitioners. Imagine not a developer writing function after function, but an engineer configuring a pipeline: a set of agents, checks, tests and acceptance rules. The product comes out of that pipeline, and the person is responsible for making sure the pipeline works correctly. A team of 11 shows, in Nadella's view, where the industry is heading: small groups overseeing large volumes of automated work.

He is convinced this trajectory is universal. Every employee will eventually become a manager of agents rather than a hands-on executor. At the same time, he believes the developer role will not disappear and will even grow in importance, but the substance of the work will be different. And, as he himself notes, this change will not appeal to everyone, though he sees no other path.

What remains out of view

It is important to keep the limits in mind. These are the words of the executive himself about his own decision, and we have no independent verification of how the transition will actually go. The terms of departure, the exact number of people who accepted, and how many people the company will hire for new roles are not disclosed in this account. The Cowork example is a single team, and it does not follow that sales, support or infrastructure departments will restructure just as easily.

Nadella himself calls the main problem for Microsoft its ability to reorganize, at the age of 51, into a truly AI-first company. By his account, this will take somewhat longer than anyone expects, and some employees will say, "I have other plans." That reads as an admission that even a company with enormous resources will not have a quick and painless transformation.

What this means for developers and product managers

First: managing agents is becoming a working specialty. It means the skill of breaking down a task, writing clear instructions, checking results and catching errors that an agent confidently presents as success. Second: for smaller teams, the 11-person example is a benchmark for what to try now: investing in tests, automated verification and the infrastructure around agents, not just in the code itself. Third: if you manage people, it is better to start the conversation about changing roles early and honestly, as Microsoft is trying to do; otherwise, circumstances will make the choice for your employees.

Story

Key Questions Answered

What are the key details on Not replacing people, but changing roles?

According to Nadella, the goal is not simply to replace employees with agents. Microsoft is restructuring so that everyone's job becomes managing agents rather than personally carrying out tasks. Put simply: previously a specialist wrote code, prepared a report or handled requests themselves; now they assign tasks to AI agents, check the results and take responsibility for the outcome. He acknowledges that this role won't suit everyone.

What are the key details on Cowork: 11 people and a "software factory"?

Nadella's main example is the team behind the Cowork product. It has just 11 people. He describes their work as building a software factory that creates the product, rather than building the product itself. This is a useful picture for practitioners. Imagine not a developer writing function after function, but an engineer configuring a pipeline: a set of agents, checks, tests and acceptance rules. The product comes out of that pipeline, and the person is responsible for making sure the pipeline works correctly.

What remains out of view?

It is important to keep the limits in mind. These are the words of the executive himself about his own decision, and we have no independent verification of how the transition will actually go. The terms of departure, the exact number of people who accepted, and how many people the company will hire for new roles are not disclosed in this account. The Cowork example is a single team, and it does not follow that sales, support or infrastructure departments will restructure just as easily.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Private AI Builders Community · Vibe Club

Ship AI Faster with Founders, Engineers & Weekly Architecture Reviews

Inside Vibe Club (hamidun.com/club) — weekly live masterminds with Zhemal Khamidun, Tech Radar, full LMS access, and 370+ production Claude Code skills.

Join Vibe Club →Explore Hamidun Academy
What do you think?
Loading comments…