Boeing Defense Gets the Dec 9 List First. Its Jobs Are in St. Louis
Boeing sends WARN notices to Commercial Airplanes engineers Dec 9. How to find them by location and program before Boeing's defense units place them.
If you want to hire the Boeing Commercial Airplanes engineers getting 60-day WARN notices on December 9, Boeing's own defense units see their names before you do. Boeing Defense and Space and Boeing Global Services get the lists first, and their skill teams will try to place people internally. On paper that looks like a head start no outside recruiter can match. It isn't much of one: the defense jobs are mostly in St. Louis, and notified engineers lose access to Boeing's internal systems about a week after they get the notice.
What is Boeing doing on December 9?
Boeing will send 60-day WARN notices to targeted teams at Boeing Commercial Airplanes (BCA) on December 9, 2026, and the layoffs take effect February 12, 2027. It's a cut of roughly 5%, about 2,500 roles.
Here's what SPEEA (IFPTE Local 2001) and the press coverage confirm:
- Size: about 2,500 jobs, measured against the 50,500 people BCA employed at the end of 2025. Boeing expects attrition to cover some of them.
- Targeting: management is cutting specific teams, not across the board. SPEEA's own post describes the targets as "work statements" that are ending.
- No buyouts: SPEEA confirmed there are no buyouts or voluntary severance options.
- List-sharing: BDS and BGS will get the lists of separated BCA workers, and their skill teams will look for internal openings.
- Non-working RIF: notified employees get 60 days of pay but are told to stay home after about one week. SPEEA objected that this cuts off their access to Boeing's internal systems and makes it much harder to find another job inside the company.
- More rounds possible: SPEEA spokesman Bryan Corliss told Reuters the union asked whether December 9 was the only notice date. Boeing management said it didn't know.
The cause is production pace. In her November 9 memo, BCA CEO Stephanie Pope wrote that the slower production plan "puts us in an overstaffed position." Boeing is trying to go from 42 jets a month to 47, and CEO Kelly Ortberg now expects to hit that rate in early 2027.
How many engineers will actually get SPEEA layoff notices?
Nobody outside Boeing knows yet, and you shouldn't plan around 2,500. That figure covers all of BCA, not only the engineers SPEEA represents. The last comparable round suggests engineers will be a minority of the notices.
In November 2024, SPEEA was told that 438 of its members would be laid off, out of almost 2,200 Washington layoffs. That's about 20%. If 2026 looks similar, the engineering and technical pool is hundreds of people, not thousands. That's still a big pool for a hardware startup that needs six stress engineers.
| Figure | Source | What it tells you |
|---|---|---|
| ~2,500 | Boeing, ~5% of 50,500 BCA staff | Ceiling for all of BCA, not just engineers |
| 438 of ~2,200 | SPEEA, November 2024 round | About 20% of Washington notices went to SPEEA members |
| ~17,000 | SPEEA representation | Size of the represented base in Washington and nearby states |
| 4.9% (~830/year) | SPEEA annual attrition | Union says this can't absorb the cut in the short term |
The way the cut is designed matters more than the headcount. With no buyouts, nobody chose to leave. People are selected by team, not by who already wanted out, so the pool isn't weaker than average. A team-based cut takes the whole team, strong and weak together.
Why does searching "Boeing Commercial Airplanes" find almost nobody?
Engineers write "Boeing" on their profiles, not the name of their division. In Refolk's index, only 148 US profiles with "Engineer" in the title mention "Boeing Commercial Airplanes" in their headline. All 25 sampled list their employer simply as "Boeing."
Defense looks even worse. Only 6 US engineer profiles mention "Boeing Defense Space Security" in their headline. The division is an org-chart label that matters inside Boeing, not on a profile. A search that filters on division name covers only about 6% of a pool the size of the headline cut.
| Query (US, title contains "Engineer") | Count | Notes |
|---|---|---|
| Headline mentions "Boeing Commercial Airplanes" | 148 | Refolk's index |
| Headline mentions "Boeing Defense Space Security" | 6 | Refolk's index |
| BCA-to-BDS headline ratio | ~25:1 | Derived |
| BCA-headline sample in Washington state | 18 of 25 (72%) | Derived from top regions |
| Stress or Liaison Engineer, all employers | 1,167 (64% Boeing in sample) | Refolk's index |
| BCA-headline profiles as share of the ~2,500 cut | ~6% | Derived |
There's a second trap. Notified engineers stay on payroll until February 12, so expect most of their profiles to keep saying "Boeing, Present" through the notice period. I covered that lag in detail in WARN layoffs whose profiles still say Present. Don't wait for profile updates to tell you who's available.
How do you tell a BCA engineer from a BDS engineer?
Start with location, then check program words. In the BCA-tagged sample, 72% of profiles are in Washington state, while the wider stress and liaison population is concentrated in Greater St. Louis, the defense hub. A liaison engineer in Everett is very likely BCA. One in St. Louis is probably defense and probably not on the list.
Signals that point to BCA
- Location: Everett, Renton, Seattle, Auburn. Wichita too, where SPEEA has a separate unit.
- Programs: 737, 777X.
- Work words: liaison, MRB.
Signals to downweight
- 787: in February 2026, Boeing moved the "remaining 787 engineering work" from Puget Sound to North Charleston. A Puget Sound profile that says "787" now is weaker evidence of a current BCA seat than one that says 737 or 777X.
- St. Louis plus F-47, Phantom Works, or MQ-25: this is defense. These people are the internal competition for talent, not the pool.
Boolean on a LinkedIn seat can't weigh "Everett" against "787" or rank someone higher for MRB experience. Refolk lets you write the rule as a sentence: you describe the person in plain English and get back a ranked list, without writing a stack of OR clauses.
Why won't Boeing's defense arm absorb most of them?
Because the defense jobs are mostly in St. Louis, many need a clearance, and notified engineers lose internal access after about a week. Boeing Defense, Space and Security has its headquarters in St. Louis, with 18,000 local employees as of 2026. That's where the flagship work is: the F-47 next-generation fighter, Phantom Works, and the MQ-25.
So placing a Puget Sound liaison engineer in defense runs into three obstacles:
- Relocation. A move from Everett to Missouri.
- Clearance. Many defense roles need one. If you're hiring for cleared work yourself, check every claim against the clearance claim reference before you build an offer around it.
- Timing. Skill teams have to match people to openings while those people still have internal access, and that's about one week.
The index points the same way. In Refolk's index there are 1,167 US Stress Engineer or Liaison Engineer profiles. Boeing employs 16 of the 25 sampled, and Greater St. Louis is the top region (4), ahead of Greater Seattle (2). The defense side already draws these engineers from its own city.
That gives the outside recruiter a real advantage. A local or remote offer gets rid of the relocation problem BDS can't avoid. Blue Origin in Kent, Washington already shows up among the employers of stress and liaison engineers in the index. It's the kind of local option that competes directly with "move to St. Louis."
Boeing's defense arm gets the names first. You get the engineers who won't move to Missouri.
A notified BCA engineer won't compare your offer only against Boeing's internal seats. They'll compare it against every other open engineering role they can see.
How should you use the December 9 to February 12 window?
Build your map now, start outreach around December 16, and plan start dates after February 12. Under the non-working RIF, December 16 is roughly when notified engineers get sent home and lose access to internal systems. From then on, Boeing's internal job board is harder for them to use, while personal email and LinkedIn still work.
Here's how the timeline plays out:
- Now through December 8: build the map. Use location plus program words to list likely BCA engineers by team. The method in one layoff notice to a team-level slate works here: start from the teams whose work statements are ending, not from a company-wide name search.
- December 9: notices arrive. Hold off on a blast. For about a week, these engineers still have internal access, and many will likely look at BDS and BGS openings first.
- Around December 16: the real window opens. They're home, still paid, and cut off from internal tools. This is when an outside message gets read with real interest.
- December 16 through February 12: interview and offer. They're on payroll the whole time, so expect them to take interviews but not resign early. Boeing's skill teams can still come back with a late internal offer. Plan for it with a counteroffer risk read.
- After February 12: start dates. Write the offer around that date. Asking someone to give up paid notice is the easiest way to lose them.
The hard part for most teams isn't the strategy. It's the hours. A small defense-tech startup trying to hire laid off Boeing engineers often has no in-house recruiter. The founder or engineering lead ends up building a Puget Sound slate in the same weeks they're running interviews and shipping hardware, and by the time they get to outreach, the engineers they wanted may have taken another offer or an internal seat.
What should the first message to a BCA engineer say?
Mention their program, the location, and a start date that protects their notice pay. Don't mention the layoff list. You can't see it, and many of the profiles that match your signals belong to people who will keep their jobs.
- Lead with the work, not the company. "Your 777X liaison work" lands. "Your experience at Boeing" reads like a mail merge.
- Address relocation directly. If the role is in Puget Sound or remote, say so in the first line. That's the gap BDS can't close.
- Name the start date. "Starting after mid-February" tells them you understand the notice period without assuming they got one.
- Anchor pay to market, not to Boeing. Check current engineering salaries in the United States before you quote a range.
- Keep it short. Three sentences and one question. They're reading on personal email, not Boeing's systems.
If Boeing sends a second round of notices (management told SPEEA it doesn't know), run the same search again.
FAQ
When are the Boeing layoffs in December 2026?
SPEEA says Boeing will send 60-day WARN notices on December 9, 2026, with layoffs taking effect February 12, 2027. The cut is about 5% of Boeing Commercial Airplanes, roughly 2,500 roles against a 2025 year-end headcount of 50,500. Boeing hasn't said whether more notice dates will follow.
How many engineers will get Boeing WARN notices?
The exact number of engineers hasn't been published. The 2,500 figure covers all of BCA. In the November 2024 round, 438 of roughly 2,200 Washington layoffs went to SPEEA members, about 20%. A similar share this time would mean hundreds of engineers and technical staff, not thousands.
Will Boeing's defense division hire most of the laid-off engineers?
Probably not most of them. BDS and BGS get the lists and will try to place people, but BDS is headquartered in St. Louis, where its flagship programs like the F-47 and Phantom Works are based, and many roles need a clearance. Puget Sound engineers would have to relocate, and they lose internal system access about a week after they're notified.
How do I find BCA engineers when profiles just say "Boeing"?
Filter by Puget Sound location first (Everett, Renton, Seattle, Auburn), then by program and work words like 737, 777X, liaison, and MRB. Give less weight to 787 profiles in Washington, since that engineering work moved to North Charleston in February 2026, and leave out St. Louis profiles that mention F-47, Phantom Works, or MQ-25.
The data behind this
Try it on the search you came here for
Stop building boolean strings. Just describe the person.
Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.
01Describe them
One plain sentence. Role, city, stack, stage, whatever matters to you.
02I read the web live
GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.
03You read the shortlist
Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.
- Staff backend engineers in NYC who shipped Rust in production
- Series A fintechs in SF under 50 people, growing headcount this year
- Maintainers of fast-growing Rust web frameworks on GitHub
- No boolean, no filters, no seat to buy. One box.
- Read at search time, so a profile updated yesterday counts today.
- Every step visible as it runs, every name with its reason.
500 free credits on sign-up. No card, no demo call. See real searches.