Employee brief · 5 min read
Published on Flags Event source
Red flag

Expedia begins 58 permanent Seattle layoffs across tech roles

Expedia Group is beginning a previously announced round of 58 permanent layoffs at its Seattle campus, according to a Washington State WARN notice received on September 22. The notice lists separation dates from November 21 through December 1, 2026, making this an older disclosure whose employment impact starts now rather than a new announcement. Expedia said it provided 60 days' notice and that some of the reductions resulted from relocation or work being contracted out. The affected positions span technical and business functions, including software development engineers, data scientists, a senior machine-learning scientist, a principal architect, technical program managers, analytics, finance, compliance and partner-facing roles. The filing says the workers are not represented by a union and have no bumping rights. It does not establish that all 58 roles are engineering positions, identify the vendors or destinations receiving contracted work, or describe a companywide layoff program. The confirmed scope is one Seattle location and the specific jobs listed in the official notice.

Candidate lensMaterial caution
Leans toward risk
OpportunityContextRisk

Company context

The wider Expedia Group picture.

Evidence-weighted · 1 verified signal
Work outlook32/100Caution
Signal mix
0 positive0 mixed1 caution
Explore the evidenceFull company profile↗

Signal snapshot

01Event typeLayoffs
02Event dateSep 22, 2026
03Reported scopeUnited States
04Source confidenceHigh

Employer analysis

What this layoffs signal says about working at Expedia Group

The event reported by Washington State Employment Security Department on Sep 22, 2026 is one verified data point—not a complete description of every team at Expedia Group. Its value for a candidate is that it reveals a current management priority, constraint or change in direction that can be tested during the hiring process.

For someone considering a role, the practical question is whether the advertised position is protected from the reported pressure, approved as replacement or growth headcount, and supported by a budget that survives the current restructuring cycle. Team-level conditions can differ materially from the company-wide signal, so the evidence should shape due diligence rather than replace it.

Candidate checklist

Four details to verify before accepting an offer

Use the public signal as a starting point, then ask for specific evidence about the role you are considering.

  1. HeadcountIs the position approved growth, a replacement or a backfill after a reorganisation?
  2. BudgetHas the team budget or hiring plan changed since this event was reported?
  3. ExposureWhich functions, locations and reporting lines are directly affected by the change?
  4. ExecutionWhat must this team deliver over the next 6–12 months, and how will success be measured?

Confirmed facts

Expedia Group is beginning a previously announced round of 58 permanent layoffs at its Seattle campus, according to a Washington State WARN notice received on September 22. The notice lists separation dates from November 21 through December 1, 2026, making this an older disclosure whose employment impact starts now rather than a new announcement. Expedia said it provided 60 days' notice and that some of the reductions resulted from relocation or work being contracted out. The affected positions span technical and business functions, including software development engineers, data scientists, a senior machine-learning scientist, a principal architect, technical program managers, analytics, finance, compliance and partner-facing roles. The filing says the workers are not represented by a union and have no bumping rights. It does not establish that all 58 roles are engineering positions, identify the vendors or destinations receiving contracted work, or describe a companywide layoff program. The confirmed scope is one Seattle location and the specific jobs listed in the official notice.

Verify with Washington State Employment Security Department ↗

What remains unknown

The public report may not resolve the exact team, role-level exposure or implementation timing. Confirm those details directly before treating an open position as protected.

What this means for employees

For Seattle-based technology candidates, this notice is useful because it shows that Expedia's workforce changes reach beyond general administration into software, architecture, machine learning, data and technical program management. The reference to relocation and contracting out suggests that the location and employment model of a team may matter as much as the role title. It does not prove that Expedia has stopped hiring in Seattle or that every group faces the same risk; WARN notices describe affected positions, not the full internal labor market. Applicants should therefore compare open roles with the functions listed in the notice and ask whether the work belongs to a growing product team, replaces a departed employee, or is moving between locations or vendors. Current employees may face knowledge-transfer duties and redistributed workloads during the November 21–December 1 separation window. Candidates should also clarify the team's expected headcount after the changes, its dependence on contractors and whether strategic ownership remains local. Those answers will be more informative than relying on the Expedia brand or a job posting alone.

01

Flags verdict

Proceed with extra diligence

This signal raises a material stability question. Understand the scope, timing and whether the position is protected before deciding.

Ask this in the interview

Is this role on a team affected by the Seattle relocation or outsourcing changes, and what will the team's employee-versus-contractor mix and local headcount be after December 1?

Editorial standard Flags separates confirmed facts from candidate-focused interpretation. The original source is always linked alongside the analysis. Read our methodology →