Salesforce's Aug 6 WARN Names an SVP of Engineering. Pool: 1.

Most recruiters read the Salesforce layoff coverage this week and wrote down "133." That is the least useful number on the filing. The Washington WARN notice, filed Aug 6, 2026, does something the September 2025 round did not: it names an SVP of Software Engineering, product management directors, and incident commanders by title, on a 60-day clock that closes Oct 5.

What Salesforce actually filed on Aug 6-7 2026

Salesforce filed WARN notices for 133 total roles across two states, effective Oct 5, 2026, and the Washington filing is the first recent Salesforce WARN to explicitly name executive-level engineering titles. This is Salesforce's third layoff round of 2026, following an under-1,000-role February round and a June round that included a California WARN for 86 positions.

The breakdown:

• 59 roles at the Bellevue and Seattle offices (929 Office Tower in Bellevue, Data 1 building in Seattle Fremont).
• 74 roles at San Francisco HQ (Salesforce Tower).
• Named titles in the Washington filing: software engineers, technical support engineers, incident commanders, product management directors, an SVP of Software Engineering, and leadership in marketing and sustainability.
• Divisions reportedly affected: Tableau, Trailhead, community engagement, and events.
• Stated posture: "The worksites will not be closed in their entirety. The terminations are not the result of, nor will they result in, the relocation or contracting out of the company's operations or the affected positions."

Translation: this is a structural reallocation, not a site closure or an offshoring move. The people cut are not being replaced by contractors in another timezone. They are being replaced by a different bet.

The talent-swap nobody wrote the headline about

Salesforce is cutting a named SVP of Software Engineering the same week it announced hiring a new EVP of Engineering for Agentforce. That is not a hiring freeze; it is a talent swap, and it defines the entire sourcing opportunity.

The incoming executive is Krishna Kumar Parthasarathy, a nearly three-decade Microsoft cybersecurity veteran who will oversee engineering for Agentforce, Agentforce Voice, Digital Channels, and Service Cloud. He is part of a broader wave of senior Microsoft security leaders leaving this summer for AWS, ServiceNow, and Salesforce.

Here is the mechanism. Senior IC and leadership headcount is moving out of legacy Service Cloud, Tableau, and Trailhead, and into agent-platform work under Parthasarathy. Anyone cut from those legacy orgs has years of context on the exact systems the new EVP now owns. That makes them premium hires for the companies Salesforce is trying to out-agent: ServiceNow, HubSpot, Zendesk, and every AI agent startup with a customer-service wedge.

If you are recruiting for any of those, the Aug 6 filing is a pre-qualified list.

Why the SVP of Software Engineering is a "pool of 1"

The named SVP of Software Engineering in the Aug 6 WARN is, on the day it was filed, a pool of exactly one candidate, whose 60-day notice window opened Aug 6 and closes Oct 5. That is the sourcing story.

Executive engineering leaders at Salesforce's scale almost never enter the market this cleanly. They get retention packages, they get quiet re-orgs, they get gardening leaves that surface them into a crowded pool of "ex-FAANG VP looking for their next chapter" by the time you hear about it. A WARN filing collapses that timeline: the person is legally required to leave on a specific date, is still on Salesforce payroll until that date, and cannot publicly sign with a competitor during the window.

1

The product management director line is a similarly small pool. None of these people show up as "Open to Work" on LinkedIn, because the tag would be premature. They show up in the filing.

Why 133 is the wrong denominator

The correct denominator for sourcing is not 133; it is the ~2,200 ex-Salesforce US engineers already in circulation plus the net-new engineers this round adds. The headline number conflates marketing, sustainability, events, and community roles with the technical cohort you actually want.

In Refolk's index of professional profiles, roughly 2,200 US-based profiles show software engineer, senior, staff, or principal titles with Salesforce in their career history. The top post-Salesforce employers are:

• Google
• PayPal
• DocuSign
• Slack (still surfacing under Tiny Speck for some tenure)
• Keysight
• General Motors
• Western Governors University

Top regions are the SF Bay Area, Mountain View, and Seattle, which happen to be the three regions where the Aug 6 filing lands. If you are recruiting into any of those metros, the base rate is that most of the Aug cohort will re-land at 6 to 8 named companies, and the recruiters at those companies will start reaching out early in the notice window.

Which is the exact gap Refolk closes: you describe the person in plain English ("ex-Salesforce staff or principal engineer, Seattle or Bellevue, worked on Tableau or Service Cloud, still at Salesforce as of August 2026") and get a ranked shortlist without pivot-tabling a WARN PDF against LinkedIn tenure fields.

The comparable-figures table

Every field on the Aug 6 filing has a comparable field from the Sep 2025 filing or Salesforce's regional headcount. Reading them side by side is what turns "layoff news" into a sourcing plan.

The Sep 2025 filing shows ~61% of SF cuts were Technology and Product. If Aug 2026 SF holds that mix, the 74 SF roles include roughly 45 technical seats. Add the Washington technical seats implied by the titles list and you are looking at a meaningfully engineer-heavy filing, one of whom is an SVP.

The Tableau sub-pool nobody else will surface

