Microsoft's Buyout: Get January Start Offers Signed Before December
Microsoft's voluntary exit offer reaches 60,000 staff at level 70 and below. Which orgs you can recruit from, and why your offer must land before December.
If you plan to recruit Microsoft's buyout leavers in January, you'll be bidding against every other company for the small number who left. Most of the rest will already have decided to stay. In late October 2026, Microsoft's EVP and Chief People Officer Amy Coleman offered about 60,000 employees a paid way out. They decide in early December and leave on Dec 31.
Who can take the Microsoft voluntary exit offer?
About 60,000 employees at level 70 and below can take it, but only in orgs that chose to participate, and only in the US, Canada, India and the UK. Copilot, CoreAI, Windows + Devices and Xbox are reportedly in. Security, marketing and quantum are reportedly out.
A Voluntary Exit Offer is a buyout. The employee chooses to leave in exchange for a severance package, rather than being picked for a layoff. That difference matters for recruiting. Nobody here is a reluctant job seeker yet. Each of them is weighing a choice, and you can be part of what they weigh.
What's been reported so far:
- Scale: about 60,000 eligible, roughly a quarter of Microsoft's last reported headcount of 223,000.
- Level ceiling: level 70, which covers general managers and some people with vice president titles. Corporate vice presidents are excluded.
- No filters on the person: no age or tenure requirement, and performance plays no part.
- Opt-in by org: each org decided whether its people could take the offer.
- No public list, no target: Microsoft declined to name the teams or roles and says it has set no number of departures.
Since Microsoft hasn't published a team list, the best map available is what sources told Emma Roth and Tom Warren of The Verge:
| Org | Reported status | What it means for you |
|---|---|---|
| Copilot, CoreAI | Participating | AI talent, reachable now |
| Windows + Devices, Xbox | Participating | Xbox lost 3,200 jobs in July, so people there are already unsettled |
| Finance, HR | Participating | Reachable for non-engineering searches |
| Security | Not participating | Treat as a normal poach, no buyout lever |
| Marketing, quantum | Not participating | Same: no package to stack on |
Without an official list, assume the edges are messy. A Windows engineer on a security-adjacent team may not be eligible. Ask about it early in the first conversation.
Why a January start beats a November resignation
A candidate who takes the buyout and starts with you after Dec 31 keeps Microsoft's severance, continued stock vesting and health insurance. A candidate who quits in November to join you gives all of that up. So your offer doesn't need to replace the package. It sits on top of it.
Here's how the package scales by level, alongside reported US total comp from levels.fyi data:
| Microsoft level | Typical engineering title | Reported US total comp | Reported buyout package |
|---|---|---|---|
| 63 to 64 | Senior SDE | ~$233K to $281K | Up to 39 weeks of base |
| 65 to 67 | Principal SDE | ~$339K to $611K | Up to 39 weeks of base |
| 68 | Partner | Not reported | 12 months of salary |
| 69 to 70 | Partner, Distinguished Engineer | Not reported | Not reported |
Work through the math for a Principal SDE. If they resign in November, your offer has to make up for as much as three-quarters of a year's base pay plus unvested stock, which is how bidding wars start. If they take the buyout and start with you in January, Microsoft has already paid for the hard part. You compete on scope, team and comp going forward, and you don't need a huge sign-on bonus.
That changes the pitch from "leave Microsoft for us" to "take the package, then come build this." The second one is easier to say yes to.
One caution. Ask candidates to read their offer paperwork and confirm that signing a future-dated offer doesn't affect their eligibility. I haven't seen any report saying it does. Still, you don't want to be the reason someone loses 39 weeks of pay.
Why your offer has to land before the early-December deadline
The deadline is when people on the fence make up their minds. Microsoft expects only 5 to 6% uptake, so most of the 60,000 are leaning toward staying. A signed offer in hand is what turns a maybe into a yes.
Microsoft's spokesperson pointed to similar programs at comparable companies, where closer to 5 to 6% of employees left. On a pool of 60,000, that's roughly 3,000 to 3,600 people. Compare that with Microsoft's own spring retirement program, where about 30% of the roughly 8,750 eligible US employees accepted.
I read that gap as the opportunity. The retirement group had an obvious next step. Most of the 60,000 don't. My bet is that some of the people on the fence would take the money if they knew where they were going, and a signed offer tells them.
The buyout doesn't create candidates. A signed January offer does.
The window only runs one way:
- Before the deadline, your offer can change the decision.
- Once someone declines, they stay. Microsoft has said it has no plans for another buyout. Keep them warm anyway.
- After Dec 31, the leavers are on the open market, and every other recruiter sees the same "open to work" banners you do.
Reports disagree on the deadline. CNBC says early December. An Indian outlet, the Free Press Journal, reports a Dec 1 deadline for India staff. Ghacks describes Dec 31 as the acceptance deadline. Plan around the earliest date.
That leaves roughly five weeks between late October and a Dec 1 India deadline. In that time you need approval for January start dates, sourcing, a first reply, interview loops and a signed offer. Keep loops to two rounds with a decision inside a week. A search that starts from a blank page will use up most of that window before the first interview.
How many reachable Microsoft engineers are there?
In Refolk's index of professional profiles, 10,258 US profiles have "Microsoft" in the headline and a Senior Software Engineer or Software Engineer II title. In India, 7,060 do. Sampling suggests about 9,400 of the US profiles and 4,800 of the India profiles still work at Microsoft.
| Segment | Profiles | Sample share at Microsoft | Est. current Microsoft |
|---|---|---|---|
| US Sr SWE / SWE II, "Microsoft" headline | 10,258 | 92% (23/25) | ~9,400 |
| India Sr SWE / SWE II, "Microsoft" headline | 7,060 | 68% (17/25) | ~4,800 |
| "Microsoft Copilot" headline, US/CA/UK/IN | 7,719 | 24% (6/25) | ~1,850 |
| Eligible pool (reported) | ~60,000 | n/a | 3,000 to 3,600 leavers at 5 to 6% |
| Spring retirement program (reported) | ~8,750 | ~30% accepted | ~2,600 accepted |
The first three rows come from headline keyword matches checked against 25-profile samples, so read the estimates as directional. The US pool is about 1.45 times the size of India's.
The hard part is that profiles rarely say which org someone sits in, and org decides eligibility. You have to infer it. Look for team terms in titles and summaries ("Windows", "Xbox", "M365 Copilot", "CoreAI"), and leave anyone who mentions security out of the buyout pitch.
Every leaver you don't sign is a senior engineer your competitors can interview in January.
Why a "Copilot" keyword search finds the wrong people
Most people with "Microsoft Copilot" in their headline don't work at Microsoft. In Refolk's index, 7,719 profiles across the four eligible countries match. In a sample of 25, only 6 (24%) were current Microsoft employees.
Copilot is a product people sell, implement and build on, so the keyword picks up the whole ecosystem rather than the org. The other 19 profiles in the sample were:
- Microsoft partners and ISVs, such as Syskit and edison365
- Consultancies, such as SoHo Dragon
- Startups building on Copilot, such as Pretty Good AI
The six Microsoft profiles caused a second problem: they skewed senior. They included an SVP of Copilot Agents Product, a CTO of M365 Copilot and a VP/COO of Copilot Studio. Some of those titles are at or above corporate vice president level, which makes them ineligible. So a keyword search buries the eligible people under partners on one side and executives on the other.
Those partners also compete with you. Firms like Syskit and edison365 are natural landing spots for ex-Copilot engineers.
The fix is to filter on current employer, level and team rather than on the product name. Boolean handles that badly, because "currently at Microsoft, level 70 or below, on a Copilot or CoreAI team, not security" isn't a string you can write. That's the gap Refolk is built for: you describe the person in plain English and get back a ranked shortlist.
India means Hyderabad, and Hyderabad may close first
Most of the India pool is in one city, and India may have the earliest deadline. In Refolk's index, 20 of 25 sampled India engineers were in Hyderabad, home to Microsoft's India Development Center cluster, and India staff reportedly have until Dec 1.
That makes India the part of the pool where timing matters most. Three practical points:
- Start there. If the Dec 1 report is accurate, India closes days or weeks before the rest.
- Filter harder on current employer. Only 68% of sampled India profiles were still at Microsoft, against 92% in the US. More alumni show up in the results.
- One city, one hiring event. With 80% of the sample in Hyderabad, a single local interview day can cover most of the pool.
The US is more spread out. Of 25 sampled US profiles, 11 were in the Seattle/Bellevue/Redmond area and 5 were in the San Francisco Bay Area. The rest were scattered, so remote-friendly roles have an advantage there.
The L68 to L70 partners are the quiet prize
Partners get the richest package and are the hardest people to reach any other way. Reports put the L68 offer at 12 months of salary, against a 39-week cap at level 67 and below. That makes the decision unusually live for general-manager-level people who rarely answer recruiters.
The Microsoft level 70 ceiling reaches general managers and some VP titles. Normal outreach rarely gets to these people. For a few weeks, a year's salary on the table changes that.
Some orgs have had a rougher year than others. Microsoft cut 4,800 jobs in July, including 3,200 at Xbox, then 268 more Xbox jobs in September, and Xbox COO Helen Chiang left after 21 years. People in an org that has absorbed two rounds of cuts and lost its COO are more likely to take a first conversation.
At this level, sell scope. A Partner taking a year's salary from Microsoft doesn't need your cash to make the move work. Pitch a Head of Engineering or VP seat that starts in January.
FAQ
Can Microsoft security engineers take the voluntary buyout?
Reportedly not. Sources told The Verge that security did not participate, along with marketing and quantum. Microsoft hasn't published an official list, so confirm with each candidate. Recruit security engineers the way you would for any normal poach, without the severance lever.
When is the Microsoft voluntary exit offer deadline?
CNBC reports that employees decide in early December and leave on Dec 31. An Indian outlet reports a Dec 1 deadline for India staff, and Ghacks describes Dec 31 as the acceptance date. Plan around Dec 1 so your offers arrive before any version of the deadline.
What does Microsoft level 70 mean?
Level 70 is the top of the eligible range. It covers general managers, Distinguished Engineers and some people with vice president titles, but not corporate vice presidents. Below it, Senior SDEs sit at 63 to 64, Principal SDEs at 65 to 67 and Partners at 68 to 69.
Should I wait until January, when people have left?
No. By January the decision is made. Most eligible staff will have declined and stayed, and the 5 to 6% who left will be talking to every company at once. A signed offer before the deadline helps the candidate decide, keeps their severance intact, and puts you first in line.
The data behind this
Try it on the search you came here for
Stop building boolean strings. Just describe the person.
Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.
01Describe them
One plain sentence. Role, city, stack, stage, whatever matters to you.
02I read the web live
GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.
03You read the shortlist
Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.
- Staff backend engineers in NYC who shipped Rust in production
- Series A fintechs in SF under 50 people, growing headcount this year
- Maintainers of fast-growing Rust web frameworks on GitHub
- No boolean, no filters, no seat to buy. One box.
- Read at search time, so a profile updated yesterday counts today.
- Every step visible as it runs, every name with its reason.
500 free credits on sign-up. No card, no demo call. See real searches.