Salesforce Named an SVP on the Oct 5 WARN. The Agentforce Pool Is 24.

Salesforce filed WARN notices in California and Washington on Aug 6, 2026 confirming 133 more layoffs effective Oct 5. The list names software engineers, technical support engineers, a product director, and, unusually, an SVP of software engineering. If you are building an agent platform, you have 60 days to convert that filing into a shortlist before everyone else notices.

What the Aug 6 WARN filing actually says

Salesforce is cutting 133 roles effective Oct 5, 2026: 59 in Bellevue and Seattle, 74 at the San Francisco HQ. This is the third 2026 round after a sub-1,000 February cut and a June round that hit Agentforce, MuleSoft, and Marketing Cloud teams.

The composition matters more than the headcount:

• Software engineers (multiple)
• Technical support engineers
• An SVP of software engineering
• A product director
• A VP of sustainability

California's WARN statute allows only a physical-calamity or act-of-war exception to the 60-day notice requirement. Oct 5 is not a soft target. Salesforce cannot pull these back, which means the people named on that filing will be free to talk on a date you can put in your calendar right now.

133

Why an SVP on a WARN filing is the real story

WARN filings almost never name SVP-level engineers. State filings usually list ICs and line managers, because senior executives leave through negotiated exits that never touch a public form. An SVP of software engineering showing up on a California WARN is either a package-driven exit that could not be structured privately, or a signal of a structural reorg under the new engineering EVP. Either way, it is a rare, addressable senior hire with a hard availability date.

Read this alongside the top of the org chart:

• Srini Tallapragada, President and Chief Engineering and Customer Success Officer, stepped down Aug 6, 2026 after 14 years, moving to Special Advisor to the CEO through Aug 6, 2027.
• Krishna Kumar Parthasarathy, a 28-year Microsoft cybersecurity veteran, was announced Jul 30, 2026 as EVP of Engineering, owning Agentforce, Agentforce Voice, Digital Channels, and Service Cloud.
• Adam Evans, EVP/GM of AI and a key figure in Agentforce's inception, has departed.
• Madhav Thattai moved from COO of Agentforce to EVP/GM Agentforce.
• Iain Mulholland arrived from Google as CSO replacing Brad Arkin.

When the head of engineering leaves, a Microsoft cybersecurity EVP takes over an agent product he did not build, and an SVP shows up on a WARN filing, the direct reports underneath that SVP are the most valuable senior IC pool on the market. They are not confused about why they are leaving.

The Agentforce pool is 24 people, and 18 are already gone

In Refolk's index of professional profiles, only 24 US engineers publicly identify with "Salesforce Agentforce" in their title or headline. Six are still at Salesforce. The other 18 have already left, and they landed at Workday, Vonage Business, Paychex, Home Depot, Hughes, Ai-Media, Forsys, and Edelman Financial Engines.

That distribution tells you two things. First, dispersion has already begun, which means the "wait for LinkedIn Open to Work in November" strategy is a strategy of showing up last. Second, the enterprises absorbing this talent are not the AI-native names on your competitive-intel deck. If you are pitching an agent platform against ServiceNow or Microsoft, your reference calls should go to a Paychex or a Home Depot tech org, not to another AI Series B.

24

Every one of the 74 SF-based Oct 5 cuts is potentially a 4 to 5 percent expansion of the entire identifiable Agentforce engineer pool. The named 133 is roughly 5.5x the currently-visible external population. Even a partial capture materially reshapes the external talent market for agent-platform builders.

The full dataset

Here is the sourcing spine, pulled from Refolk's index and the WARN filings themselves.

The 1,074 number is the outer ring for outbound, useful for adjacent Service Cloud, MuleSoft, and platform engineers who never got the Agentforce keyword on their profile but ran integration work against it. The 24 is the inner ring you draft messaging for by name.

The "core Agentforce spared" carve-out is a feature, not a caveat

June reporting said core Agentforce teams were spared in the earlier round. The Oct 5 filing names software engineers and an SVP of software engineering anyway. What that means: what is leaving is Agentforce-adjacent, not Agentforce-core. Service Cloud engineers, Digital Channels engineers, technical support tooling, integration surfaces.

That is exactly what buyers of Agentforce actually integrate against in production. Rivals building agent platforms need integration engineers more than they need model researchers, and the Oct 5 pool skews toward the people who spent the last year making an agent product work inside a real enterprise ticket queue.

Model researchers are a hiring luxury. Integration engineers with $1B ARR scars are a hiring emergency.

Frame outreach accordingly. The most defensible line is not "come build cool AI." It is "we need someone who has shipped an agent that answers a real customer's real ticket in production, at scale, without breaking Service Cloud."

Benioff's "zero engineer hires" claim is a résumé line

Marc Benioff has publicly stated Salesforce did not hire a single new engineer in FY2026 while claiming roughly 90 percent of code on internal teams is AI-written. Whatever you think of the number, the operational implication is real: the engineers being cut spent a year shipping into an AI-heavy codebase at $1B+ ARR scale on Agentforce, which passed $1B in annualized revenue in May 2026.

