Salesforce's Oct 5 WARN: 37 SF Engineers, 59 in Bellevue, One SVP

Salesforce filed WARN notices in California and Washington covering 133 permanent cuts effective October 5, 2026. The headline is the number. The opportunity is the mix: 37 tech and product roles in San Francisco, 34 G&A, only 3 in sales, plus 59 in Bellevue and Seattle skewed toward Tableau engineers and one SVP of Software Engineering. If you source, this is a knock-every-door list, not a bulk campaign, and the window closes the moment the wire pickups do.

What the Oct 5 WARN actually says

Salesforce is cutting 133 people effective October 5, 2026, split 74 in San Francisco and 59 across Bellevue and Seattle, and the role mix is heavier on engineers than on back office. That last part matters because it directly contradicts the AI-replacement story Marc Benioff has been telling in public.

Here is the shape of the pool, pulled from the filings and the prior round for context:

The ratio inside the SF filing is the tell. Tech-to-sales sits at 12.3 to 1 this round versus roughly 40 to 1 in the September 2025 filing (161 T&P to 4 Sales). Engineering is still the biggest bucket, but the skew is easing, not intensifying. That is not what "AI is eating engineers" looks like on paper.

12.3:1

This is Salesforce's fourth round of Bay Area cuts in just under a year, following 86 jobs at Salesforce Tower in June. Salesforce is still San Francisco's biggest private employer, and shares are down about 27% this year in what the market is calling the SaaSpocalypse.

Why the AI story doesn't fit this filing

Benioff keeps framing Salesforce layoffs as AI-driven, but the Oct 5 WARN reads like managerial de-layering, not automation of routine work. If Agentforce were quietly clearing out humans, G&A would dominate the filing. Instead, tech and G&A are within one head of each other (37 versus 34), and software engineers, technical support engineers, an SVP of Software Engineering, a product director, and a VP of sustainability are on the Washington list.

The context that actually explains the shape:

• Benioff confirmed in September 2025 that support headcount went from roughly 9,000 to about 5,000 as Agentforce was deployed internally. That cut already happened. It is not what Oct 5 is.
• Miguel Milano, a former Oracle executive, was promoted to COO. Longtime engineering chief Srini Tallapragada left after 14 years.
• Salesforce has been poaching senior engineers away from Microsoft even while running a hiring freeze on engineers broadly.
• Adam Evans, the former EVP and GM of AI, departed earlier in 2026.
• Agentforce itself passed $1bn in annualised revenue in May, so this is not a product in retreat.

Read together, this is a company trimming layers and consolidating product lines under a new operator, then rebuilding the top of the engineering org with outside senior ICs. The Oct 5 WARN is the trim, not the automation. Candidates you contact will have heard the AI narrative from every recruiter that skimmed the press release. Naming the actual mechanism ("product consolidation under Milano, not Agentforce eating your job") is how you sound like you read the filing.

The SF pool is smaller than 37, and that changes your sequencing

The real number of separated SF engineers you can reach is closer to 28 to 32, once internal transfers, voluntary severance, and attrition absorb their usual 15 to 25 percent. Treat this as a named-list exercise, not a campaign.

Sourcing steps that fit a 30-person pool:

1. Pull the San Francisco headquarters tech and product headcount visible on LinkedIn as of last week. Filter to individual contributors and line managers, exclude anyone already showing an "open to work" banner (they are already saturated).
2. Cross-reference against the Bellevue and Seattle Salesforce footprint separately; those are different labor markets and different narratives.
3. Segment by product surface: Data Cloud, Agentforce, Sales Cloud platform, Tableau. Each has a different natural landing spot.
4. Sequence outreach in the two weeks before Oct 5, while candidates are still on payroll and past the "am I safe?" phase but not yet in triage.
5. Save the bulk sends for Oct 6 onward when everyone else piles in. You want your name in the inbox first.

Describing that shortlist in plain English ("SF-based Salesforce ICs on Data Cloud or Agentforce, 4 to 10 years, not currently signaling open to work") is the exact gap Refolk closes. You get a ranked list back across GitHub, LinkedIn, and the open web without paying the LinkedIn Recruiter tax on a filter you could have written as a sentence.

The Bellevue and Seattle 59 is a Tableau story

The 59 Washington cuts land at 929 108th Avenue NE in downtown Bellevue and 744 North 34th Street in Seattle's Fremont neighborhood, and the affected roles include Tableau positions plus an SVP of Software Engineering. This is targeted product-line pruning inside Tableau, not a site closure. Salesforce's Tableau unit just renewed a 114,000-square-foot Fremont lease, and candidates being cut know it.

That last detail is a specific emotional angle worth naming in outreach. "Your office isn't going away, your product line got trimmed" is a different conversation than "your building is closing." Recruiters who reach out with the generic condolence template will get filtered.

Where the Tableau cohort actually lands:

