Expedia's Rumored Fifth Round: The Seattle ML Pool Is 10 People

A Blind layoff-tracker post lists Expedia as a rumored August 2026 global cut of about 1,650 people, or 10% of the company. It would be the fifth reduction event since 2024, and no mainstream outlet has confirmed it. That gap between rumor and press is the window: 30 to 60 days in which sourcers who know the names can move before every Seattle recruiter runs the same boolean.

The rumor, the math, and the window

Blind's public layoff tracker currently tags Expedia with a suspected August 2026 global cut of ~1,650 (10%), sourced entirely from user submissions. Treat it as a sourcing signal, not journalism - Blind itself notes the tracker is "built solely on information submitted by Blind users."

Here is the timing mechanism nobody spells out. Expedia's third round in this arc followed a clean sequence:

1. Internal announcement, January 26, 2026.
2. WARN filing with Washington's Employment Security Department on January 28, naming 162 Seattle HQ and WA-remote roles.
3. Actual separation dates between April 1 and April 19, 2026.

That is a roughly 10-week gap from public confirmation to people being on the market, and Blind rumors typically precede the WARN by another 30 to 60 days. If the August 2026 rumor holds, ex-Expedia ML candidates hit the open market in October or November. Recruiters who wait for Skift or GeekWire to confirm are working the same list 60 days late.

1,650

Why Blind beats WARN as a leading indicator

Blind rumors lead WARN filings by 60 to 90 days because WARN only fires once legal counsel confirms scope and site thresholds, while Blind fires the moment somebody in a Slack channel hears a number.

That has three consequences for recruiters:

• Blind surfaces teams, not individuals. Rumors indicate which orgs are being restructured before HR notifies anyone.
• WARN gives counts and locations but not titles. Washington's ESD portal confirmed 162 January cuts. Axios later reported nearly 50 had "software development" in the title and nearly 30 were director-level. That level of detail took a week of reporting after the filing.
• Skift and GeekWire are the second signal. Both broke the January round between January 26 and January 29. If you are reading them, you are already in the fair fight.

The play is to build the target list off Blind now, then verify against WARN when it lands. This is the exact gap Refolk closes: instead of running the same "current company: Expedia AND title: machine learning" LinkedIn search every other Seattle recruiter is running, you describe the profile in plain English and get a ranked shortlist across GitHub, LinkedIn, and the open web in one pass.

The actual Seattle ML pool at Expedia is 10 people

The hireable Seattle ML pool at Expedia is not a funnel, it is a whiteboard list. In Refolk's index, searching current Expedia headcount by ML-adjacent titles (Machine Learning Engineer, Applied Scientist, Senior Data Scientist) in the US returns 25 total profiles, of which 19 are currently at Expedia. Seattle metro accounts for 10 of the 25: seven in Seattle proper, three in the Greater Seattle Area.

Widen the definition to include Data Engineers and the number is still two-digit:

Top current titles inside Expedia: Machine Learning Engineer (14) and Senior Data Scientist (9) on the narrow query; Data Engineer (15) and Machine Learning Engineer (8) on the wider one.

The takeaway for anyone doing OTA machine learning hiring: this is a name-by-name exercise. There is no boolean that finds "the good ones" because the pool is small enough that every profile matters individually. If the rumored 10% cut hits ML proportionally against the 21 currently-at-Expedia ML/DE profiles, that is roughly 2 people. If it skews like January's cut (which took an estimated 10% of the entire tech team), it can shrink the discoverable pool faster than the Seattle market can absorb.

10

These cuts are AI-driven, not distress-driven

The people being cut are being cut because they built ML systems Expedia now considers replaceable, not because the business is soft. Revenue grew 9% to $4.4 billion in Q3 last year, adjusted net income grew 19% year over year, and gross bookings were up 12% to $30.7 billion. On the earnings call, CEO Ariane Gorin described AI as a "step function" opportunity to boost team efficiency and effectiveness over time.

That framing matters for how you approach outbound. Ex-Expedia ML engineers coming out of an AI-justified restructuring split into two useful segments:

• GenAI-native. Engineers who were building the LLM and agent systems Gorin is investing behind. These are the survivors of prior rounds and the most competitive hires.
• GenAI-displaced. Engineers whose classical ML systems (ranking, pricing, forecasting) are being folded into GenAI-driven replacements. Deep production experience, often more senior, often cheaper to close because they read the writing on the wall six months ago.

Segment your outreach on that axis. A generic "we saw the news" note performs worse than a message that acknowledges which side of the restructuring the candidate sat on.

