Refolk
June 11, 2026·8 min read

Expeditors' 47-Year Streak Just Broke. 230 Walk Aug 8, And You Have 60 Days.

Expeditors filed a WARN on June 8 cutting 230 Seattle-area engineers. Here's the sourcing playbook for supply-chain software talent, by office and by date.

Expeditors layoffs 2026Seattle logistics engineerssupply chain software talentWARN Act Washington techBellevue tech sourcing
Expeditors' 47-Year Streak Just Broke. 230 Walk Aug 8, And You Have 60 Days.

On June 8, 2026, Expeditors International filed a WARN notice ending a 47-year no-layoff tradition, releasing 230 technologists from its U.S. Global Technology Department across five Washington offices. First separations land Aug 8, with the rest spread through Dec 31. If you recruit supply-chain software talent in the Puget Sound, this is the cleanest, most time-boxed liquidity event you will see this year, and the window to act started the day the notice was signed.

What the WARN actually says

The filing was signed by SVP and CIO Courtney Hawkins, who joined Expeditors in 2024 after stops at Starbucks, Nike, Nordstrom, and Zulily. It attributes the cuts to "a workplace restructuring involving the Company's U.S. Global Technology Department." The office-level breakdown matters more than the headline number, because it tells you where to point your sourcing:

  • Downtown Seattle: ~68
  • Federal Way: 66
  • Lynnwood: 59
  • Bellevue: 35
  • Airway Heights (near Spokane): 2

Role mix, per laid-off employees talking to GeekWire and KIRO 7: software developers, QA testers, project managers, and business analysts. A "vast majority" are developers. Notice date is June 8, first separations Aug 8, all wrapped by Dec 31.

The 230 represents roughly 15% of Expeditors' global tech workforce. The company had about 1,500 in information systems worldwide as of March 31, 2026, up from 1,360 a year prior. Read that again: they were growing IS headcount until the moment they weren't. Corporate scale for context: ~20,000 employees worldwide, $11.07B in 2025 revenue, $810M in 2025 net income. This is not a distressed company. This is a deliberate restructuring at a profitable one.

47
Years Expeditors went without a layoff
The streak survived 2008-09, COVID, and the 2022-23 tech cuts. It ended on June 8.

The smoking-gun timeline

Sometime between January and May 2026, Expeditors quietly edited its corporate-history page. The phrase "our no layoff policy" became "our short-term no layoff policy." The Internet Archive caught it. This is the single most important piece of context for any recruiter working Expeditors layoffs 2026 as a sourcing event, because it tells you the internal employees who pay attention to these things have been quietly interviewing for months.

The implication is uncomfortable but real: the most marketable people are already in pipelines somewhere. If you start your outreach in August when "ex-Expeditors" tags begin appearing on LinkedIn, you are sourcing the second tier. The window that matters is now, between the June 8 notice and the Aug 8 first-separation date.

Why this pool is different from Meta, Amazon, or Cisco cuts

Most layoff-sourcing playbooks treat displaced engineers as fungible. This one is not. Expeditors' 2021 DEF 14A proxy describes a culture where senior leaders average 24 to 30 years of service and the company "promotes from within." Peter J. Rose, co-founder and CEO from 1988 to 2013, architected the original no-layoff policy. Current CEO Daniel R. Wall, who took over April 1, 2025, started as a messenger in 1987.

That culture produced engineers who have spent 10, 20, sometimes 30 years inside one of the largest freight-forwarding platforms on the planet. They know customs brokerage workflows, EDI and AS2 plumbing, ocean and air manifest integration, and the inside of the U.S. Customs ACE system at a depth that AI-native logistics startups simply cannot hire elsewhere.

These are not displaced devs. They are domain experts in a field where domain knowledge takes a decade to build.

If you are sourcing for Flexport, Flexe, Project44, FourKites, e2open, Blue Yonder, Descartes Systems Group, or Intelage, this is your roster. The freight-forwarding domain knowledge that's hard to find outside legacy 3PLs just walked into the open market on a published calendar.

The comp arbitrage nobody is pricing

Glassdoor reviews of Expeditors repeatedly flag pay as "well below industry standard." Combine that with promote-from-within culture and 20-plus-year tenures and you get engineers who are likely 20% to 40% under Seattle market comp. A logistics-tech buyer offering Flexport or Convoy-tier numbers can win these candidates on a single conversation, without having to sell mission, without having to negotiate around competing offers from FAANG.

This is the rarest configuration in tech recruiting: deep domain talent, no inflated comp baseline, a published exit date, and a state-run rapid-response program (Washington ESD) about to plug them into resume workshops. If you are a recruiter at a Series B logistics platform who has been losing offers to Amazon Global Logistics on comp for two years, August 8 is your reset.

How to source against a WARN, not a LinkedIn filter

The standard move on a layoff story is to set a LinkedIn alert for "ex-Expeditors" and wait. Don't. Here's the actual sequence.

Source the still-employed, not the separated

Between June 8 and Aug 8, these engineers still have corporate email, SSO access to their work portfolios, and Slack accounts. They have not signed severance paperwork, which means they have not signed non-solicits or non-disparagement clauses. They are also at their most receptive to outbound: the notice just landed, the no-layoff myth just died, and they are watching colleagues update resumes in real time.

