Salesforce Cut 86 on June 10. The MuleSoft Ring Has Until August 7.

A California WARN notice posted on June 10, 2026 listed 86 Salesforce eliminations across Agentforce, MuleSoft, and Marketing Cloud, with Washington state and international cuts on top. The tech press read it as another "AI is eating SaaS" beat. The WARN itself, and Business Insider's follow-up, say something more useful: the core Agentforce engineering team was not touched. What got cut is the connective tissue around it.

That distinction is the whole sourcing story. And the clock is short. Affected workers stay on payroll until August 7, which gives anyone reading this roughly seven weeks to move before the open market catches on.

What the WARN actually says

Strip out the headline framing and the filing reads like this. Eighty-six US positions, weighted toward California (mostly the Bay), spanning sales, G&A, and technology and product. The technical cohort sits inside three product areas: Agentforce-adjacent roles (not the core AI engineering team), MuleSoft integration, and Marketing Cloud. Severance is generous: 9 weeks for senior managers and below, 13 for directors and senior directors, plus 3 weeks per year of service, plus 4 weeks if the employee is 60 or older. Cap is 26 weeks, or 30 if 60+. COBRA runs six months to a year.

Compare that to Oracle's recent template (four weeks plus one per year of service, capped at 26) and Salesforce's package is materially better. These candidates are not desperate. They will not take the first call. They will, however, take the right call.

The other piece of context worth holding in your head: Salesforce sits above 80,000 employees. Benioff told the May earnings call that engineering staffing has held steady at roughly 15,000 for two years. This is the third major round in nine months, after a February 2026 cut of close to 1,000 and a September 2025 cut of 262 in San Francisco. Customer support has gone from 9,000 to 5,000 over the same period. The 86 is small in absolute terms. It is large in signal.

Why core Agentforce got spared

Follow the revenue. Agentforce crossed $1B in annualized revenue with 205% YoY growth. Combined Agentforce and Data 360 ARR is near $3.4B, up more than 200% YoY. Benioff also said Salesforce could spend close to $300M on Anthropic tokens in 2026, most of it tied to coding. You do not cut the people sitting on top of that P&L.

$3.4B

So who actually got cut? People in the orbit. Product managers who shipped Agentforce features but reported into an adjacent org. Solutions engineers and forward-deployed engineers who built customer-facing agent work. Marketing Cloud engineers whose products have been quietly rebranded as Agentforce 365 over the past year (Sales Cloud became Agentforce Sales, Service Cloud became Agentforce Service, Platform became Agentforce 365 Platform). And, most interestingly, MuleSoft integration engineers.

The Informatica overlap nobody is naming

Here is the part the layoff coverage skipped. Salesforce closed its Informatica acquisition in November 2025. Informatica and MuleSoft do overlapping work in enterprise data integration. When a company finishes a multi-billion-dollar acquisition and seven months later cuts integration headcount, that is consolidation, not skill obsolescence.

That matters for sourcing because it changes what these candidates are. They are not engineers whose stack got automated away. They are engineers whose org chart got reorganized. Their MuleSoft Anypoint Platform and DataWeave skills are still in demand. MuleSoft's own 2026 Connectivity Benchmark Report surveyed over 1,000 IT leaders and found disconnected data is the top barrier to delivering AI-powered customer experiences. The people who just got cut are the people who solve the top problem the people doing the hiring say they have.

The 86 are not engineers whose stack got automated. They are engineers whose org chart got reorganized.

The real shape of the pool

Run the cohort through a sourcing lens and you get four tiers, in roughly descending scarcity:

Tier 1: Agentforce-adjacent product and forward-deployed engineers

The smallest and most valuable group. These are people who shipped real agentic workflows against real enterprise data and customers. Hands-on agentic AI shipping experience is essentially unbuyable on the open market right now. They will not show up on LinkedIn with "Agentforce" in their title because the brand only consolidated in the last year. You have to find them by the work they did, not by the keyword they wear.

This is the cohort where natural-language search beats Boolean. Describing what someone built ("PM who shipped a customer-facing agent on top of Salesforce Data Cloud in the last 18 months") is how you actually pull them out. That is the shape of query Refolk was built for: you describe the person in plain English, and the system pulls a ranked shortlist across GitHub, LinkedIn, and the open web, including the public-facing artifacts (talks, Trailblazer profiles, MuleSoft Meetup writeups) that tell you what the candidate actually did.

Tier 2: Senior MuleSoft integration engineers

The biggest single bucket inside the 86, and the one with the most obvious comp arbitrage. Average US MuleSoft integration pay is $117,986 as of June 3, 2026, with most workers earning $91K to $146.5K. Salesforce comp sits well above that band. The implication: these candidates are reachable by mid-market offers that would never land a Bay Area senior IC otherwise.

Demand is structural. The pipeline of production-ready certified MuleSoft Salesforce developers has stayed constrained for years, which is why rates stay elevated. Boomi, Workato, Tray.io, and Celigo all need them. So do the SI practices at Slalom, Deloitte Digital, IBM iX, and shops like Ad Victoriam Solutions.

Tier 3: Marketing Cloud engineers, now rebranded as Agentforce-adjacent

Quietly the most underrated group. Because Salesforce repositioned the product line under the Agentforce brand over the past year, many "Marketing Cloud" engineers on the WARN have spent the last 12 months doing AI-adjacent work without the title showing it. Their LinkedIn says Marketing Cloud. Their last six pull requests say something very different.

