If your Salesforce badge stopped working this fall, you already know the strange part. The company is still putting Agentforce on every stage, and you are at the kitchen table reading a separation packet.
This is for you: AEs, SEs, CSMs, solution architects, product managers, engineers, ops, enablement, and the Trailhead and community people. I will keep it practical: what the reporting says, what to do this week, and how to earn from what you are good at while you look. I will not invent a severance formula, a headcount, or a rate.
What happened in the latest Salesforce layoffs?
The most recent round was filed with state officials in early August 2026 and was scheduled to take effect October 5. KRON4 and the California Post reported 74 jobs at the San Francisco headquarters, and GeekWire reported 59 across Seattle and Bellevue, including Tableau. The Next Web put the combined total at 133.
By location, the California Post said the San Francisco cuts included 37 technology and product roles, 34 administrative roles, and three in sales and distribution. GeekWire listed software engineers, product management directors, incident commanders, technical support engineers, and marketing and sustainability leaders in Washington. SalesforceBen reported employees posting about cuts across events, community, Trailhead, Marketing Cloud, and Industries Cloud, and an anonymous source told them about half of the North America Tableau tech support team was allegedly affected. SalesforceBen also said final numbers had not been confirmed.
The counting is messy, and I would rather tell you that than pick a winner. GeekWire and The Next Web call this the third round of 2026. KRON4 calls it the fourth Bay Area round in under a year. SalesforceBen says fourth in one paragraph and third in another. Earlier this year, Business Insider reported a cut of fewer than 1,000 roles (dated to early February in one story and January in a later one), then a June round touching Agentforce, MuleSoft, and Marketing Cloud, with 86 positions in California.
On the why, the California Post said Salesforce did not identify teams or reasons for the August cuts, and The Next Web noted the filings do not mention AI. The AI framing comes from the top. In 2025, Marc Benioff said on a podcast that he had cut support "from 9,000 heads to about 5,000, because I need less heads," as CNBC reported. On the May 2026 earnings call, he said engineering headcount had stayed mostly flat because "we have been using AI to create more efficiency for our engineers," per Inc., as cited by Quartz.
So the honest one-liner: you were part of a restructuring at a company betting its future on AI agents. That holds whatever the final count turns out to be.
What should you do in the first week after a Salesforce layoff?
Do not start with applications. Start with paperwork, money, and a short list of questions, because decisions made on facts beat decisions made on adrenaline.
-
Save everything while you still can. Separation letter, benefits summary, any agreement, equity and RSU details, final pay information. Make sure your Trailhead profile, certifications, and badges sit under a login you control, not only your work email.
-
Read the packet before you read the forums. Business Insider reported in June that Salesforce's internal policy ties severance to level and tenure. I am not going to repeat a formula from a news story. Your packet is the only number that counts.
-
Put your HR questions in writing. Your last day of employment and of benefits. When final pay lands and what it includes. What happens to unvested stock and any ESPP balance. How long you have to review anything before signing. Who to contact once your access is gone. Email gives you a record.
-
Write a one-page runway. Cash, fixed monthly costs, and whatever the packet says is coming. Just enough to know how many calm weeks you have.
None of this is legal or financial advice. If your agreement is complicated, or you are unsure what you give up by signing, have a qualified professional read it. Using the full review window is normal.
For the broader version of this week, including unemployment and health coverage, I wrote a general first-week layoff guide.
How do you tell people you were laid off from Salesforce?
Say it plainly, in three circles: the people close to you, the people who can actually help, and then a short public post when you are ready. The Salesforce ecosystem is unusually connected, so one clear note travels further than you think.
That connectedness is a real advantage. You know former customers, implementation partners, ISV founders, user group leaders, and admins you helped in the community. Many of them run Salesforce orgs and need people who understand them.
Keep the note short. I was part of Salesforce's latest reduction. Here is what I did, in one concrete line. Here is the role I want next. Here is who you could introduce me to.
Skip the long open-to-work essay on day one. One honest sentence is enough, and you do not owe anyone the timeline.
How do you keep a focused job search after Salesforce?
Pick a narrow target, write down your bar, and give the search fixed hours instead of all of them. Recruiter messages for vaguely similar roles will pile up, and volume can feel like progress when it is not.
Translate your work into outcomes a hiring manager outside Salesforce can picture. AEs, the deal cycles you ran and how many stakeholders sat in them. SEs and solution architects, the implementations, the integrations, and the technical objections you resolved. CSMs, the renewals, the adoption work, and the at-risk accounts you turned. Engineers and product people, what you shipped, who used it, and what broke. Enablement and Trailhead people, what you built and whose work it changed.
Then protect the week: two focused blocks a day, real breaks, and something that is not the search.
What expert AI lab roles fit former Salesforce staff right now?
There is a lane many people miss: expert work for AI labs. Labs pay experienced operators by the hour for judgment in domains they know, and enterprise sales, CRM workflows, and B2B software are exactly where generic answers break. Think about what a model gets wrong that you would catch in seconds: a discovery call summary that misses the economic buyer, a Flow or Apex suggestion that would hit governor limits in a real org, a sharing model answer that sounds right and would expose records it should not. That instinct is the paid hour.
As of early October 2026, a pull of public AI-lab listings showed sales, ops, engineering, and design roles that map to Salesforce careers. None of those cards named Salesforce, and I will not pretend they did. They are looking for the judgment, not your last logo. The kinds of work showing up included:
-
B2B sales expert, and business and sales operations expert: judge deal cycles, stakeholder maps, and the ops mechanics behind pipeline.
-
Sales and revenue operations task author: write and score the kind of RevOps scenarios a model would mishandle.
-
Solutions engineer (including identity and IAM solutions), software engineering expert (backend, frontend, full stack, AI-native platform and integrations), and software engineer task author for AI training: judge architecture, integrations, and code a generalist would green-light.
-
Senior product designer UI/UX: judge flows, states, and the failure modes a pretty mock hides.
Customer success and marketing people will find fewer exact-title listings in that pull and should map to sales, ops, and business expert categories instead of waiting for a perfect title match.
One rule protects you. See the level, the hours, and the rate before you say yes. If any of the three stays hidden until after you have committed your evenings, walk away. Cap your hours before you start so bridge income supports the search instead of quietly replacing it. I wrote more on why open queues are the wrong default for experienced operators.
Where does Swooply fit for laid-off Salesforce people?
Swooply matches experienced operators with expert work for AI labs, and we built it for moments like this one. Free for experts. Paid by the hour. Remote. You see the level, the hours, and the rate before you say yes, and a person on our team reviews what you shipped.
I will not promise that a Salesforce background guarantees you work. Nobody honest can. What I can promise is clarity up front and a team that is on your side while you figure out what is next.
If you were cut this year, start with the packet, the questions, and the runway. Tell the people who can help. Keep the search narrow. Then, when you are ready, put the CRM and enterprise judgment you spent years building to work, by the hour.