Expedia's Rumored 1,650 Cut: The 11-Day Window Before WARN
A TeamBlind rumor of 1,650 Expedia cuts is circulating before any WARN filing. Here is how to build the sourcing list in the 11-day window.
A TeamBlind rumor is circulating that Expedia will cut roughly 1,650 people in August 2026, about 10% of the company. No WARN notice has landed with Washington's Employment Security Department yet. The moment it does, every scraper on the internet publishes the same list inside 24 hours, and your head start is gone.
This post is about the sliver of time between "Blind post" and "public WARN," what you can actually build inside it, and why the real Expedia engineer pool visible on the open web is much smaller than the rumor implies.
The window is 11 to 14 days, not 60
The real sourcing window between a credible Blind rumor and a scraped WARN filing is about 11 to 14 days. The 60-day WARN clock protects workers, not recruiters.
Federal WARN requires employers with 100+ employees to give 60 calendar days of notice before a mass layoff of 50+ at a single site. Once filed, every free tracker publishes it. A WARN notice must contain a specific separation date or a 14-day separation window, and that 14-day window is the working period you actually get between the rumor circulating on TeamBlind and the filing landing on WARNTracker, Layoff Lookout, or GeekWire.
The prior confirmed 2026 round shows the pattern. Expedia filed with Washington ESD on January 28, 2026, confirming 162 role eliminations at its Seattle HQ, with separations scheduled between April 1 and April 19. The 14-day separation window was baked right into the filing.
The rumored 1,650 exceeds Expedia's entire 17-year WARN history
If the rumor is accurate, this single round would be larger than every Expedia WARN filing since 2009 combined. That is either a signal the number is inflated, or a signal the company will slice the round to dodge federal single-site triggers. Either way, it changes how you source.
Cumulative Expedia filings from October 2009 to April 2026 total 12 notices covering 1,627 workers across Florida, Texas, and Washington. A 1,650-person August round would be 1.01x that entire 17-year footprint.
The practical read: Expedia will likely file the August round in sub-500-employee tranches split across Seattle, Austin, and Springfield to stay under the 500-per-site federal reporting threshold. The WARN filings, when they come, will understate the true cut. You cannot wait for them.
A 1,650-person round would equal Expedia's entire 17-year WARN history in one filing cycle.
The real Expedia engineer pool is 215, not 1,650
In Refolk's index of professional profiles, a search for "Software Engineer" tied to Expedia in the US returns 215 matched profiles, of which 13 are currently at Expedia Group and 8 are in Greater Seattle. That is the addressable "still-there" pool, not the 1,650 in the rumor.
Layoff rumors always sound bigger than the sourceable pool underneath them. The ratio matters. About one open-web-visible engineer profile exists for every 7.7 rumored cuts. That is because the rumor number bundles PMs, UX designers, content designers, data engineers, and support functions along with the SWE/ML/DE roles most engineering recruiters actually want. The prior January filing spelled the mix out: product managers, software development engineers, user experience designers, data engineers, content designers, and others.
If you want the "still at Expedia" cohort specifically, you cannot rely on LinkedIn's "current company" filter alone. A share of any large-layoff cohort gets reshuffled internally rather than exiting, because the company spokesperson was explicit: "We are eliminating roles as well as opening some new roles as we remain disciplined about assessing the skills we need for the future." That is Expedia backfilling in real time, which means the profile that says "Expedia, present" today may say "Expedia, present, new team" in six weeks. De-risk the pipeline by 15 to 25% and start conversations earlier.
This is the exact gap Refolk closes. You describe the person in plain English ("software engineers at Expedia in Seattle who publish on GitHub and have shipped services in Java or Kotlin"), and get a ranked shortlist that pulls from GitHub, LinkedIn, and the open web at once, before any WARN tracker publishes.
The comparable dataset, at a glance
Every claim above rolls into one table. If you screenshot one thing for your VP of Talent, make it this.
| Cohort | Value | Source or method |
|---|---|---|
| Expedia US engineers surfaced (SWE/ML/DE) | 215 profiles | Refolk index, Expedia plus engineering titles |
| Of which currently at Expedia Group | 13 | Same query, top-companies breakdown |
| Seattle-area SWE/ML/DE visible on open web | 186 profiles | Refolk index, Seattle plus engineering titles |
| Rumored Aug 2026 cut size | ~1,650 (~10%) | TeamBlind layoffs tracker |
| Prior confirmed 2026 WA WARN | 162 roles, Apr 1-19 window | Washington ESD via GeekWire |
| Total Expedia WARN filings 2009-2026 | 12 notices, 1,627 workers | warntracker.com |
| Rumored round vs entire WARN history | 1.01x | 1,650 divided by 1,627 |
| Open-web profiles per rumored cut | ~1 per 7.7 | 215 divided by 1,650 |
Pre-build the boolean now, from the January filing
The single best predictor of what titles get cut in August is what titles got cut in April. Build the shortlist against the exact January 2026 mix at Expedia today, before the next filing, because the composition is unlikely to shift.
The prior 162-role round hit product managers, software development engineers, user experience designers, data engineers, and content designers. Practical steps that fit inside an 11-day window:
- Lock the title list. SWE, Senior SWE, Staff SWE, ML Engineer, Data Engineer, Applied Scientist, UX Designer, Content Designer, Senior PM, Group PM. Skip the recruiter and marketing titles unless you are staffing those roles.
- Pull the "still there" cohort first. Refolk's index shows 13 currently-at-Expedia engineers in the SWE query alone. Get those messaged in the first 72 hours after rumor surfacing, before Blind chatter alerts them to update banners.
- Cross-reference GitHub activity. Filter for recent commits in the languages the target team uses to skip the middle-management layer.
- Split by geography. Seattle HQ is 8 of the 13. The rest are remote, mostly in Washington. Cuts follow physical presence.
- Queue the outbound messages, do not send until the filing lands. The message hit rate on "I saw the WARN filing" tends to outperform "I saw a rumor" for candidates who value discretion.
Where displaced Expedians will land
Sourcing before WARN is only half the game. The other half is knowing which competing offers you are up against, and the answer is Microsoft, Amazon, AWS, Google, and Apple.
In Refolk's parallel index of 186 Seattle-area SWE/ML/DE profiles, the top current employers are Microsoft (6), Amazon (4), AWS (2), Google (2), and Apple (2). Those are the five doors an ex-Expedian is most likely to walk through if nobody else moves first. If your company is not one of those five, your pitch needs to be built around something the FAANG offers cannot match: equity upside, scope, remote flexibility, or speed to hire.
Seattle's absorption capacity is unusually thin
The absorbing market cannot soak up a 1,650-person round the way it could in 2021. Puget Sound is deep into a synchronized contraction, and out-of-market roles will convert faster than in normal years.
T-Mobile cut 393 statewide positions earlier this year. Oracle eliminated 491 Washington jobs, mostly in downtown Seattle. Microsoft, Amazon, Snap, LinkedIn, and Epic Games have all trimmed Puget Sound headcount in 2026. Seattle now leads the world in AI-linked tech job losses. Expeditors International cut 230 Seattle-area tech jobs in a single filing, ending a four-decade no-layoff tradition.
The mechanism this creates: displaced Expedians are unusually mobile. If you are hiring from Denver, Austin, NYC, or fully remote, your response rate on ex-Expedia outbound over the next quarter should be materially higher than your baseline, because the local absorption pipeline is clogged.
The playbook, compressed
Rumor-stage sourcing is a race between how fast you can convert a Blind screenshot into a ranked shortlist and how fast a WARN filing hits GeekWire. Three moves compress the timeline:
- Treat the January filing as the schema for August. Same titles, same HQ concentration, same 14-day separation window. Pre-build the list.
- Do not wait for the WARN feeds. Layoff Lookout's Washington ESD feed updates daily. WARNTracker runs 6 months behind on some feeds. The Blind-to-scraper delta is where the pool is quiet.
- Message the "still there" cohort first. In Refolk's index that is 13 people. Small enough to hand-write. Large enough to matter if two convert.
The Expedia story will get picked up by every generalist recruiting newsletter the day the WARN drops. That day is the day the arbitrage ends. Use Refolk to turn the plain-English brief into the actual list before the trackers do.
FAQ
Is the 1,650-person Expedia rumor confirmed?
No. As of publication, no WARN notice has been filed with Washington's Employment Security Department for the August 2026 date. The rumor originates from a TeamBlind layoffs tracker post citing ~1,650 cuts (roughly 10% of the workforce). The prior confirmed 2026 filing, dated January 28, covered 162 roles between April 1 and April 19. Treat the August number as directional, not final. Even if the true number is half the rumor, it still exceeds the January round by 5x.
How do I source engineers before a WARN filing legally?
Nothing about pre-WARN outbound is illegal. Public profiles are public. What matters is who you contact and how. Message individuals through LinkedIn, X, or their listed email or GitHub profile. Do not contact people via a work address once they have been notified internally, and do not reference non-public information you should not have. The 11 to 14-day arbitrage exists because sourcing from open-web signals is faster than the WARN scraper cycle, not because you are getting a leaked internal list.
What titles should I prioritize on an Expedia engineer layoff list?
Match the January 2026 filing exactly: software development engineers, data engineers, ML engineers, product managers, UX designers, and content designers, with a bias toward Seattle-based and Washington-remote profiles. That mix is unlikely to shift materially for the August round. Refolk's index shows 215 US Expedia engineers surfaced against SWE/ML/DE keywords, with 13 still currently at Expedia Group and 8 in the greater Seattle area. Start with the still-there cohort, then work backward through the alumni.
Who competes with me for displaced Expedia engineers?
The top current employers for Seattle-area SWE/ML/DE profiles in Refolk's index are Microsoft (6), Amazon (4), AWS (2), Google (2), and Apple (2). Those five names will produce most of the competing offers. If you are not one of them, lead with scope, equity, or remote flexibility rather than trying to match compensation. And move fast: Seattle's absorption capacity is thin in 2026, so the strongest candidates will attract competing interest quickly after any confirmed filing.