Because the Aug 6 filing explicitly names Tableau as an affected division, it is one of the only recent public triggers for sourcing ex-Tableau data-viz engineers, who otherwise almost never move. This is the non-obvious win.

Tableau engineers in Seattle and Bellevue are one of the deepest data-visualization pools in the PNW, and their retention is notoriously sticky. They joined pre-acquisition, vested through the Salesforce deal, and have not had a clean public reason to test the market. A WARN filing is that reason.

Signals to filter on:

1. Salesforce tenure that predates the Tableau acquisition close.
2. Seattle or Bellevue as current location, not Mountain View.
3. Titles containing "data," "visualization," "analytics platform," or "server."
4. GitHub activity on any repo touching Tableau's core engine or extensions API.
5. Public conference talks between 2020 and 2025.

The pre-acquisition Tableau engineering cohort is a small pool nationally, and the Seattle/Bellevue slice is a fraction of it. Cross-referenced against "still at Salesforce as of Aug 2026," you are looking at a defined shortlist. Sixty of them just got a WARN notice.

The 60-day sourcing clock, explained

The WARN Act requires 60 calendar days of paid notice before separation at large employers, which means the Aug 6 filing creates a fixed, non-negotiable sourcing window from Aug 6 to Oct 5, 2026. That is when named executives are still on payroll, still cannot publicly sign a competitor's offer, and are maximally responsive to inbound.

The honest cadence:

• Days 1 to 7 (Aug 6 to Aug 13): Filing hits state databases. Most recruiters read press coverage; the WARN PDF has the titles.
• Days 8 to 21 (Aug 14 to Aug 27): The named SVP takes a handful of inbound calls from executive search. First-mover advantage lives here.
• Days 22 to 45 (Aug 28 to Sep 19): Individual contributors surface. Some update LinkedIn to "Open to Work"; most do not.
• Days 46 to 60 (Sep 20 to Oct 5): The pool floods. Everyone's inbox is full. Response rates drop hard.
• Day 61+ (Oct 6 onward): The cohort merges into the 2,200 already indexed. Advantage gone.

The WARN PDF has the titles. The press release has the number. Only one of them is a sourcing list.

The tactical implication: pull the actual WARN filings from the WA Employment Security Department and CA EDD sites, not from press coverage. Cross-reference the named titles against a current-employer filter. That is the exact workflow Refolk automates: ask in plain English for "current Salesforce staff engineers in Bellevue with Tableau experience," get a shortlist you can actually message this week.

The "same building" sourcing sweep

The Aug 2026 PNW WARN cluster is not just Salesforce, and treating it as one sweep is worth more than treating each filing individually. Google filed for 52 Washington positions, Zillow for 91, and Visa for 70 at the 929 Office Tower in downtown Bellevue, the same address on Salesforce's Washington WARN.

The incident commanders and technical support engineers Salesforce is cutting are, physically, in the same building as Visa's 70 cuts. They share coffee shops. They share a commute. They share a LinkedIn "People You May Know" graph. Sourcing one alumni pool without sweeping the others leaves signal on the table, especially for infrastructure, SRE, and payments-adjacent roles where the skill sets overlap.

FAQ

How do I get the actual Salesforce WARN filings instead of press coverage?

Pull them directly from the Washington Employment Security Department's WARN database and the California EDD WARN report. Both are public, both update weekly, and both publish the employer's own filing letter as a PDF. The Aug 6-7 2026 Salesforce filings include a titles column that most press coverage summarizes but does not reproduce. If you are sourcing seriously, always read the PDF, not the article about the PDF.

Is the SVP of Software Engineering identified by name in the Aug WARN?

The Washington WARN lists the title and headcount for that role but, per standard WARN format, does not print the executive's personal name in the public filing. Identifying the specific individual requires cross-referencing Salesforce's public engineering leadership as of Aug 2026 against the Seattle and Bellevue reporting lines, which is a short exercise for anyone with a LinkedIn Recruiter seat or an index like Refolk's. The point is that "SVP of Software Engineering, Bellevue reporting line, Salesforce, on notice through Oct 5" is a pool of exactly one person.

How is this different from the Sep 2025 Salesforce layoff round?

The Sep 2025 SF WARN broke cuts into "4 in Sales and Distribution, 97 in General Administration, and 161 in Technology and Product," per Salesforce Ben's reporting, plus 93 in Seattle/Bellevue and 30+ in Ireland. It was aggregated by category, not by individual title, so the ~161 tech/product roles were a statistical cohort rather than an addressable list. The Aug 2026 Washington filing is the first recent Salesforce WARN to name executive-level engineering titles explicitly, which is what makes the SVP a pool of 1 rather than 1-of-161.

Where do ex-Salesforce engineers usually re-land?

Based on Refolk's index of roughly 2,200 US-based ex-Salesforce engineers, the top post-Salesforce employers are Google, PayPal, DocuSign, Slack, Keysight, General Motors, and Western Governors University, concentrated in the SF Bay Area, Mountain View, and Seattle. If you are recruiting for an AI agent startup outside those seven companies, your window on the Aug 2026 cohort is short before the incumbent enterprise SaaS recruiters start reaching out.