Director-heavy cuts mean senior ICs come loose

January's round included nearly 30 director-level positions out of 162, roughly 18% of the cut. That is unusually top-heavy, and the rumored August round is likely to shake loose more of the same profile: expensive senior ICs and player-coach directors that founders under-hire because they assume unavailability.

For a Series B or C engineering team, this is the moment those hires become reachable. Two practical filters:

• Look for directors with a recent IC commit history on GitHub. They will take an IC-plus role at a smaller company; pure people-managers will not.
• Filter on tenure at Expedia of 4+ years. Long-tenure directors coming out of a restructuring are more open to a step down in title than short-tenure ones who will chase the same title at Amazon or Microsoft.

Where this talent actually lands

OTA-to-OTA is not the obvious next stop. Airbnb's discoverable US ML pool is only about 2.2x Expedia's on the same Refolk query, concentrated in the SF Bay Area, and Booking Holdings runs mostly out of Europe. The realistic landing pads for laid-off Expedia ML talent in Seattle are:

• Amazon and Microsoft, both of which are hiring aggressively into AI orgs even as they cut elsewhere.
• Seattle-area AI startups absorbing engineers from the 30,000+ Seattle tech cuts announced in 2025 (per layoffs.fyi), driven overwhelmingly by Microsoft, Amazon, and Blue Origin.
• Adjacent enterprises in travel-tech, ads, and marketplace that never make the sourcing shortlist because recruiters default to the FAANG-to-FAANG lane.

For a smaller buyer, the first-mover advantage is real. The 10 Seattle-based Expedia ML engineers in Refolk's index will not all be on the market, and the ones who are will field Amazon and Microsoft outreach within a week. If you are a Series B founder who wants one of them, you need to be in the inbox before the WARN hits the news, with a specific role and a specific reason you are writing to them by name. Refolk is built for that: describe the profile, get the list, personalise on what the candidate actually shipped.

The five-round arc, in context

The rumored August 2026 cut would be the fifth reduction event since 2024:

1. February 2024: nearly 1,500 roles cut following the unification of Expedia, Hotels.com, and Vrbo.
2. 2025: reportedly about 3% of the workforce, per Skift.
3. January 2026: 162 WARN-filed roles in Washington, ~50 SDE titles and ~30 directors.
4. A subsequent round referenced in the broader arc.
5. Rumored August 2026: ~1,650 globally, per Blind.

The pattern is smaller, more surgical cuts against a growing top line. That is unusual, and it changes the sourcing thesis. In a distress layoff, you get a flood of mid-quality talent and a short window. In an AI-restructuring layoff at a growing company, you get smaller batches of specifically-skilled ML people, released repeatedly, over an 18 to 24 month arc. You do not build a campaign for this. You build a standing list and refresh it every time Blind lights up.

FAQ

How reliable are Blind's layoff rumors as a sourcing signal? Reliable enough to act on, not reliable enough to publish. Blind states plainly that the tracker is built entirely from user submissions. For recruiters, that is fine - you are building a target list, not writing a news story. The January 2026 round appeared on Blind before it appeared in the WARN portal, and the WARN filing landed before Axios and GeekWire reported title-level detail. Use Blind to start work, use WARN to confirm scope, use Skift and GeekWire to confirm framing.

Should I contact currently-employed Expedia ML engineers now, or wait for the cut? Contact them now, but not about the layoff. The 19 currently-at-Expedia ML/Applied Scientist/Sr DS profiles in Refolk's index are watching the same Blind post you are. A message that references their actual work lands; a message that references the rumor reads as ghoulish. If they respond, you are in the conversation before the cut. If they do not, you are still in their inbox before the flood.

Why is the Airbnb comparison relevant if I am hiring in Seattle? Because it tells you where the talent will not go. Airbnb's US ML pool is 2.2x Expedia's on the same query and concentrated in SF, which means Airbnb is not a realistic Seattle landing pad for most ex-Expedia ML engineers. The competition for these candidates is Amazon, Microsoft, and Seattle-area AI startups, not other OTAs. Price and pitch accordingly.

What titles should I actually search for beyond "Machine Learning Engineer"? Applied Scientist and Senior Data Scientist are the two title conventions that Expedia uses interchangeably with ML Engineer for production ML work. Data Engineer catches another slice of the pipeline-heavy roles that were named in January's WARN. Director of Data Science and Principal Applied Scientist are the two senior titles most likely to appear in a director-heavy round. Run those five titles and you will have the pool.