Run your outreach against current Expeditors employees in the affected job families, in the five named cities, with tenure of 5+ years. Describing that filter in a Boolean string on LinkedIn Recruiter is painful and brittle. Describing it in English is fast, which is why we built Refolk: you ask in plain English ("software engineers and QA at Expeditors in Seattle, Federal Way, Lynnwood, Bellevue, or Airway Heights, 5+ years tenure") and get a ranked shortlist across GitHub, LinkedIn, and the open web in one pass.

Don't sleep on Federal Way and Lynnwood

The two largest cuts after downtown Seattle are Federal Way (66) and Lynnwood (59). These offices are systematically underserved by Seattle and Bellevue tech sourcing teams who default to downtown. If your firm can offer remote or a non-downtown hub, you have a geographic moat against every other recruiter working the same WARN.

Map the diaspora, including India

Reddit threads, the active thelayoff.com Expeditors thread, and LinkedIn chatter suggest cuts outside Washington as well, with concern in India in particular. The 230 WA figure undercounts the true reachable diaspora. If your role can be filled outside the U.S., widen the search beyond the WARN list.

Use the state's rapid-response program as a channel, not a competitor

Washington ESD's Rapid Response program kicks in automatically at WARN filings. They will run resume workshops and job fairs for these 230 employees. Show up. Sponsor sessions. CSCMP's Puget Sound Roundtable, FreightWaves' reader community, and The Loadstar are the other channels that index on supply chain software talent specifically, rather than generic tech.

The buyers already circling

If you want to know who you are competing with for this roster, here's the in-region list of likely absorbers:

  • Flexe (Seattle, flexible warehousing, 1,300-plus warehouse operator network)
  • Flexport (Bellevue and SF, the most obvious destination for freight-forwarding domain knowledge)
  • Amazon Global Logistics (Bellevue)
  • TikTok USDS Global E-Commerce Supply Chain & Logistics (Seattle)
  • Intelage (Seattle, global-trade platform)
  • FlavorCloud (Seattle, cross-border)
  • Booster (fleet and fuel logistics)
  • Convoy alumni networks, now scattered across Robinson, Waymo, and elsewhere

Nationally, Project44, FourKites, e2open, Blue Yonder, and Descartes are the other obvious bidders. If you are at any of those companies and you do not have an Expeditors-specific sourcing plan filed by July 1, you are late.

The calendar to put on the wall

  • June 8, 2026: WARN filed. Notice delivered. Outreach window opens.
  • June 8 to Aug 7: Best window. Engineers still employed, unencumbered by severance paperwork, most receptive to outbound.
  • Aug 8, 2026: First separations. LinkedIn "Open to Work" tags start appearing. Public competition begins.
  • Aug 8 to Dec 31: Rolling separations through year-end. Second-tier candidates still available, but pricing has corrected upward.
  • Dec 31, 2026: Cuts complete. The 47-year streak is officially a historical footnote.

The 60 days from notice to first separation is the entire game. Most recruiters working WARN Act Washington tech filings treat the notice date as a pre-event and the separation date as the start. Flip that. The notice is the start, and Aug 8 is when you have already lost the engineers you most wanted.

What good outreach looks like here

Skip the "I saw the news, sorry to hear it" opener. These are 20-year company veterans who just watched a 47-year promise evaporate. They have heard the condolence note from six recruiters already and it reads as opportunism.

Lead with the domain. Reference customs brokerage, ocean freight visibility, AS2 integration, ACE filings, or whatever your platform actually does. Name a specific Expeditors product or workflow if you know it. Ask one question about their work, not three about their availability.

For the 35 engineers in Bellevue, Bellevue tech sourcing is a small enough pool that you can run a personalized outreach campaign in an afternoon if your tooling lets you describe the target in English instead of building a 14-clause Boolean string. Refolk handles that part; you handle the message.

The companies that win this roster will be the ones that treat these 230 names as a finite, named, time-boxed list, not as a generic post-layoff pool. The WARN filing handed everyone the same calendar. The differentiation is entirely in speed and specificity.

FAQ

When should I start outreach to Expeditors employees?

Immediately. The WARN notice was June 8 and first separations are Aug 8, which means there is a roughly 60-day window where targeted employees are still employed, have not signed severance or non-solicit paperwork, and are most receptive to outbound. Waiting until "ex-Expeditors" tags appear on LinkedIn in August means you are competing for the second tier.

Which Expeditors offices are most underserved by recruiters?

Federal Way (66 cuts) and Lynnwood (59 cuts) are the second and third largest, but they sit outside the default Seattle and Bellevue downtown sourcing radius. Most local recruiters will concentrate on the ~68 downtown Seattle and 35 Bellevue cuts. If your role supports candidates from those secondary offices, you have meaningfully less competition.

What roles are actually being cut?

Per the WARN filing and laid-off employees speaking to GeekWire and KIRO 7, the mix is software developers, QA testers, project managers, and business analysts, with a "vast majority" being developers. The deeper value is domain expertise in freight forwarding, customs brokerage, EDI/AS2 integration, and global trade workflows that's hard to find outside legacy 3PLs.

Are these candidates expensive?

Probably not, relative to your Seattle benchmarks. Glassdoor reviews consistently flag Expeditors compensation as below industry standard, and the company's promote-from-within culture means long-tenured engineers have rarely tested the open market. A logistics-tech buyer offering Flexport or Convoy-tier comp can often close on a single number, without the negotiation cycles you'd run for an Amazon or Meta candidate.

Read next