Salesforce Cut 133. Only 5 Agentforce Engineers Exist by Title.

Salesforce filed WARN notices for 74 San Francisco and 59 Washington roles this month, effective October 5, 2026. The composition is what matters: software engineers, an SVP of software engineering, technical support engineers, incident commanders, and a product director, weighted toward engineering rather than back-office. Meanwhile the September 2026 Hacker News "Who is hiring" thread is stuffed with "Agent Builder" postings. If you source AI talent, you have about two weeks before this cohort gets absorbed.

What actually happened in Salesforce's third 2026 round

Salesforce cut 133 roles across California and Washington, effective October 5, 2026, and the mix is engineer-heavy rather than admin-heavy. This is the third round of layoffs Salesforce has run this year, and it follows a June cut that hit Agentforce, MuleSoft, and Marketing Cloud directly.

The public facts, from WARN filings and reporting:

• 133 total roles, 74 in San Francisco, 59 in Washington state.
• Separation date: October 5, 2026 for every affected employee.
• Washington titles named: software engineers, technical support engineers, an SVP of software engineering, a product director, a VP of sustainability.
• June 2026 preceded this: a WARN notice listed 86 roles hitting employees on Agentforce, MuleSoft, and Marketing Cloud, spread across sales, general administration, and technology and product.
• Follow-on cuts (per Salesforce Ben): Tableau, Trailhead, community advocacy, content, and events teams, predominantly remote employees.

Benioff's public rationale, delivered on The Logan Bartlett Show, was that Agentforce and adjacent AI tools had lifted engineering productivity by more than 30%, and that customer support had been cut from 9,000 heads to about 5,000. Read alongside the WARN filings, that framing does not fully hold: this round trims builders, not just call-center staff.

133

Why the WARN list is unusually rich for sourcers

Because the cut targets engineers on Salesforce's most-hyped AI products at the exact moment the market is paying a premium for people who have shipped agents in production. The mismatch between HN demand and titled supply is severe.

Look at the demand side first. The September 2026 HN "Who is hiring" thread includes postings like Catalyst·Wayfare AI's: "AI Engineer, Agent Builder. Hands-on builder delivering key projects within multi-agent orchestrations." Catalyst·Wayfare disclosed on the thread that their August posting drew 216 applications and produced roughly 10 offers, a 4.6% offer rate. That is a flooded inbound funnel where an outbound-sourced ex-Salesforce engineer with real Agentforce shipping history skips the line entirely.

Now the supply side, from Refolk's index of professional profiles:

The headline number is the ratio. There are roughly 6,706 Salesforce-stack engineers for every one person who has already relabeled themselves as an Agent Builder. If you are sourcing on title, you are fishing a pond of 59 people against every AI-native startup on HN.

The 5-profile problem, and how to solve it

Sourcing "Agentforce Engineer" as a title misses about 99% of the actual displaced cohort. In Refolk's index, only five US profiles combine Agentforce as a skill with an engineer, developer, or architect title. The right query is Salesforce alumni plus agent-orchestration signal, not a title match.

Here is the pattern that works:

1. Anchor on employer, not title. Current or former Salesforce, MuleSoft, or Tableau, with a tenure that overlaps 2024 to 2026 (when Agentforce shipped).
2. Layer skill signals loosely. Apex, LWC, MuleSoft flows, or Tableau extensions on the Salesforce side. LangChain, LangGraph, function calling, tool use, RAG, or "agent" mentions on the AI side. Either signal counts; both is a keeper.
3. Read GitHub and blog activity. Ex-Salesforce engineers who have been shipping side projects with OpenAI, Anthropic, or open-weights models are your top decile.
4. Do not filter on "AI." Salesforce engineers who worked on Agentforce internals often list "Salesforce Platform" or "Einstein" instead. Filtering on the word "AI" collapses the pool without improving quality.
5. Cross-reference the WARN worksites. SF, Bellevue, Seattle. Titles and worksites are public within days of filing.

This is the exact gap Refolk closes: describe the person in plain English ("US-based engineer who spent 2+ years at Salesforce on Agentforce, MuleSoft, or Einstein, with public LangChain or agent-framework work") and get a ranked shortlist back. No boolean gymnastics, no five-tab search stack.

The reshaping vs shrinkage framing changes the pitch

This is not a distressed layoff, and your outreach should not sound like a rescue. Salesforce revenue growth re-accelerated after six straight quarters below 10%, 133 roles is a sliver of a roughly 80,000-person company, and Tableau just renewed a 114,000-square-foot lease. This looks like a reshaping, not a shrinking.

Two consequences for how you write to these candidates.

First, the ladder is being rebuilt from the top. Salesforce hired longtime Microsoft cybersecurity executive Krishna Kumar Parthasarathy as EVP of engineering, while engineering chief Srini Tallapragada is departing. Even non-WARN'd Agentforce ICs are watching the reshuffle and are receptive to inbound. Do not restrict outreach to WARN names; the broader Agentforce team is in play.

