Qualtrics' 117 Seattle Cuts Are a Floor. Provo Is 3.5x Bigger.

A second Washington WARN notice, filed September 2, 2026, put a number on something Qualtrics had refused to disclose: 117 roles at Qualtrics Tower, 1201 Second Avenue, Seattle, with separations starting October 18. That gives sourcers a five-week window and, more usefully, a public list of exactly which functions the acquirer just decided are duplicates. Read as a job-family map instead of a headline, both sides of the merger become addressable.

Why the 117 number is a floor, not a total

117 is the Seattle-only count that hit the public record because of a statute, not the size of the layoff. Qualtrics notified employees in Provo and international offices the same morning, August 19, and has disclosed nothing outside Washington state.

The mechanism is Washington's Mini-WARN Act, which took effect in July 2025 and requires 60 days' notice for any mass layoff of 50 or more employees at employers with 50+ state workers. It removed the single-site percentage threshold in the federal WARN law, which is why the Seattle number surfaced when equivalent Utah cuts did not. Washington is now the best US state for early sourcing signals on mid-size cuts. Utah has no equivalent transparency regime.

The 117 represents roughly 13% of the ~900 people Qualtrics disclosed employing in Seattle as of 2023. Extrapolating that percentage globally is a bad idea, but treating 117 as the ceiling is worse: it is the visible slice of a review CEO Jason Maynard described as going "function by function, team by team" across the entire post-acquisition organization.

117

The WARN filing is a duplicate-role map

Read the enumerated titles in the filing as a public list of which Press Ganey Forsta counterparts Qualtrics decided are redundant. That is a sourcing brief written by the acquirer, at the acquirer's expense.

The Seattle filing names:

• Software engineers from entry-level through principal
• SDET / testing roles
• Machine learning engineers
• Network and information security
• Engineering managers and directors
• Product managers
• Product marketing managers

Every one of those is a function that existed on both sides of the $6.75 billion Press Ganey Forsta deal, which closed May 18, 2026. Separations start exactly five months later. In a "function by function" integration, the retained role on the other side inherits the workload of the eliminated one within 60 to 90 days. That creates burnout-driven flight risk on the "winning" side of every duplicate pair, which is the second cohort most sourcers miss.

For competitor clients (Medallia, Sprinklr, Genesys, Verint on the XM/CX side; NRC Health and Kyruus Health on the healthcare-CX side), both cohorts are in play: displaced Qualtrics ICs now, and overloaded Press Ganey Forsta keepers on a 90-day lag. Press Ganey Forsta serves more than 41,000 healthcare facilities, including the majority of US hospitals, so the healthcare-vertical talent overlap is where duplicate cuts concentrate.

What Refolk's index says about the real pool

The addressable pool across both legacy orgs is materially larger than any WARN filing shows, and it is not centered in Seattle. Refolk's index of professional profiles puts the Utah presence at roughly 3.5x the Seattle presence.

The top current titles on those 912 Qualtrics engineer profiles are Software Engineer, Senior Software Engineer, Software Engineer II, Staff Software Engineer, and Staff Systems Engineer, which is the same ladder enumerated in the WARN filing. That is not a coincidence. It confirms the filing describes the modal engineer at Qualtrics, not a fringe cohort, so the reach across the 2,676 US Qualtrics profiles is high-fidelity.

The Press Ganey side is concentrated around South Bend, Indiana, where the legacy Press Ganey HQ sits. That is where post-acute duplicate consulting and healthcare-CX PM roles most likely live, and where the "keeper" side of many duplicate pairs will burn out first.

The Utah blind spot

If you are only monitoring WA filings, you are systematically undercounting the addressable pool by roughly 3.5x. Provo has no equivalent to Washington's Mini-WARN transparency, and international sites disclose nothing.

Refolk's index shows 7 Qualtrics-tagged professionals in the Salt Lake / Provo corridor for every 2 in Greater Seattle. Qualtrics was founded in Provo and the engineering center of gravity never fully moved. When Maynard's memo describes a global function-by-function review, the arithmetic implies the undisclosed Utah cut is likely larger in absolute terms than the 117 in Seattle, not smaller.

The practical implication for sourcing:

1. Do not wait for a consolidated figure. There will not be one.
2. Set outbound cadences on Utah profiles now, not on WARN triggers.
3. Weight recent Qualtrics tenure changes in the Salt Lake metro heavier than Seattle in your scoring.
4. Cross-reference against "Open to Work" signals with a 30-day lookback rather than 7, because Utah cohorts have not been publicly told what Seattle has.

Duplicate role does not mean underperformer

Post-merger duplicate cuts skew toward tenured mid-level ICs and first-line managers whose function existed on both sides, not stack-rank bottoms. That is a materially better candidate profile than a generic layoff cohort, and it should change your outreach.

In a performance-driven RIF, the eliminated cohort correlates with low ratings. In a duplicate-role reduction, the eliminated cohort correlates with the acquiring org already having someone in the same seat. Those are opposite signals. A Senior Software Engineer at Qualtrics who worked on survey-distribution infrastructure was not cut because their code was bad. They were cut because Press Ganey Forsta had a survey-distribution team too, and integration picked the other one.

