Qualtrics Cut 117 in Seattle. The 3:1 Ratio Names Who's Next.
Qualtrics' 117 Seattle cuts are integration overlap from the $6.75B Press Ganey deal. Here is how to source the next wave before WARN.
Washington state posted a WARN filing showing Qualtrics is cutting 117 jobs tied to Qualtrics Tower at 1201 Second Ave. in Seattle. The role list - entry-through-principal software engineers, ML, security, network, testing, engineering managers, and PMs - is not a cost cut. It is the visible tip of a duplicate-role integration wave, exactly 93 days after Qualtrics closed its $6.75B Press Ganey Forsta acquisition on May 18, 2026. If you read the acquirer/acquired split correctly, you can queue outreach 60 to 90 days before the next names surface on any tracker.
Why the 117 is not what most sourcers think it is
The 117 Seattle cuts are Qualtrics-side generalist platform engineering being deleted because Press Ganey Forsta brought its own equivalent team into the merged org. Qualtrics' own filing named "duplicate roles created by the merger" as the reason, a category distinct from the roughly 24% of 2026 US job cuts attributed to AI.
The tell is in the role mix on the WARN:
- Software engineers, entry level through principal
- ML engineers
- Network and infosec engineers
- Testing engineers
- Engineering managers and directors
- Product and product marketing managers
That is a full-stack platform org, not a targeted team wind-down. When acquirers cut a full platform slice, they are keeping the acquired org's equivalent slice. Which means the standard sourcer instinct - chase the acquired company's laid-off staff in South Bend, Indiana - is wrong here. The people leaving are in Seattle and Provo, and they are Qualtrics employees.
The 3:1 ratio that inverts who gets cut
In Refolk's index, roughly 2,875 US professionals are tied to Qualtrics against 918 tied to Press Ganey, a ratio of about 3.1 to 1. Combined with the nature of the deal, that ratio is what tells you the axe falls on the acquirer's side.
Press Ganey Forsta is not a tech-stack acquisition. It is a vertical data buy: the company serves more than 41,000 healthcare facilities including a majority of US hospitals, and the value is in that proprietary healthcare experience dataset. Qualtrics paid $6.75B for access to a customer base and a domain workforce it cannot replicate. So when integration decisions get made, the domain-specific Press Ganey engineers stay (they know the healthcare data model), and Qualtrics' generalist survey-platform engineers become redundant.
This inverts the usual post-merger sourcing playbook. In a tech-stack acquisition (a codebase or an AI team buy), acquirers cut the acquired staff after a retention period. In a vertical data buy, acquirers cut their own generalists. If you are building a Boolean or a saved search off this event, aim at Seattle and Provo Qualtrics engineers, not South Bend Press Ganey staff.
The 93-day integration-cut clock
Qualtrics closed the Press Ganey Forsta deal on May 18, 2026. The first WARN notice hit on August 19, 2026. That is 93 days, and it is not a coincidence. For any large SaaS merger, deal close plus roughly 90 days is when duplicate-org reviews finish, org charts get published, and the first WARN drops.
Put this in your calendar as a repeatable trigger:
- Day 0: Deal closes. Log it. Pull both sides' headcount from LinkedIn and your own index.
- Day 30 to 60: Integration team announces reporting lines. Blind threads spike. Watch for VP-level departures.
- Day 75: Start warm outreach on the acquirer's generalist engineering ladder. You are two to three weeks ahead of WARN.
- Day 90 to 100: First WARN drops. Names start hitting Open-to-Work.
- Day 150 to 180: Second wave in secondary offices and international.
The window between day 75 and day 90 is the sourcer's edge. This is exactly what Refolk is built for: you describe the person in plain English ("senior backend engineer at Qualtrics, Seattle, 5+ years, worked on survey platform or XM Discover") and get a ranked shortlist back, without waiting for anyone to flip an Open-to-Work toggle.
The dataset
| Segment | Count | Source |
|---|---|---|
| US profiles tied to Qualtrics | ~2,875 | Refolk's index |
| US profiles tied to Press Ganey | ~918 | Refolk's index |
| Acquirer:acquired ratio | ~3.1:1 | Derived |
| Qualtrics Seattle 2023 headcount | ~900 | GeekWire |
| Aug 19 Seattle cut as % of 2023 base | ~13% | Derived (117/900) |
| Days from deal close to WARN | 93 | May 18 to Aug 19 |
| Days from notice to separation | 60 | Aug 19 to Oct 18 |
The 117 in Seattle is roughly 13% of the last disclosed Seattle headcount (about 900 as of 2023). Qualtrics has not published a Seattle number since, and the cuts on August 19 were global, so 117 is a floor for the region, not a total.
Why the debt overhang guarantees a second wave
A JPMorgan-led 11-bank syndicate is sitting on estimated paper losses exceeding $500M on the $5.3B debt package that funded the Press Ganey Forsta deal, including a $3.3B leveraged loan and $2B in junk bonds and private credit. This was the largest hung deal in leveraged finance in 2026. Combined with Silver Lake as PE owner and Jason Maynard newly installed as CEO in February 2026 (after Zig Serafin departed in October 2025), the synergy math is non-negotiable.
New CEO, PE owner, hung debt, and a 3:1 workforce ratio. There is a second WARN coming.
Translation for sourcers: 117 in Seattle is not the last filing. Expect a second wave in Provo and international offices in Q4 2026 or Q1 2027. Build your list now, not in December. The Qualtrics Provo pool alone is several times the Seattle pool, and Provo does not have the same absorption market that will soak up Seattle engineers within weeks.
The WARN blind spot: 50 is a floor, not a total
Washington's WARN Act triggers only when 50 or more workers at a single site are affected, so the 117 figure captures the Seattle campus and nothing else. Remote workers, sub-50 satellite offices, and international teams are invisible to any WARN database. If your sourcing pipeline depends on WARN alerts, you are missing most of the story.
Fill the gap with:
- Team Blind's Qualtrics forum (teamblind.com/company/Qualtrics): verified employees discussing severance packages, impacted teams, and manager names in real time.
- LinkedIn Open to Work + start-date filters: catches people who accepted severance but have not updated their headline.
- GitHub commit velocity drop-off: engineers who stop pushing to work orgs typically know something two to four weeks before HR does.
The Blind threads on Qualtrics from mid-August 2026 onward are especially rich because Seattle engineers are comparing severance numbers publicly. Names, teams, and manager reporting lines surface in the replies. Cross-reference those team names against LinkedIn to build a working list of people impacted below the WARN threshold.
The Seattle absorption market is saturated
Qualtrics engineers hitting the Seattle market in October 2026 face the worst local re-hire environment in a decade, which means outbound response rates will spike and relocation offers become viable again. Track the comparable recent cuts:
- Zillow: 500+ in early August 2026
- Meta: nearly 1,400 in Washington state earlier in 2026 (~20% of local workforce)
- Microsoft: 605
- Oracle: 491
- Amazon: 121 on August 31
- T-Mobile: 77 on August 26
- TikTok: 75 in Bellevue on August 19
That is more than 10,000 Seattle-area tech layoffs since last year, with roughly 8,900 from Amazon and Microsoft alone. Two practical consequences:
- Response rates to cold outbound jump. Engineers who ignored recruiters in 2023 answer in 48 hours in October 2026. Adjust your cadence: fewer touches, more specific first messages.
- Relocation offers become viable. Austin, NYC, Chicago, and remote-first Series B/C companies can compete for senior Qualtrics engineers in a way they could not 18 months ago. If you are sourcing for a non-Seattle role, this is your window.
The sourcing playbook, in order
Here is the sequence to run this week if Qualtrics is in your ICP:
- Segment the acquirer, not the acquired. Ignore Press Ganey South Bend. Build the list from Qualtrics Seattle and Provo generalist platform engineering.
- Filter by ladder. Principal and staff engineers named in the WARN role list have the highest offer velocity. Start there.
- Cross-reference GitHub. Qualtrics has a public org and several employees push to personal accounts. Look for a commit drop-off in the last 30 days as a soft signal.
- Watch Blind daily. Team-name mentions on the Qualtrics forum tell you which orgs got hit hardest below the WARN threshold.
- Queue Provo now. The second wave is likely there. Build the list before the filing, not after.
The 60-day window between the August 19 notice and the October 18 separation date is your outreach runway for the confirmed 117. After October 18, they are in the open market and every recruiter with a WARN alert is emailing them. Reach them in September, not November.
FAQ
How is an M&A integration layoff different from a cost cut for sourcing purposes?
A cost cut spreads across functions and geographies to hit a percentage target; the impacted list is unpredictable and often includes strong performers who happen to sit in expensive roles. An M&A integration layoff is surgical and predictable: it targets duplicate functions on one side of the merger, usually the larger acquirer in a vertical data buy or the smaller acquired org in a tech-stack buy. Read the deal thesis, then read the acquirer/acquired ratio, and you can name the impacted org before HR does.
Why target Qualtrics engineers instead of Press Ganey engineers?
Because Press Ganey Forsta was a vertical data acquisition (41,000 healthcare facilities, proprietary dataset), not a tech-stack acquisition. Qualtrics paid $6.75B for domain workforce and customer relationships it cannot replicate, so it keeps the Press Ganey healthcare-domain engineers and cuts its own generalist survey-platform engineers. The 3:1 workforce ratio and the WARN role list (entry-through-principal generalist SWE) both confirm this.
When should I expect the next Qualtrics WARN filing?
Likely Q4 2026 or Q1 2027, and more likely in Provo or an international office than Seattle. The drivers are the Silver Lake PE ownership, Jason Maynard's mandate as new CEO, and roughly $500M in paper losses on the acquisition financing syndicate. Synergy targets on a deal this hung do not get met with one 117-person filing.
What is the practical outreach window for the confirmed 117?
Sixty days, from the August 19 notice to the October 18 separation date. The sweet spot is early to mid September: severance terms are known, employees are actively looking, but the broader recruiter market has not fully pivoted to them yet. After October 18, response rates stay high but competition intensifies, especially because the Seattle absorption market is saturated with 10,000+ recent tech layoffs.
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.