Tier 4: Sales and G&A

Real people, real talent, mostly not your problem if you are sourcing for engineering. Skip.

The August 7 arbitrage window

Severance changes how this pool behaves over time. Right now, on June 10 plus a few weeks, candidates have 9 to 26 weeks of pay locked in plus six months of COBRA. They will be selective. They will take warm intros. They will not respond to a templated "saw your background" InMail.

By August 7, the payroll cliff hits. Severance starts burning down. Comp expectations reset. The pool also stops being yours alone, because the broader market will have noticed by then. Every Salesforce layoff round since September 2025 has followed the same pattern: a quiet WARN, a week of trade-press coverage, then a four-to-six-week lag before mid-market recruiters wake up.

Your window is the next three weeks. Move now, you get pick of the pool. Move in late July, you are competing with Boomi and Slalom for the same names.

Where to actually look

LinkedIn alone will not surface this cohort cleanly. Title drift from the Agentforce rebrand, the fact that core Agentforce was spared (so "Agentforce" in a title is a negative signal for "available"), and the MuleSoft community's habit of living in Trailblazer and Slack rather than LinkedIn all conspire against keyword search.

The high-signal surfaces:

• Salesforce Trailblazer Community profiles, especially badges earned in the last 24 months on Data Cloud, Agentforce, and Anypoint trails.
• MuleSoft Meetup organizer and speaker lists in the Bay Area and Seattle.
• GitHub activity on Anypoint connectors, DataWeave libraries, and Salesforce DX repos. Recent commits to org-affiliated repos are a strong tell that someone is on the WARN.
• Salesforce Ben and #Awesome-Admins Slack and Discord communities. Marketing Cloud user groups. The Pardot diaspora.
• Conference talks at Dreamforce, MuleSoft CONNECT, and Connections (Marketing Cloud's event) from the last two cycles.

This is the kind of multi-surface sweep that takes a senior sourcer a week to do manually. It is also the kind of sweep Refolk runs in a single prompt: ask for "ex-Salesforce MuleSoft engineers in the Bay Area with recent Trailblazer activity and GitHub commits to Anypoint or DataWeave repos," and the search runs across all of those surfaces at once.

The geography is unusually concentrated

Salesforce layoffs normally spread thin. This one does not. The WARN is California-heavy, with Washington and international on top. The technical cohort inside that is heavily SF and Seattle. If you normally fish nationally for MuleSoft talent (because the pool is otherwise scattered across enterprise IT shops in the Midwest and Northeast), this is the rare event where hyper-local outreach beats wide nets.

Refolk's own index shows the broader US MuleSoft-titled cohort is thin and dominated by enterprise IT at IBM and mid-market integration consultancies, mostly outside the major tech hubs. Eighty-six Salesforce-pedigree, Bay-clustered candidates is a disproportionate liquidity event in a normally illiquid market. Treat it accordingly.

What this is not

It is not an AI displacement story. Core Agentforce kept its seats. Engineering headcount has held at 15,000 for two years. The "SaaSpocalypse" framing analysts are reaching for is real at the macro level (Salesforce stock is down more than 30% YTD, worst on the Dow), but it is not what is moving these 86 people specifically. What is moving them is post-acquisition consolidation with Informatica and a quiet rebrand around a core product the company is protecting.

That makes the candidates more valuable, not less. They are integration and adjacent-product engineers at the exact moment integration and adjacent-product engineering became the bottleneck for everyone trying to ship AI features against enterprise data.

You have until August 7 before they stop picking up the phone on their own terms.

FAQ

How do I tell which of the 86 were on the spared core Agentforce team versus the adjacent layer?

Title alone will mislead you. The core Agentforce engineering team kept their jobs, so anyone you find who is genuinely on the market and lists "Agentforce" prominently is almost certainly adjacent (PM, solutions engineer, forward-deployed, or a recently rebranded Marketing Cloud or Platform engineer). Cross-reference recent Trailblazer Community activity, GitHub commits to org repos, and conference talks against the WARN dates. If someone went silent on org-affiliated repos around June 10 and has 9+ years of tenure, they are almost certainly in the pool.

Is MuleSoft still a future-proof skill if Salesforce is consolidating it with Informatica?

Yes, for the buyer side. The consolidation is about Salesforce's internal product redundancy, not the underlying market. MuleSoft's 2026 Connectivity Benchmark Report (over 1,000 IT leaders) named disconnected data as the top blocker to AI customer experiences. Boomi, Workato, Tray.io, Celigo, and every major SI are hiring this skill set. Comp data shows pipeline constraint, not surplus.

What is a reasonable first message to send these candidates?

Skip "saw your background." Lead with what they actually shipped. For a Tier 1 forward-deployed candidate, reference a specific Agentforce customer story or Dreamforce talk. For a Tier 2 MuleSoft IC, reference a specific Anypoint connector or DataWeave contribution. The severance package means they have leverage and time, so a generic ping gets ignored. A message that proves you read their work gets a reply.

When does this pool effectively close?

Practically, late July. Severance starts burning down at the August 7 payroll cliff, and the wider mid-market recruiting wave typically lags WARN filings by four to six weeks based on prior Salesforce rounds. The candidates with the strongest options (Tier 1 forward-deployed and senior MuleSoft) will be off the market first. Move in the next three weeks or compete on price later.