Say that in the first message. "I saw the Sep 2 WARN. Duplicate-role reductions in a post-merger integration are not a performance signal, and your ladder position is exactly what my client is hiring for." That framing beats generic "sorry to hear about the layoff" outreach by a wide margin, because it names the mechanism and respects the candidate's read on their own situation.

The WARN filing is not a headcount. It is a public list of which functions the acquirer just decided are redundant.

Debt overhang predicts a second wave

The financing behind the Press Ganey Forsta deal creates structural pressure to keep trimming through 2027, so treat the September WARN as the opening move. The 117 is not the finale.

Bloomberg characterized the JPMorgan-led syndicate's $5.3 billion debt package as the largest "hung deal" in leveraged finance this year. The 11 banks involved faced estimated paper losses exceeding $500 million on a stack that included a $3.3 billion leveraged loan and $2 billion in junk bonds or private credit. Debt service on that structure does not care about integration timelines. It compounds monthly.

For sourcers, that means:

• The current wave targets duplicates that are obvious after 90 days of review.
• A second wave in Q1 or Q2 2027 will target duplicates that only surface after a full product-integration cycle (typically 9 to 12 months post-close).
• The "keeper" side of duplicate pairs cut in September becomes at-risk in wave two if the retained function underdelivers.

The right posture is a standing search, not a one-off pull. In Refolk the plain-English query can be saved and rerun monthly as new titles, tenure changes, and location moves land in the index. That is how you catch wave two without watching WARN portals every morning.

The Seattle context that changes conversion

Washington's labor market is slack enough that outbound to displaced Qualtrics engineers should convert faster than usual. State unemployment was 5.0% in July 2026, up from 4.6% a year earlier, and Seattle has absorbed more than 10,000 tech layoffs since last year.

Recent WA WARN filings worth cross-sourcing against:

• Amazon: 121 WA cuts disclosed August 31
• Zillow: 500+ Seattle cuts in early August
• T-Mobile: 77 on August 26
• TikTok Bellevue: 75 on August 19

Amazon and Microsoft alone account for more than 8,900 of the 10,000+ Seattle tech layoffs since last year. That saturates local competing employers, which means displaced Qualtrics engineers are more likely to consider relocation, remote roles outside the Pacific Northwest, or non-obvious verticals than they would have been in 2023. Cold outreach that leads with "Seattle-based only" leaves the majority of the pool on the table.

3.5x

A five-week playbook before October 18

There are roughly five weeks between the September 2 filing and the October 18 separation date to build relationships before the cohort saturates competitor pipelines. Here is the sequence that works for a duplicate-role reduction specifically:

1. Week 1: Pull both cohorts. Displaced Qualtrics ICs and managers in Seattle, Provo, and Salt Lake, plus the "keeper" cohort at Press Ganey Forsta with matching functional titles.
2. Week 2: First-touch the displaced cohort. Reference the WARN specifically. Name the duplicate-role mechanism. Do not say "sorry."
3. Week 3: Second-touch with a specific role. Duplicate-role candidates convert on specifics because they are pattern-matching against the seat they just lost.
4. Week 4: Begin outreach to the Press Ganey Forsta keeper cohort with a 60-day framing ("checking in as the integration workload settles").
5. Week 5 and beyond: Convert the standing search into a monthly rerun. Wave two is coming.

The candidates who move fastest in weeks one and two are staff and principal engineers with recent Qualtrics tenure and no visible LinkedIn activity, which is the exact profile a title-search on a job board will miss and a plain-English query in Refolk will surface.

FAQ

How do I identify which Press Ganey Forsta roles are duplicates of the Qualtrics cuts?

The WARN filing enumerates the Qualtrics side (SWE entry through principal, SDET, ML, network/infosec, EMs, directors, PMs, PMMs). The Press Ganey Forsta duplicate is whoever holds the same functional title on the legacy side, concentrated in South Bend, Indiana. Refolk's index shows 899 US profiles referencing Press Ganey, which is a workable universe for a functional cross-match.

Why should I care about Utah if the WARN only covers Seattle?

Because Refolk's index shows roughly 3.5x more Qualtrics presence in the Salt Lake / Provo corridor than in Greater Seattle, and Utah has no mini-WARN equivalent. The undisclosed Utah cuts likely exceed the 117 Seattle number, but no filing will surface them. Sourcers who only monitor WARN portals systematically undercount post-merger pools centered outside a handful of transparent states.

Is a duplicate-role layoff a red flag on a candidate?

No, and saying so in outreach is a differentiator. Duplicate-role reductions in a post-merger integration are structural, not performance-driven. The cohort skews toward tenured mid-level ICs and first-line managers whose function existed on both sides of the deal. That is a materially better candidate profile than a generic layoff cohort, and worth explicit framing in the first message.

When does the next wave hit?

Probably Q1 or Q2 2027, driven by the $5.3 billion debt overhang on the Press Ganey Forsta financing and by duplicates that only surface after a full 9 to 12 month product-integration cycle. Set a standing monthly search on the combined Qualtrics and Press Ganey Forsta pool rather than treating September 2 as a one-off event.