• In Refolk's index of professional profiles, there are 937 US Tableau software, data, and product people, and only 1 of the top-title sample is still at Tableau itself. Walmart, Meta, and Moody's already employ far more Tableau talent than the mothership.
• The competitive supply on Oct 6 is worse than it looks. Zillow filed 91 Washington separations effective the same day, and Google filed its own WA layoffs the same week, putting roughly 150 senior tech workers on the Seattle market at once.
• The differentiator is reaching Bellevue Tableau engineers before Oct 5, not after.

937

The SVP line item is the highest-value name in the filing

An SVP-level departure inside a WARN filing is unusual. Senior VPs are almost always severed quietly with a package that keeps them off the public list. Whoever this Salesforce SVP of Software Engineering is, they will bring a network with them when they land. The name is findable by cross-referencing "SVP, Software Engineering, Salesforce" on LinkedIn against Bellevue and Seattle location changes in September. It is worth the hour.

Who is actually hiring the Agentforce cohort

The Agentforce ecosystem outside Salesforce is now bigger than Salesforce's own Agentforce bench, and that is where the cut ICs will actually land. In Refolk's index there are 2,408 US professionals with Agentforce in their headline or experience, and while Salesforce is still the top employer (14 in the top-title sample), the long tail of SIs, ISVs, and enterprise customers running Agentforce internally is where the demand is.

That reshapes the pitch. If you are hiring Agentforce implementation talent, the Oct 5 cohort is not just a defensive hedge against your own attrition, it is the shortest path to hiring somebody who shipped the platform itself rather than integrated with it. Two or three names from the SF 37 are worth more than a month of inbound from an Agentforce certification bootcamp.

Sequencing the outreach before every other recruiter reads the headline

The whole play is compression: reach the ~30 SF engineers and the ~45 Washington Tableau and platform folks between now and Oct 5, before the wire pickups saturate their LinkedIn inboxes. After Oct 6, you are one of forty recruiters in the thread.

A workable cadence:

• Weeks before Oct 5. Named outreach only. Reference the specific product line, not "the recent news." Do not mention Agentforce unless you are actually hiring for it.
• The week of Oct 5. Silence. They are packing desks and hugging colleagues. Sending anything this week reads as vulture.
• Week after. Warm follow-up to the people who half-replied. First outreach to the internal-transfer refuseniks, the ones who were offered a role in another org and turned it down. Those are the highest-signal candidates in the whole pool.
• Weeks 2 to 4. Broaden to alumni-network intros. Adam Evans, Srini Tallapragada, and the older Salesforce AI diaspora are all warm-intro paths back into current ICs.

After Oct 6 you are one of forty recruiters in the thread. The whole play is the two weeks before.

What to prep candidates for

Candidates from this cohort will hit the market with a specific objection you need to preempt: their own employer just poached senior engineers from Microsoft while cutting them. That is a hard read on your own resume, and every good candidate in this pool will feel it.

Two prep points that actually help:

1. The cuts are role and layer specific, not talent specific. Milano is delayering. Being on the Oct 5 list is not a signal about performance, it is a signal about org shape.
2. The Microsoft poach is a top-of-org story. Salesforce is buying VPs and directors, not backfilling the exact IC layer being cut. Candidates should not read the poach as a comparison against themselves.

Get those two lines into the first call and you will convert. Skip them and you will lose candidates to whoever addressed the elephant.

FAQ

How many Salesforce engineers are actually reachable from the Oct 5 SF WARN?

The filing lists 37 tech and product roles at the San Francisco headquarters, but 15 to 25 percent typically get absorbed by internal transfers, voluntary severance, or attrition before hitting the open market. The realistic reachable SF engineering pool is 28 to 32 people, which is small enough to work as a named list rather than a campaign. Treat it that way and you will hit a much higher reply rate than the recruiters running bulk sequences off the press release.

Why does the WARN filing not mention AI when Benioff keeps talking about it?

WARN filings are legal notices, not narrative documents; they list roles and dates, not causes. The reason AI is not in the Oct 5 filing is that this round is not primarily automation. It is managerial de-layering under new COO Miguel Milano and product line consolidation, with the actual Agentforce-driven support cut (roughly 9,000 down to 5,000) already behind Salesforce. Benioff frames every reduction as AI-driven because that is the market story he is selling. The filing is the operational reality.

What makes the Bellevue and Seattle cut different from the SF cut?

The Washington 59 skew heavily to Tableau engineers and technical support engineers, plus an unusually public SVP of Software Engineering, at 929 108th Avenue NE in Bellevue and 744 North 34th Street in Fremont. The Fremont Tableau office just renewed a 114,000-square-foot lease, so this is targeted product-line pruning, not a site closure. Outreach should acknowledge that specifically; candidates know their building isn't closing and generic condolence templates will get filtered.

How do I compete with the Zillow and Google WA filings landing the same day?

Zillow's 91 Washington separations and Google's parallel WA layoffs put roughly 150 senior tech workers on the Seattle market on Oct 6. The way to compete is time, not volume: reach the Salesforce Tableau and platform engineers in the two weeks before Oct 5, while they are still on payroll but past the "am I safe" phase. First names in the inbox win. Everyone who waits for the effective date is fighting for attention against every other recruiter in the region.