That is a résumé line no startup can currently match internally. It is worth naming explicitly in outreach:

• "You shipped in a codebase where ~90% of code was AI-generated. We want to hear how that actually worked."
• "You supported Agentforce customers past $1B ARR. What broke first?"
• "You were adjacent to the June and October cuts. What did the reorg tell you about where agent products go wrong?"

None of that reads as sympathy outreach. It reads as a peer inviting a peer to a real conversation.

The 60-day WARN clock, mapped to sourcing actions

The clock is not "Aug 6 to Oct 5 and then start recruiting." It is a set of overlapping windows, each with a different play. Here is how to sequence them.

1. Aug 6 to late August: identification. Build the named list. Cross-reference the 24 Agentforce-tagged profiles and the 1,074-person senior Salesforce pool against Bellevue, Seattle, and San Francisco office affiliations. This is where a plain-English query beats a boolean string, which is the exact gap Refolk closes: you describe the person and get the ranked shortlist back, without maintaining a 200-character boolean.
2. Early September: severance signing. Most California severance and release-of-claims deadlines run in days. Many of the named workers will have signed paperwork before Labor Day and will be free to talk immediately, even though their last day is Oct 5.
3. Mid-September: first outreach. Reference the reorg (Tallapragada out, Parthasarathy in, Evans out) by name. This signals you read past the headline.
4. Oct 5 to Oct 20: closing. Competing offers will land the week the Oct 5 cohort officially exits. Have your loop calibrated before then.
5. Nov 1 onward: the dispersal window closes. By November, LinkedIn Open to Work flags flip on and the pool becomes visible to every recruiter running a saved search. Your 60-day head start ends there.

Geographic split: don't lump SF and Seattle together

The two WARN offices attract different competing buyers, and outreach should reflect that. In Bellevue and Seattle (59 cuts), the natural competing buyers are AWS agent teams, Microsoft Copilot and Azure AI, and ServiceNow. In San Francisco (74 cuts), the competing buyers are every agent startup plus the applied teams at the frontier labs.

The Puget Sound cohort is more likely to want a large-employer landing spot with equity refresh predictability. The SF cohort is more likely to entertain a Series A pitch. Same résumé, different close. Refolk's index shows Bothell, WA and the Bay Area as the two dominant regions inside the 24-person Agentforce pool, which matches the WARN geography almost exactly.

What to do this week

Three concrete moves before Aug 20:

• Pull the named list. Not "ex-Salesforce engineers." The specific 24 Agentforce-tagged profiles plus the SF and Seattle subset of the 1,074 senior Salesforce pool.
• Draft one outreach per named exec context. One version referencing the Tallapragada departure, one referencing the Parthasarathy arrival, one referencing the Adam Evans exit. The right context depends on which team the recipient sat on.
• Book the loops now. If your interview loop takes two weeks to schedule, you cannot close an Oct 5 candidate against a competing offer that lands Oct 7. Compress the loop before you send the first message.

The Oct 5 window is unusually clean. A named SVP, a named product area, a hard state-filed date, and a 24-person visible pool that the incoming cohort could grow by 5x. Windows this specific do not repeat often.

FAQ

How many ex-Salesforce Agentforce engineers are actually identifiable in the US?

Refolk's index shows 24 US engineers who publicly identify with Salesforce Agentforce in their title or headline. Six are still at Salesforce and 18 have already left, currently at Workday, Vonage Business, Paychex, Home Depot, Hughes, Ai-Media, Forsys, and Edelman Financial Engines. The Oct 5 WARN cohort of 133 could expand this identifiable pool by more than 5x if even a fraction get tagged post-departure.

Can Salesforce rescind the Oct 5 layoffs before the effective date?

Effectively no. California's WARN statute allows only a physical-calamity or act-of-war exception to the 60-day advance notice requirement, so the Oct 5 effective date is a firm floor rather than a moving target. Severance and release-of-claims paperwork typically closes within days of the WARN filing, which means many of the named workers will be legally free to talk well before their official last day.

Who should I target first, the SVP or the ICs?

Target the SVP's direct reports first. An SVP of software engineering appearing on a state WARN filing is unusual and worth a personal outreach in its own right, but the highest-leverage hires are the senior ICs and line managers who reported into that org, because they are more numerous, closer to the code, and less likely to be locked into a long non-compete or advisor arrangement. Use the SVP's public org chart to map downstream.

What outreach framing actually works on this cohort?

Skip sympathy language and lead with operational specifics: the Agentforce $1B ARR milestone in May 2026, Benioff's public claim that ~90% of internal code is AI-written, and the reorg under new EVP Krishna Kumar Parthasarathy. These engineers know exactly what happened and why. Referencing named executives and dated product context signals that you are hiring for the actual work they did, not for a generic "ex-Salesforce" line on your careers page.