ServiceNow Layoffs: Skip the 3,709 Partner Admins, Find the Engineers
ServiceNow layoffs November 2026: why searching "ServiceNow" returns partner admins, and how to find its engineers and the Moveworks, Veza and Armis teams.
If you hire platform engineers, your first move after a ServiceNow layoff headline is probably to search "ServiceNow" and start messaging people. That search mostly returns partner admins and consultants, and most of the engineers it does turn up were never laid off.
The headline itself is real. ServiceNow filed two more California WARN notices on Nov 3, its fourth pair since June, and two days later Calcalist reported a new round reaching the US, UK and India. This piece covers who was actually cut, why the keyword search fails, and where the engineers worth calling are.
What did ServiceNow file in November 2026?
ServiceNow filed two California WARN notices dated Nov 3, 2026: 37 workers at 2225 Lawson Lane in Santa Clara and 25 at 4801 Eastgate Mall in San Diego, with jobs ending in early January 2027. That brings California to eight notices and 486 workers since June 10.
Trackers don't agree on the exact end date: one lists Jan 3, 2027 and another lists Jan 4, so "early January" is the honest version.
Every filing so far has come in pairs, one for each of the same two addresses:
| WARN date | Santa Clara | San Diego |
|---|---|---|
| Jun 10, 2026 | 54 | 63 |
| Jul 28, 2026 | 154 | 133 |
| Oct 13, 2026 | 2 | 18 |
| Nov 3, 2026 | 37 | 25 |
| Total | 247 | 239 |
A note on counting. "Fourth" here means the fourth pair of WARN filings. Trade press, including NowBen, calls November the third round of the year. Both numbers are defensible. Just say which one you're using when you repeat it to a hiring manager.
The company hasn't given a global headcount. According to Calcalist, staff in the UK, US and India are affected, and the shares fell 35% between Oct 23 and Nov 5.
Why is ServiceNow cutting while it keeps buying companies?
ServiceNow bought three companies and committed to end the year at the headcount it started with. Every acquired employee means a legacy role has to go somewhere else.
The acquisitions came close together:
- Moveworks (enterprise search and virtual agents) closed Dec 15, 2025. Purchase consideration was $2.4B, according to the 10-Q.
- Veza (identity security, built around its Access Graph) closed Mar 2, 2026.
- Armis (Tel Aviv-based cyber-asset and OT security) closed Apr 20, 2026 for about $7.75B in cash.
In July the company said it aimed to "end 2026 where we started." The San Diego Union-Tribune, as reported secondhand, quoted ServiceNow saying the three deals added thousands of employees, so a matching number of positions elsewhere had to go. That's the whole mechanism: the layoffs are about absorbing headcount.
What sped things up was the Q3 guidance. ServiceNow guided Q4 constant-currency cRPO growth to 18.5% against the 19.8% the market expected, and the stock fell about 27% in one day, a record. On the call, CEO Bill McDermott described a smaller workforce as "a gorgeous situation."
The spending shows how big this is:
Even so, NowBen puts headcount at about 29K at the start of 2026 and about 30K now. The company is cutting and growing at once.
Who actually lost jobs, and who is worth calling?
Mostly go-to-market and customer staff lost their jobs. The engineers worth calling are mostly still employed at ServiceNow and the companies it bought.
NowBen reports the November cuts hit four groups:
- Customer Success Management (CSM)
- Marketing
- Media
- The Customer Excellence Group (CEG)
None of those is engineering, and that follows from why the cuts are happening. ServiceNow paid billions for Moveworks, Veza and Armis because of their products. Cutting the engineers who build and integrate them would undo the reason it bought them.
So if you came here hoping to hire former ServiceNow engineers off a layoff list, expect a short list. The better pool is passive: engineers who still have jobs and are unsettled. McDermott's reported plan is to let attrition happen without backfilling. When someone leaves a team and the seat stays empty, the people left take on that work for the same pay. That gives a recruiter a pitch, which comes later in this piece.
Don't use WARN as your measure of scope, either. All 486 workers are at two California addresses. The November round reached the UK and India, which have no comparable public filings. Severance spending at 3.2x last year's suggests the real total is several times what California shows.
Why does searching "ServiceNow" return so few engineers?
"ServiceNow" in a profile headline usually means someone works on the platform, not at the company. Searching the keyword gets you the partner ecosystem, which is mostly admins, developers and consultants at systems integrators.
In Refolk's index of professional profiles, 3,709 US profiles with "ServiceNow" in the headline hold ServiceNow Developer, Administrator, Consultant or Architect titles. Only 1,299 hold Software Engineer, Senior, Staff or Principal Software Engineer, or Platform Engineer titles.
The employers make the difference clearer. In a 25-profile sample of each group, the people with admin or consultant titles worked at Slalom, KPMG, Tata Consultancy Services, GovCIO, JPMorganChase and Boeing, and ServiceNow itself appeared once. In the engineer sample, ServiceNow appeared 18 times.
| Segment ("ServiceNow" in headline, US) | Profiles | ServiceNow as employer (sample) | Bay Area (sample) |
|---|---|---|---|
| Admin, Developer, Consultant, Architect titles | 3,709 | 1 of 25 (4%) | 1 of 25 |
| SWE, Staff, Principal, Platform Engineer titles | 1,299 | 18 of 25 (72%) | 10 of 25 (40%) |
The sample columns cover only the 25 profiles behind each query's top-employer and top-region breakdown. Treat them as directional, not representative.
In practice, a recruiter working a "ServiceNow" keyword list spends most of the afternoon opening profiles of KPMG implementation consultants and bank platform admins. None of them build the platform, and none of them were affected by the layoffs. The engineers are roughly one profile in four, scattered through the list.
Title and location filters remove that noise. The keyword doesn't.
How do you build a clean list of ServiceNow engineers?
Filter by engineering title first, then by location around the two WARN sites, then remove the partner firms. After that, search each acquired company by name, separately.
- Title before keyword. Require Software Engineer, Senior, Staff or Principal Software Engineer, or Platform Engineer. That alone takes you from 3,709 noisy profiles to 1,299 relevant ones.
- Location next. Ten of the 25 sampled engineers were in San Jose, Santa Clara or the wider Bay Area. Add San Diego, home to the other WARN site, which recorded 239 workers.
- Exclude the integrators. Remove current employers like Slalom, KPMG, Tata Consultancy Services and GovCIO. Their people are valuable, just not to this search.
- Search acquired companies one at a time. Refolk's index returned zero when a single query required "Moveworks," "Armis" and "Veza" together alongside engineering titles. That's almost certainly because no headline names all three, not because nobody is there. Run each name on its own.
Stacking those filters and exclusions in a boolean string is where most sourcing searches fall apart. That's the part Refolk takes off your hands: you describe the person in plain English and get back a ranked shortlist from GitHub, LinkedIn and the open web.
Moveworks, Veza, Armis: which acquired team is ready to move?
Moveworks and Veza, the two earlier closes, are the nearer-term calls. Armis engineers are held in place by roughly $500M in retention grants, so treat them as a longer play.
| Company | Focus | Closed | Retention signal |
|---|---|---|---|
| Moveworks | Enterprise search, virtual agents | Dec 15, 2025 | About 11 months inside ServiceNow |
| Veza | Identity, Access Graph | Mar 2, 2026 | About eight months inside ServiceNow |
| Armis | Cyber-asset and OT security | Apr 20, 2026 | ~$500M grants for ~950 people |
Moveworks and Veza are the first calls
Moveworks has been inside ServiceNow the longest of the three, and its roadmap now comes from a parent whose severance spending through Q3 ran at 3.2x the prior year's. If you're doing Moveworks engineers hiring, I'd lead with autonomy, not pay. Veza is the narrower pool: identity engineers who built around its Access Graph. Search "Veza" by name plus engineering titles, on its own query.
Armis is retention-locked, for now
Calcalist reported about 950 Armis employees joining with roughly $500M in retention grants, more than $500K per person, vesting over time. The schedule isn't public, so don't guess at cliff dates in your outreach. Ask instead. Cuts inside acquired companies have also started: Armis cut 45 people at Otorio, a company Armis had itself acquired. Build relationships with Armis engineers now and expect them to move later.
What should the first message say?
Lead with scope and pay, not the layoffs. Most of the engineers you're contacting still have jobs, and a message that treats them as victims will get ignored.
The useful facts are public, so use them:
- The no-backfill plan. If teams shrink through attrition and nobody gets replaced, the engineers who stay end up covering empty seats. Ask how many their team has lost this year.
- The stock. A 35% drop between Oct 23 and Nov 5 changes what unvested equity is worth. Engineers do that math themselves. Show your numbers and let them compare.
- The CEO's framing. McDermott called a smaller workforce "a gorgeous situation." You don't need to quote it back. Just offer a company where headcount isn't the goal.
Most ServiceNow engineers still have jobs. Pitch them more scope and fair pay, not sympathy.
The people who were actually laid off from CSM, Marketing, Media and CEG are a separate search with a separate message. They know the ServiceNow customer base, which is the pitch for customer success and solutions roles elsewhere. Keep the two pools and the two messages apart.
FAQ
How many people were affected by the ServiceNow layoffs in November 2026?
ServiceNow hasn't given a number. The Nov 3 California WARN notices cover 62 workers (37 in Santa Clara, 25 in San Diego), bringing California to 486 since June 10. Calcalist reported the round also reached the UK and India, where there are no comparable public filings. Severance costs of $167M through Q3, up from $53M a year earlier, suggest the true total is well above the WARN figure.
Did the ServiceNow layoffs hit engineers?
According to NowBen, the November cuts mainly hit CSM, Marketing, Media and the Customer Excellence Group. Engineering wasn't the target because the cuts offset headcount added by the Moveworks, Veza and Armis acquisitions, and ServiceNow bought those companies for their products. Engineers are a passive pool to approach, not a layoff list.
How do I hire former ServiceNow engineers without wading through consultants?
Don't use "ServiceNow" as your main filter. In Refolk's index there are 2.86 admin and consultant profiles for every engineer among US headlines containing the word. Filter for engineering titles first, focus on Santa Clara, San Jose and San Diego, exclude partner firms like Slalom and KPMG, and search Moveworks, Veza and Armis by name, one at a time.
Should I approach Armis engineers now?
Yes, but plan for a slow process. About 950 Armis employees joined with roughly $500M in vesting retention grants, which makes them expensive to move before those grants vest. Start the conversation now, ask about their vesting timeline rather than guessing it, and be ready to offer a start date that works around it.
The data behind this
Try it on the search you came here for
Stop building boolean strings. Just describe the person.
Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.
01Describe them
One plain sentence. Role, city, stack, stage, whatever matters to you.
02I read the web live
GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.
03You read the shortlist
Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.
- Staff backend engineers in NYC who shipped Rust in production
- Series A fintechs in SF under 50 people, growing headcount this year
- Maintainers of fast-growing Rust web frameworks on GitHub
- No boolean, no filters, no seat to buy. One box.
- Read at search time, so a profile updated yesterday counts today.
- Every step visible as it runs, every name with its reason.
500 free credits on sign-up. No card, no demo call. See real searches.