Second, the "we can save you" pitch flops. Candidates on this list are not panicked. They will negotiate. Your message needs a why-upgrade story: bigger scope, faster shipping cycles, equity in an agent-native company, freedom from Salesforce's platform constraints. Not "sorry to hear about the news."

There are 6,706 Salesforce-stack engineers for every one person who already calls themselves an Agent Builder.

The sleeper pool: Trailhead, community, and events

The follow-on cuts to Tableau, Trailhead, community advocacy, content, and events are the sourcing gold in this round, because these are Salesforce-native people with deep customer relationships and platform fluency. AI-native startups struggle to source this profile anywhere else.

Where they fit:

• Developer Relations. Trailhead content authors have been teaching Salesforce developers for years. They can teach agent frameworks to the same audience next quarter.
• Forward Deployed Engineer. Community and events staff who ran World Tours know how to walk into a customer conference room and ship. That is the FDE archetype every agent-orchestration startup is hiring for.
• Customer-facing Agent Builder. People who bridged Salesforce product and customers understand enterprise workflows better than any pure-AI engineer. The gap between "the demo works" and "the agent survives contact with an insurance claims process" is closed by this cohort.

Salesforce Ben's reporting flagged that this cut hit remote employees hardest, which means the geographic constraint is looser than the WARN worksites suggest. You are sourcing a distributed pool.

Where the displaced cohort is landing

The employers already absorbing agent engineers, per Refolk's index, are a useful hunting list for competitive intel and referrals. Liberate leads with 5 current AI Agent Engineers, followed by Walmart Global Tech, Observe.AI, Hazel Health, Hexaware, Google, and NVIDIA.

If you are recruiting for an AI startup that is not on that list, two things follow:

• Every outreach you write is competing with Liberate's inbound flow. Move faster on WARN names than they will.
• Your ex-Salesforce hires already at Liberate, Observe.AI, or Hazel Health are your best referral source. Ask them who else on their old team is quietly looking.

The geographic concentration is convenient: the Bay Area, San Jose, and NYC each hold 3 of the current 59 titled agent-engineers, which overlaps 100% with Salesforce's WARN worksites. Your candidate pool and your competitors' recruiting pool sit in the same three metros.

A two-week operating plan for this cohort

Run this like a WARN campaign, not a broad sourcing effort. The October 5, 2026 separation date gives you a compressed window where displaced Agentforce, MuleSoft, and Tableau engineers are simultaneously on the market and not yet locked into their next role.

1. Day 1 to 3: build the list. Pull the 133 WARN titles as they publish. Layer in searches for the broader Salesforce-stack pool: Agentforce, MuleSoft, Tableau skills plus agent-orchestration signal. Target 400 to 600 names, not 40.
2. Day 4 to 7: first-touch outreach. Personalized notes referencing specific Agentforce work, MuleSoft integrations, or Tableau extensions. No "sorry to hear" openings. Lead with scope and equity.
3. Day 8 to 12: second-touch and referrals. For every WARN name who does not reply, ask a mutual connection at Liberate, Observe.AI, or Google for a warm intro.
4. Day 13 onward: convert. By October 5, competing offers start landing. Your interview loops need to be five days end-to-end, not five weeks.

FAQ

How do I get the WARN names before competitors do?

California and Washington publish WARN filings on state labor department sites within days of the filing. Set a weekly check on the California EDD WARN report and the Washington ESD WARN list, filter for Salesforce, and cross-reference the worksite address against the 74-SF and 59-Washington counts. Names of specific affected employees are not always public, but titles and worksites are, which is enough to pull the matching profiles from LinkedIn and GitHub in an hour.

Is "Agent Builder" a real title or an HN meme?

Both. It shows up as a formal job title at Catalyst·Wayfare AI and a growing list of AI-native startups, and it is dense enough on HN's September 2026 "Who is hiring" thread to constitute a distinct market segment. In Refolk's index only 59 US profiles currently use the title, which is why sourcing has to convert adjacent Salesforce-stack engineers rather than title-match.

Should I approach non-WARN'd Salesforce engineers too?

Yes. The leadership reshuffle (Tallapragada out, Parthasarathy in from Microsoft) has the broader Agentforce IC pool watching the ladder rebuild in real time. Receptivity to inbound is higher than baseline across the whole engineering org, not just among the 133 people on the WARN. Restricting outreach to WARN names leaves the majority of your convertible pool untouched.

What about the Trailhead and community layoffs, are they worth sourcing?

Very much so, for non-engineering roles. Trailhead content authors, community managers, and events staff are Salesforce-native people with customer relationships and platform fluency. They are the ideal DevRel, Forward Deployed Engineer, and customer-facing Agent Builder hires for AI-native startups, and almost nobody else is sourcing them into those roles yet.