Microsoft's Rule of 70: 8,750 Self-Selecting Exits. Source by June 8.

Microsoft just opened the cleanest senior-IC talent window of the year, and most recruiters are going to miss it. On May 7, Chief People Officer Amy Coleman detailed the company's first-ever voluntary retirement program to employees: roughly 8,750 U.S. workers at Level 67 and below, whose age plus tenure totals 70 or more, have until June 8 to elect a buyout that ends with a fixed July 2 separation date. CFO Amy Hood booked a $900 million charge on the earnings call and confirmed headcount will keep declining through FY27.

This is not a layoff. The people walking out the door on July 2 are doing so on their own terms, with up to 39 weeks of pay, a year of fully covered healthcare, and a six to twelve month vesting tail still ticking. If you source senior technical talent, you have roughly 30 days to build the right list, and then a much longer game to play around when these people are actually free to start.

Why the "voluntary" framing changes everything

Layoff sourcing is hard for a reason most recruiters don't admit: the candidates are emotionally compressed and price-anchored to their last TC. They screen out anything that looks like a step down. They ghost. They take 90 days to come back to a thread that should have closed in two.

The Rule of 70 cohort is the inverse. These are people who looked at a spreadsheet, talked to a financial advisor (Avier and Gevers Wealth in Bellevue are already publishing detailed package walkthroughs aimed directly at this group), and decided the math worked. They are financially cushioned. They have a year of fully paid medical, dental, vision, and wellness, then four more years where they pay the premium themselves. They remain bonus-eligible. Many are in their early to mid 50s, not actually retiring, just exiting Microsoft on dignified terms.

That is the most receptive senior-engineer pool to hit the U.S. market since the 2023 Meta cuts, and unlike Meta in 2023, the volume is tiny.

8,750

The eligibility math, decoded for sourcers

The program is open to U.S. employees at Level 67 or below whose age and years of service add up to 70 or more as of June 30, 2026. Workers on sales and services incentive plans are excluded. The severance table tells you exactly who the company is paying to leave:

• L65 to L67: two weeks of base pay per six months of service, minimum eight weeks, maximum 39 weeks (about nine months).
• L64 and below: one week per six months, same floor and ceiling.
• Unvested stock: continues vesting for six additional months after separation. Employees with 24+ years of continuous service get up to twelve months.

That structure tells you the cohort's shape. L68 (Technical Fellow) and above are excluded, so the top of the pool is L67 Distinguished Engineer and Partner-level management. The bottom is whoever managed to hang on for 20+ years at L63. Sales is gone. What's left is principal-engineer and senior-EM density at the legacy product groups: Azure Core (already under a March hiring freeze), Windows and Devices, the Office Experience Org, Dynamics 365, Power Platform, and SQL Server.

Translation: this is a surgical strike on the cash-cow ICs and middle managers whose roles are being deprioritized in favor of Copilot bets. They know it. The pitch that lands is not "come do the same job at a smaller company." The pitch that lands is "come build the AI-native version of the system you spent 15 years operating."

What the eligible cohort actually looks like online

A query against our index for senior and principal-level engineers and managers in the U.S. with Microsoft in their current profile returns roughly 5,941 matches, with Microsoft itself dominant as the current company and the largest geographic clusters in Redmond, Seattle, Bellevue, Sammamish, the SF Bay Area, and New York. That 5,941 is the publicly visible slice of the ~8,750 eligible pool, and it tells you where to point your outreach: four metros account for almost all of it.

That's also where the standard tooling falls down. LinkedIn's filters can give you "Microsoft + Seattle + Principal Engineer" but they can't give you "Microsoft tenure 12+ years, last promotion before 2022, in a product group not on the AI org chart." Boolean strings don't encode career arcs. This is exactly the friction Refolk was built for: you describe the person in plain English (long-tenured Azure Core engineer in Redmond, principal level, not on a Copilot team) and get a ranked shortlist that respects all of those soft constraints at once.

The dates you need to put on a wall

Print these and tape them above your monitor. Every one of them is hard and most cannot be extended.

• April 23, 2026: program announced publicly.
• May 7, 2026: internal details distributed to eligible employees.
• June 8, 2026, 11:59 PM PDT: election deadline. Decide whether to participate.
• June 22, 2026: deadline to sign the separation agreement.
• June 29, 2026: OWBPA rescission deadline (workers over 40 get seven days after signing to revoke).
• July 1, 2026: last day of active employment.
• July 2, 2026: official separation date. Fixed.

If your goal is to influence the decision (get someone to elect in, knowing you have a soft landing for them), your window closes June 8. If your goal is to win the hire after they've already decided, you have through roughly mid-July before the best of this cohort is in serious conversation with two or three other shops.

The hidden non-compete nobody is pricing in

Here is the part most recruiters will get wrong. The six-month continued vesting (twelve months for 24-year veterans) means a meaningful slice of accepters will quietly delay any new full-time start until late 2026 or early 2027. Starting a new W-2 job in August doesn't necessarily kill the vest, but most people will want to consult a lawyer before they find out, and many comp packages from competitors will require them to forfeit Microsoft equity that's still cooking.

The founders who win this cohort are the ones offering advisory, fractional, or 1099 engagements between July and December, with the FTE conversation booked for January. That's a completely different sales motion than the one most in-house recruiters are running. If you can sit on someone for six months as a paid advisor while their Microsoft stock keeps vesting, you've outflanked every competitor trying to close a July start.

