# Microsoft's Buyout Pays Like a Layoff. A December Offer Breaks the Tie

_Microsoft's Voluntary Exit Offer pays the same as severance. Here's who's eligible, which orgs opted in, and how to time an offer before early December._

- Canonical URL: https://www.refolk.ai/blog/microsoft-voluntary-exit-offer-recruiting-before-december
- Published: 2026-11-06
- Reading time: 9 min
- Keywords: Microsoft voluntary exit offer, Microsoft buyout 60,000 employees, hire Microsoft engineers, recruiting laid off Microsoft employees

If you want to hire Microsoft engineers, about 60,000 of them have just been offered a buyout, and Microsoft expects very few to take it. That gap is your opening. The package pays the same as a layoff would, so for most people it doesn't decide anything. A signed job offer that arrives before the early-December decision date can.

## What is Microsoft's Voluntary Exit Offer, and who got it?

The Microsoft Voluntary Exit Offer (VEO) is a buyout offered to about 60,000 employees at level 70 and below, in participating teams, in the US, Canada, the UK and India. That's about 27% of a 223,000-person workforce. Decisions are due in early December, and anyone who accepts leaves on Dec 31.

Todd Bishop at GeekWire confirmed the 60,000 figure with Microsoft. Amy Coleman, Microsoft's EVP and Chief People Officer, wrote the memo announcing it.

> **60,000** Microsoft employees offered the Voluntary Exit Offer
>
> About 27% of the company's 223,000 staff, across the US, Canada, the UK and India.

The level cutoff is higher than it sounds. According to TechPowerUp, level 70 reaches general managers and some vice presidents. Corporate vice presidents are excluded. Age, tenure and performance play no part in eligibility.

The package includes:

- Base pay scaled to tenure and level
- Continued stock vesting
- Healthcare for a fixed period
- Career transition support

Microsoft describes all of this as equivalent to its standard severance. That one word, "equivalent," is the reason a recruiter can make a difference here.

## Why doesn't the package alone move anyone?

It pays the same as being laid off. An eligible employee who turns it down and gets cut later probably walks away with about the same money, so there's no financial reason to leave early.

Microsoft has also said the VEO doesn't replace layoffs. It cut 4,800 jobs in July, 3,200 of them at Xbox, and another 268 Xbox jobs in September. Put yourself in the shoes of an Xbox engineer below level 70. You can take severance now, or you can stay, keep vesting, and take the same severance if another round reaches you. Waiting is the rational choice, because waiting costs nothing.

CFO Amy Hood said it directly in her note to staff: "We expect very few people to select this offer because of the growth opportunities here at Microsoft." Read that as a forecast, not a boast. Nothing in the package pushes people toward the exit.

> The VEO doesn't pay people to leave early. A start date on top of it does.

A written offer changes the math. Severance plus a new salary starting in January is clearly more money than staying and hoping. A recruiter who shows up with that before the decision date is offering the one thing the package can't: a good reason to choose now.

