Microsoft's First Buyout in 51 Years Is a Tenure List. Trackers Will Miss 8,750 Names.
Microsoft's Rule-of-70 voluntary buyout creates 8,750 long-tenured exits that won't hit layoffs.fyi. Here is how to source them before May 7.
CNBC and GeekWire confirmed this month that Microsoft is running its first-ever voluntary retirement program, open to U.S. employees at Level 67 (senior director) and below whose age plus tenure totals 70 or more. About 7% of the U.S. workforce, roughly 8,750 people, qualify. If you are waiting for this to show up on layoffs.fyi or in a WARN filing, you are already late.
This is not a RIF. It is a tenure-weighted, self-selected exit, and it produces a fundamentally different talent pool than anything the trackers have surfaced in 2026. The sourcing window is narrow: details land May 7, the acceptance window is 30 days, and ADEA release periods push actual departure dates into July and August. The people who will take this offer are deciding right now.
Why the Rule of 70 inverts your sourcing heuristic
Recruiters trained on growth-era playbooks chase candidates with 2 to 4 year tenure stripes and recent job changes. The Microsoft buyout pool is the exact opposite. To clear age plus years equal to 70, a candidate looks like a 45-year-old with 25 years of service, or a 52-year-old with 18 years. Yahoo Finance walked through both examples. Either way, you are looking at a single, dominant Microsoft tenure stripe on the resume.
Most boolean strings filter these people out. "Job change in the last 12 months," "3+ companies," "tenure under 6 years," all common quality filters, eliminate the entire Rule-of-70 cohort by construction. If your ATS or sourcing tool is scoring on velocity, it is actively penalizing the highest-signal pool Microsoft has released in 51 years.
Long tenure at Microsoft is a quality signal, not a staleness signal. Survivors of 18 to 25 years cleared both the stack-rank era and the Connects era. Many of them own the institutional knowledge that AI infrastructure startups, defense-tech buyers, and regulated industries (banks, hospitals, utilities) are paying premium for: Windows kernel, Azure internals, Exchange, Active Directory, SQL Server, and the Office C++ codebases. That is a different shopping list than "ex-FAANG AI engineer," and the buyers are different too.
The trackers will miss this entirely
Here is the structural problem. Layoffs.fyi shows 98 tech companies cut more than 92,000 workers in 2026. None of those numbers will move when Microsoft's buyout closes. WARN filings only trigger on involuntary mass layoffs above a threshold. Voluntary, individually-negotiated exits get logged as ordinary attrition in the company's quarterly disclosures, if at all.
That means three things for your pipeline:
- No public list. You will not get a CSV. There is no equivalent of the Bungie or Wix WARN drop.
- No "Open to Work" wave. Long-tenured employees who chose to leave tend not to flag the green ring. Many will quietly negotiate their next role before their last day in August.
- No clean departure date. ADEA release windows (45 days to consider, 7 days to revoke) stagger exits across July and August. Your usual "ex-Microsoft, departed Q3" filter catches a fraction of the cohort.
Sourcers who treat this like a normal layoff event will be working from a list that doesn't exist. The work is upstream: identify Rule-of-70-eligible profiles inside Microsoft now, while they are still technically employed, and build the relationship before May 7 turns into an accepted offer somewhere else.
What the eligible pool actually looks like
The research is unambiguous on geography and org. Microsoft froze hiring in Azure cloud and North American sales in March 2026, while explicitly exempting AI and Copilot teams. That hiring-freeze map is also the buyout uptake map. Expect concentration in:
- Redmond and Greater Seattle infrastructure teams. On-prem server, Windows client, Exchange, AD, SQL Server.
- Enterprise sales engineering and field CTO roles (excluding those on sales incentive plans, who are out of scope).
- Office and Windows client orgs, where the C++ codebases have been migration targets for years.
- Azure foundational infrastructure, the parts that predate the Copilot rebuild.
The AI org itself is largely out. Copilot and Azure AI teams are still hiring aggressively, and engineers there have less reason to take a one-time package when stock and scope are accelerating. The pool skews toward the orgs Microsoft is systematically automating or deprecating, which is exactly why the Rule of 70 is the right filter from Microsoft's perspective and the wrong filter from a competitor's.
Our own index shows roughly 2,745 U.S.-based senior and director-level engineers currently tagged to Microsoft in titles like Principal Software Engineer and Principal Program Manager. The Redmond cluster dominates, the Bay Area is second. That is the population to comb through before May 7.
The leveling detail that matters
Level 67 is the ceiling. In Microsoft's ladder, that is senior director or partner-track IC. Everything below is in scope: L63 to L67 ICs (principal and partner engineers), L62 to L67 managers (senior director and below), and most program management equivalents. If you've been sourcing with a "principal and above" filter at Microsoft, your entire candidate set is potentially in the pool.
The no-non-compete advantage you have for about 90 days
GeekWire reported what is, for recruiters, the single most important line in the package: there are not expected to be any restrictions on future employment for those who take the deal. Compare that to a normal RIF severance package, which routinely attaches 6 to 12 month non-solicits and, in some states, non-competes that survive the cut.
A senior Microsoft engineer with no non-compete and a one-time package in hand is the cleanest hire competitors will see all year.