The six-month vesting tail is not a perk. It is a non-compete in disguise, and it reshapes the hiring sequence.

This is also where the "where will they go" question gets interesting. Meta cutting 10% (~8,000), Amazon's 30,000 across two rounds, and Block at 40%: Big Tech is not the destination. The realistic landing zones are mid-stage AI-native and infra startups (Databricks, Snowflake, Anthropic, Vercel, Pinecone, Modal, Together AI), private equity portcos that need a Director of Engineering who has actually shipped at scale, and defense and government tech (Anduril, Palantir, Shield AI) where a 20-year Microsoft pedigree is still a clearance accelerator and a credibility win.

Building the list in the 30 days you have

Here is the workflow that actually moves on this timeline.

Step 1: Define the eligible cohort, not just "senior Microsoft people"

The standard LinkedIn search returns tens of thousands of results, most of which are useless because they include sales, AI-team members who are not leaving, and people whose age plus tenure does not clear 70. You want long-tenured ICs and middle managers in non-AI product groups, in four metros, at L65 to L67 equivalent titles (Principal, Partner, Senior Director). Tenure is the proxy variable that does the most work here, because public profiles rarely list level directly. A 15-year Microsoft career with a Principal title since 2019 is a stronger Rule of 70 signal than any keyword combination.

Step 2: Segment by product group

A Power Platform principal in Redmond is a different sales motion than an Azure Core principal in Bellevue. Power Platform talent lands well at Retool, Airtable, and PLG-style startups. Azure Core talent lands at infra startups and hyperscaler competitors. Windows kernel engineers are an extremely thin pool that defense tech will pay a premium for. Group your list by product area before you write the first message.

Step 3: Write the message that respects the package

The worst outreach you can send right now: "Saw the news, are you open to chatting?" Every other recruiter is sending that. The right outreach acknowledges that they're sitting on a decision deadline, doesn't ask them to do anything before June 8, and offers a specific reason to talk in late July when their vest situation is clearer. Name the team you want them to build. Name the problem. Don't name a title.

Step 4: Run the list weekly, not once

The cohort is not static. Decisions are being made every day between May 7 and June 8, and the public signal (profile updates, "Open to" toggles) lags by weeks. A list you build May 10 and don't re-run will be 30% stale by June 8. This is the other reason we built Refolk the way we did: you save the query, and the shortlist updates as the underlying signal changes, so the list you pull on June 7 reflects who actually decided to walk.

$900M

What this means if you're a founder, not a recruiter

If you've been trying to hire a VP of Engineering or a founding infra engineer with real production scale experience, this is the closest the market will get to a free option in 2026. The cohort is small (~8,750), pre-qualified (they decided to leave), financially patient (they have a year of healthcare and up to nine months of severance), and concentrated in four metros you can fly to.

Three rules for founders specifically:

1. Don't try to close in July. Offer a paid advisory engagement, three months, scoped to a specific problem. Convert in Q4.
2. Skip the title conversation. A 22-year Microsoft Partner-level engineer does not care whether your title is "Founding Engineer" or "Principal." They care whether the problem is real and whether your existing team is good.
3. Recruit the spouse. Many of these accepters are dual-income households making a joint decision about whether to take a year off. The pitch that lands at the kitchen table is "interesting work, flexible time, no five-day RTO mandate," not "competitive equity."

The cohort that walks out on July 2 will not be on the market in six months. They will either be locked into advisory engagements, sitting on boards, or building their own thing. The window is the 30 days before the decision and the 30 days after. After that, the names you wanted are gone.

FAQ

How is the Rule of 70 program different from Microsoft's 2025 layoffs?

The 2025 cuts (~9,000 in July, ~6,000 in May, ~15,000 total) were involuntary RIFs with WARN filings and the usual displaced-worker dynamics. The Rule of 70 is voluntary, age and tenure gated, financially generous, and self-selecting. Candidates from this cohort are systematically more receptive to outreach than 2025 RIF candidates because they were not fired; they elected to leave. Different sales motion, different message, different timeline.

Why does sales being excluded matter for sourcing?

Workers on sales and services incentive plans cannot participate. That means anyone with an Account Executive, Solution Specialist, or CSAM title at Microsoft is not in this pool, regardless of how long they've been there. If you're filtering by tenure alone you will burn cycles on sales profiles. Filter for engineering, PM, design, research, and non-revenue management roles only. This is one of the reasons natural-language search beats Boolean for this cohort: "long-tenured Microsoft, not in sales or services" is one sentence in plain English and a brittle nested string in LinkedIn.

What's the right outreach timing?

For people you want to influence pre-decision: send by May 25, lead with a problem statement, do not ask for a commitment. For people post-decision: send the week of June 15 once the elections are visible internally, propose a late-July call. For founders offering advisory or fractional work: send the week of July 6, after the separation date but before they've signed anywhere else.

Will the visible LinkedIn footprint accurately reflect who took the package?

No, and that's the trap. Many accepters will not update profiles until late July or August, some not until they have a new role lined up. The "Open to Work" signal will badly under-represent this cohort because these are senior people who don't job-search publicly. You need to work the list proactively based on tenure, team, and level, not wait for the signal to surface. A profile that hasn't changed by July 10 may still belong to someone who walked out July 2.