> **Senior engineering roles open right now** - [see the open roles](https://www.refolk.ai/jobs/search?family=engineering&seniority=senior)
>
> Live senior engineering postings, a view of the demand a Microsoft engineer will weigh against staying.

## How many Microsoft employees will actually take the buyout?

Probably about 1,800 to 3,600, depending on which reported rate you trust, and Microsoft's own guidance points to the lower end. Outlets quote different figures, so here is each one next to the number of leavers it implies on 60,000 eligible people.

| Source | Reported expectation | Implied leavers |
|---|---|---|
| Fortune (spokesperson) | "Around 3% to 5%" at similar programs; Microsoft expects "under 5%" | 1,800 to under 3,000 |
| Business Insider, via People Matters | "3,000 or fewer" | up to 3,000 |
| Other reports (spokesperson, citing peers) | 5% to 6% | 3,000 to 3,600 |
| Spring Voluntary Retirement Program | 30% of about 8,750 | about 2,600 |

The last row is the useful comparison. The spring Voluntary Retirement Program (VRP) went to about 8,750 US employees whose age plus tenure was already at least 70, and about 30% accepted. The VEO goes to roughly seven times as many people, and Microsoft still expects about the same number of departures.

The difference is who's being asked. VRP recipients were close to retirement and many already planned to go. VEO recipients are mid-career, still vesting, and have reasons to stay. The 3,000 or so who accept on their own aren't really your audience, because they've already decided. Your audience is the undecided group in the remaining 57,000: people who would leave if leaving came with a plan.

## Which Microsoft orgs opted into the VEO?

Per The Verge, the participating orgs are AI experiences, Copilot, CoreAI, Windows + Devices, Xbox, finance and HR, while security, marketing, commercial business, discovery and quantum, and data centers are reported as out. Each org leader decided whether their team takes part, so eligibility follows the org, not the individual.

Coleman's memo says only that some organizations are offering the VEO and some aren't. Press reports fill in the rest, and the outlets' exclusion lists differ slightly.

**Reported as participating (per The Verge):**

- AI experiences
- Copilot
- CoreAI
- Windows + Devices
- Xbox
- Finance and HR

**Reported as partially participating:**

- Cloud + AI
- Microsoft AI
- Corporate, external and legal affairs

**Reported as not participating:**

- Marketing
- Commercial business
- Discovery and quantum
- Security
- Data centers

Because performance wasn't a factor and leaders made the call org by org, a person's team tells you more than their title does. A principal engineer in Windows + Devices is probably eligible. A senior engineer in security probably isn't, whatever their level. Start your list with Windows + Devices, Xbox and CoreAI. In the partial orgs, ask before you assume. Leave security and commercial staff for later.

The Microsoft community on Blind has active threads mapping levels and evaluating offers. Read them before you write a single message, so your outreach uses the levels and team names candidates actually use.

## Why is this a rare chance to hire Microsoft's AI engineers?

Microsoft offered buyouts to the AI teams Google protected. Google's buyouts have run since June in Canada, France, Germany, Japan and Switzerland, with Cloud and DeepMind excluded.

Microsoft's participating list includes CoreAI, Copilot and AI experiences. Applied-AI product engineers at a company like this are normally off-limits. Right now, some of them have a formal, company-approved reason to think about leaving.

The Google comparison is useful on terms too. Google Zurich, with about 5,000 staff, has the most detailed published buyout terms: one month's pay per year of service, capped at 12 months. Reuters also reports that Google followed its buyouts with layoffs in at least one division. That's worth mentioning to a candidate who thinks declining the buyout is the safe option.

## Where are the Microsoft engineers in the four VEO countries?

Mostly in the US and India. In Refolk's index of professional profiles, 34,577 people across the four VEO countries have "Microsoft" in their headline and a Software, Senior Software or Principal Software Engineer title. The US and India together account for about 95% of them.

| Market | Profiles in Refolk's index | Share of 4-country total | Still at Microsoft (25-profile sample) |
|---|---|---|---|
| United States | 18,976 | 54.9% | 17/25 (68%) |
| India | 13,887 | 40.2% | 15/25 (60%) |
| UK + Canada | 1,714 | 5.0% | 9/25 (36%) |
| Total | 34,577 | 100% | n/a |

One caveat: "Microsoft" is matched against the headline, so the counts include people who have already left. The sample column gives a rough idea of how many are current employees. In the UK and Canada, only about a third of the sample still worked there. In the US and India, most did.

The samples also show where people are. In the US sample, 9 of 25 were in the Seattle/Bellevue area, and Meta was the second most common current employer. That tells you where ex-Microsoft engineers tend to land, and who you're competing with for them. In the UK and Canada, London and Vancouver were the top cities.

To build the list, start with the participating org names and work down to individuals. A title search for "software engineer Microsoft" brings up security and data-center people you can't move. [Refolk](/) lets you describe the person you want in plain English, including their org, and returns a ranked shortlist:

> **Example search:** "Senior or principal software engineers currently at Microsoft working on Windows, Xbox, Copilot or CoreAI, based in Seattle, Bellevue or Hyderabad" - [run it on Refolk](https://www.refolk.ai/s/9ngef9899b)
>
> You get a ranked list of current Microsoft engineers in the participating orgs, with profile links and signals for team and location.

## Why is India the overlooked pool?

India accounts for 40% of the Microsoft engineer profiles in Refolk's index, and most of them are in one city. India is in Microsoft's VEO. Google's latest buyout round doesn't include it.

> **13,887** Microsoft-headline software engineers in India in Refolk's index
>
> In a 25-profile sample, 14 were in Hyderabad, where Microsoft's India Development Center is.

That concentration works in your favour: one city, one campus (the Microsoft India Development Center in Hyderabad), and a pool about 0.73 times the size of the US one. Recruiters hiring in India also aren't competing with a parallel Google buyout wave for attention. If your team can hire in Hyderabad, this is the least crowded part of the VEO market.

## When should you send the offer?

Before the early-December decision date, with a written offer in hand and a January start date. Leavers exit Dec 31, so an offer that arrives after someone has already declined the VEO can't change their decision. At that point it's just a regular poach of a regular employee.

Work backward from the deadline:

1. **Now through mid-November:** build the list from participating orgs and make first contact. Ask about the person's team, not their VEO plans.
2. **Late November:** run a compressed loop. Two or three interviews, not six.
3. **Before the decision date:** put a signed written offer in their hands with a firm January start.
4. **Dec 31:** they exit Microsoft with severance.
5. **January:** they start with you, with no gap and no lost income.

The hard part is the calendar. A normal sourcing cycle for a senior engineer (find, reach out, follow up twice, schedule, interview, approve) can easily run past the time left. If your req is still waiting on headcount approval, or your pipeline depends on cold messages that take two weeks to get replies, you'll lose this window to a company that already has candidates ready to interview.

Speed matters more than salary here. An undecided engineer doesn't need the best offer on the market. They need one that is concrete and arrives before the decision date.

## How should you frame the outreach?

Pitch "severance plus a job," not "a better job." The candidate isn't comparing you to Microsoft. They're comparing a known Dec 31 exit with income lined up against staying and possibly getting laid off later.

What works:

- **Lead with the timeline.** "A written offer before early December, with a January start" does more than any line about your mission.
- **Name the stacking explicitly.** Your salary comes on top of their severance. Spell out the math.
- **Ask about the team, not the decision.** "Is Windows + Devices part of the VEO?" is a safe question. "Are you taking the buyout?" isn't.
- **Respect the vesting.** VEO leavers keep vesting under the package terms, so don't build a sign-on bonus around "replacing" equity they aren't actually losing.
- **Make it checkable.** A real company domain, a named hiring manager, and a clear process. Someone weighing a Dec 31 exit will check before they reply.

What fails:

- Treating them the way you would when recruiting laid off Microsoft employees. They haven't been laid off. They still have a job, leverage, and the option to say no.
- Vague "let's chat" messages in late November. There's no time left for a chat that doesn't lead to an offer.

## FAQ

### Is every Microsoft employee at level 70 and below eligible for the VEO?

No. Eligibility requires level 70 or below, a participating team, and a location in the US, Canada, the UK or India. Org leaders decided whether their teams take part. Marketing, commercial business, discovery and quantum, security and data centers were reported as not participating, and Cloud + AI and Microsoft AI only partially. Age, tenure and performance weren't factors.

### What happens if my offer arrives after the December deadline?

It won't affect the VEO decision. Anyone who declined is still a Microsoft employee with no severance attached, so you're back to a standard poach. That can still work, but you lose the severance-plus-salary math that made the move easy.

### Should I just wait for Microsoft's next layoff instead?

That's a gamble. Microsoft says the VEO doesn't replace layoffs, and it cut 4,800 people in July and 268 in September. But a layoff picks the teams for you, and every competing recruiter hears about it at the same time. The VEO window lets you choose the org and reach people before the decision is made for them.

---

_From the Refolk blog. More posts: https://www.refolk.ai/blog/index.md_