T-Mobile's Third Cut in Five Months: 60-Day Window on Bellevue SDEs

T-Mobile just filed its third Washington WARN notice in five months: 363 workers in May, on top of 393 in February and an undisclosed IT reorg on March 27. The software development engineering team has been named, on the record, as the most-affected group across all three rounds. If you recruit Seattle engineers, the window to reach these people while they're still on payroll is measured in weeks, not quarters.

What actually happened, in order

Three rounds, all in the same Washington ESD database, all primarily out of Bellevue:

Round 1, February 2, 2026. T-Mobile filed a WARN for 393 workers across more than 200 job titles. Around 210 of those were senior- or director-level, plus seven VPs and SVPs (including a senior VP of talent and four VPs of legal). Official separation day: April 2.

Round 2, March 27, 2026. T-Mobile confirmed "further aligning" its IT org. The company refused to give a number; a tipster told GeekWire it was in the hundreds. No WARN required because it was structured in smaller chunks across sites.

Round 3, May 2026. Another 363 employees in Washington. The Fierce Network breakdown of the filing lists 21 senior systems architecture engineers, 17 senior business systems analysts, and 11 senior technical project managers among the eliminated titles. With 60-day WARN notice, separations land in early-to-mid July, right at the close of Q2.

1,156+

The strategic context is in T-Mobile's own filings: roughly $1.2 billion in cash outlays in 2026 for "network optimization and workforce restructuring," dropping to $1 billion in 2027. New CEO Srini Gopalan, who replaced Mike Sievert in November, is running the program. Monica Frohock, senior director of the Magenta Service Center, signed the WARN filings citing "changing business needs."

This is not a one-time correction. It's a multi-year program, and the SDE bench in Bellevue is the line item.

Why the WARN gap is the actual sourcing window

Here's the part most recruiters get wrong. They wait until "T-Mobile" turns into "Ex T-Mobile" on a LinkedIn profile. By then, you're 60 to 90 days late, the candidate has talked to seven other companies, and Amazon or Zillow already has a verbal out.

The WARN mechanic is the opposite signal. Affected employees were told in February that their last day was April 2. They were told in May that their last day is in July. They are job-searching today. They cannot start at your company today, but they can interview, negotiate, sign, and bridge into a start date that lines up perfectly with their separation.

For Round 3, that means the right time to reach a senior systems architecture engineer at T-Mobile is now, while their LinkedIn still says T-Mobile, current. If you filter your sourcing on "Open to Work" or "Ex T-Mobile," you will miss this entire cohort.

That filter problem is why we built Refolk: you describe the person in plain English, like "Senior or principal SDE at T-Mobile in Bellevue, still currently employed, with backend distributed systems experience," and get a ranked shortlist that includes people whose status hasn't flipped yet. You don't have to wait for the public signal.

The pool is more senior than you think

The default mental model for a telecom layoff is helpdesk and ops. That's not what this is.

T-Mobile is explicitly calling these rounds an "IT reorg," but the reporting is unambiguous about who's actually in the cuts. From MyNorthwest's reporting on the March wave: the software development engineering team was the most affected role, and the company has said it plans to use generative AI to replace corporate workers. Round 3's filing lists senior systems architecture engineers, senior software development engineers, and principal-level product platform people.

The seniority skew matters for two reasons:

1. These are titles that almost never enter the open market. Staff and principal engineers at a Fortune 100 telecom typically stay 8 to 12 years. When they leave voluntarily, they leave for a named offer at FAANG or a late-stage startup, not into the candidate pool. A forced cut at this level is a once-every-few-years event.
2. The narrative is favorable to the candidate. T-Mobile said the quiet part out loud: they're cutting to invest in genAI tooling. These aren't performance cuts. You can say that directly in an outreach message and it will land, because the candidate knows it's true.

The opportunity here is staff and principal engineers who would never have answered your InMail six months ago.