ServiceNow Just Broke McDermott's Pledge. 63 Senior Now Engineers Are Free Aug 17.
ServiceNow's June 14 San Diego WARN released 63 senior Now-platform staff. Here is how to source them before the August 17 separation date.
On June 14, 2026, ServiceNow filed a WARN-style notice in San Diego eliminating 63 roles at its Eastgate Mall campus, with separations starting August 17. About half are directors, senior managers, staff engineers, and senior consultants. That is the smallest, most senior, hardest-to-replace pool of Now-platform talent that has hit the open U.S. market in years, and you have roughly nine weeks to move on it.
What the WARN actually says
The filing lists 63 jobs at the Eastgate Mall campus, separations beginning Aug. 17, with "additional job cuts elsewhere in California" hinted at but not enumerated. Hoodline's reporting on the notice flags that roughly half of the reductions land on directors, senior managers, staff engineers, and senior consultants. The cuts concentrate in middle-market sales, consulting, and senior engineering, the kind of roles that carry deep institutional knowledge of customer Now-platform builds.
That seniority skew matters more than the headcount. Sixty-three is small against ServiceNow's 2025 10-K headcount of roughly 29,187 full-time employees. But when the cuts are senior-weighted, you are not shopping for fungible ICs. You are shopping for people who know how a specific Fortune 500 bank wired its CMDB to its incident workflow, or how a federal customer's App Engine Studio scope is structured.
The pledge that broke
The recruiting angle here is not "saw you were impacted." It is the broken pledge. CEO Bill McDermott told Bloomberg in January 2023 that ServiceNow would have "absolutely no layoffs in 2023." The pledge predates that, too: ServiceNow publicly promised no layoffs in 2020 and was actively hiring through the pandemic. On the April 22, 2026 earnings call, McDermott softened the language to "exit the year into a new year with the same headcount," the standard attrition-plus-AI signal. Then April 14 happened (the entire Quality Engineering team was told to reassign or take the package), the June 11 triple-digit broader cut leaked through NowBen, and now the June 14 San Diego WARN.
For senior staff who joined or stayed at ServiceNow specifically because of that pledge, the trust break is the actual reason they will take your call. Lead with it. A line that names the pledge and the date converts materially better than generic outreach, because it signals you read the story rather than scraped the LinkedIn "open to work" badge.
Sixty-three is the visible tip. The April QE cut and the June 11 triple-digit reduction are the rest of the iceberg.
Why the recruitable pool is bigger than 63
The April 14 Quality Engineering elimination already pushed several hundred senior Now QE engineers into the market. The June 11 reporting from NowBen confirms a separate triple-digit broader cut, framed by ServiceNow as restructuring to "grow sustainably and win." Add the McDermott "same headcount" guidance, which implies aggressive attrition management through year-end, and the true addressable pool of senior Now-platform talent now sitting in the market or actively interviewing is materially larger than the WARN's 63.
The problem: most of that movement is invisible. WARN filings only catch site-level mass layoffs. The April QE reorg was structured as reassignment-or-package, which never hits a public notice. The June 11 cut was confirmed by a source, not an SEC filing. If your sourcing playbook starts and ends at "San Diego ServiceNow LinkedIn search," you will see 63 names and miss the other several hundred.
This is the friction we built Refolk to remove. You describe the person in plain English ("senior ServiceNow platform engineers who left ServiceNow between April and August 2026, with Flow Designer or App Engine Studio depth") and get a ranked shortlist that pulls from GitHub, LinkedIn, and the open web rather than a single source. The April reassignments and the June 11 quiet exits show up because their LinkedIn tenure ended, not because a journalist named them.
The skill stack that actually transfers
Here is where engineering leaders make the expensive mistake. "Senior platform engineer" sounds generalizable. For Now-platform people, it is not.
Pulled from active 2026 senior ServiceNow JDs, the real stack is: Business Rules, Script Includes, Client Scripts, ACLs, Data Policies, UI Actions, Flow Designer and Workflows, App Engine Studio with upgrade-safe development patterns, IntegrationHub, MID Server, and CAD certification. GlideScript on top. ATF (Automated Test Framework) for the QE side. UI Builder for the newer Workspace work.
Where it transfers brilliantly
- Other Now shops: Deloitte, Capgemini, Cognizant, Accenture, KPMG, EY, Unisys, NTT Data. These are the natural landing spots and your natural competition.
- ServiceNow customers with large Now footprints: big banks, healthcare systems, federal agencies, telcos. Their internal Now teams pay well and almost never see senior external talent become available.
- Boutique Now consultancies. Smaller, often hungrier, and willing to move fast on a senior hire before Deloitte's req closes.
Where it transfers poorly
- Salesforce platform roles. Different metadata model, different scripting, different deployment story. The mental model overlaps but the muscle memory does not.
- Workday or generic ERP customization. Same caveat, more so.
- Pure JavaScript backend roles. GlideScript is JavaScript-shaped but the runtime, scoping, and APIs are Now-specific. A staff ServiceNow engineer is not a drop-in Node.js hire, and pretending otherwise wastes everyone's first interview.
ServiceNow itself acknowledges the ecosystem gap. ServiceNow University and the RiseUp program exist specifically because demand for Now-skilled developers outruns supply. If you have a Now-shaped req open, the candidates released August 17 are the rarest input you will see this year.
San Diego is the wrong place to look
The cuts are in San Diego. The talent largely is not. Refolk's index shows the U.S. senior-ServiceNow population concentrated in Dallas-Fort Worth, the DC-Baltimore corridor, and Minneapolis. San Diego barely registers. Most affected staff at the Eastgate Mall campus were either remote-hired or will remote-relocate after separation. A recruiter limiting outreach to "San Diego ServiceNow" misses most of the addressable pool, including the high-value federal-cleared candidates clustered around the DMV.
The 789-vs-42 gap is the practical reality. The broader senior pool sits at about 789 U.S. profiles, concentrated at Deloitte, Capgemini, and Cognizant. Filter to true Senior+ with the full platform stack (Flow Designer, App Engine Studio, IntegrationHub, ACLs, upgrade-safe patterns) and you get roughly 42 people. The August 17 cohort adds materially to that 42, which is why nine weeks of disciplined outreach matters.
The nine-week playbook
Week 1 to 2: identify the cohort
Pull the visible 63 from WARN coverage (Hoodline, San Diego Union-Tribune, NowBen). Cross-reference against LinkedIn tenure changes at ServiceNow San Diego since April 1. Layer in the April QE exits and the June 11 cohort. KORE1, the staffing firm cited in the Hoodline reporting, is already seeing senior Now engineers and QE specialists in the market, which is a signal that the cohort is talking.
For Now-platform recruiting this is exactly the use case where Refolk's plain-English search beats Boolean. "Ex-ServiceNow staff engineers with ATF or GlideScript depth who left in 2026" is one query, not fifteen LinkedIn searches with OR strings.
Week 3 to 4: split the cohort by destination
Three buckets:
- Will go to a Big 5 SI. Deloitte, Capgemini, Cognizant, Accenture, KPMG. They have the open reqs and the certifications process. If your offer is not better than Deloitte's, do not waste a slot.
- Will go to a ServiceNow customer. Big bank, federal, healthcare. This is where you can win on equity, scope, or "stop being a consultant" pitches.
- Open to something genuinely different. Smaller, but real. Adjacent platforms (low-code, workflow, ITSM-shaped startups) that can credibly use Now expertise.
Week 5 to 7: outreach
Lead with the broken pledge. McDermott said "absolutely no layoffs" in 2020 and 2023. Name it. Then name the specific skill you want (Flow Designer, App Engine Studio, IntegrationHub, ATF). Generic "saw you were impacted" notes from generic recruiters lose to specific notes that read the story.
Week 8 to 9: close before August 17
Once separation hits, severance starts, and the Big 5 SIs accelerate their offers. The window where you have asymmetric attention from these candidates is now to mid-August. After that, you are competing against signed Deloitte offers and a tightening interview calendar.
What engineering leaders should actually ask for
If you run an engineering org with a Now footprint, do not write a generic "Senior Platform Engineer" JD. Write a "Senior ServiceNow Platform Engineer" JD that names the modules: Flow Designer, App Engine Studio, IntegrationHub, ACLs, upgrade-safe patterns, CAD certification, ideally CIS certifications. The 42-person Senior+ pool reads JDs carefully. A precise JD signals you know what you are buying.
If you do not have a Now footprint and you are tempted by the "senior engineer at a public company" surface signal, pass. The skill stack does not transfer to your stack. Hire from this cohort because you need Now, not because you need senior.
FAQ
How many ServiceNow employees are actually affected by the June cuts?
The visible count is 63 from the June 14 San Diego WARN notice, with separations starting August 17. The fuller picture includes the April 14 Quality Engineering team reorganization (several hundred engineers told to reassign or take a package) and a June 11 triple-digit broader cut confirmed by NowBen reporting. ServiceNow has not filed an SEC disclosure for a company-wide layoff, so the true total beyond the San Diego 63 is not publicly itemized.
Why does the seniority of the cuts change the recruiting approach?
When layoffs hit 63 ICs, you are sourcing fungible engineers and competing on comp. When roughly half the cuts are directors, senior managers, staff engineers, and senior consultants, you are sourcing institutional knowledge of specific customer Now builds. That kind of candidate is worth more to a ServiceNow customer or a Big 5 SI than to a generic platform role, and your pitch should reflect that.
Do ServiceNow platform skills transfer to Salesforce or Workday roles?
Poorly. GlideScript, Flow Designer, App Engine Studio, IntegrationHub, ACLs, and UI Builder are a closed ecosystem. They transfer well to other Now shops (Deloitte, Capgemini, Cognizant, Accenture) and to ServiceNow customers with large Now footprints, but the metadata models, scripting runtimes, and deployment stories on Salesforce and Workday are different enough that you should not treat a senior ServiceNow engineer as a generic platform hire.
What is the single best opener for outbound to this cohort?
Name the broken pledge. McDermott publicly committed to "absolutely no layoffs" in both 2020 and 2023, and on the April 22, 2026 earnings call shifted to "same headcount" language. A message that references that specific trust break, then names the candidate's specific Now module depth (Flow Designer, ATF, IntegrationHub), outperforms generic post-layoff outreach because it proves you read the story rather than scraped a list.