ServiceNow Layoffs 2026: Hiring Impact for Platform Talent

ServiceNow has not announced a traditional 2026 layoff, but CEO Bill McDermott confirmed on April 22 that the company will not backfill natural attrition through year end, banking on AI productivity to hold 2027 headcount flat. The quieter story for hiring managers is that the elimination of the QA function in April and the close of the $7.75 billion Armis acquisition are already seeding the platform-talent market with senior Now-trained engineers.

One memo and a stage at Knowledge 2026 in Las Vegas the first week of May. That is what the public surface of “ServiceNow layoffs 2026” actually looks like. Underneath, the attrition-plus-AI model is steadily moving QE engineers, ITSM platform admins on the system-integrator bench, Now App Engine developers, and Armis cyber-asset specialists toward the open market. The supply curve is real even when the headlines are mostly about share price.

Last updated: May 18, 2026

Mike Carter, KORE1. Most of my fifteen-plus years of placement work has run through enterprise IT and service-management buyers, including the system integrators who staff the bulk of Now-platform implementations. KORE1 earns a fee when you hire through our IT staffing services practice, so the framing below leans toward “this pool is real and a quiet supply curve beats a loud one for hiring teams paying attention.” Worth saying on the record before you keep reading.

What follows is built from McDermott’s April 22 earnings call and CNBC interview, ServiceNow’s Q1 2026 financial release and Knowledge 2026 keynote, the Armis acquisition close announcement on April 21, employee reporting on Blind and TheLayoff, salary aggregator data from Levels.fyi, Glassdoor, and ZipRecruiter, and what our enterprise IT and ITSM desks have been seeing across the bench at the large SI partners since the QE memo went out in mid-April. ServiceNow is the outlier in this 2026 layoff cycle. The company that built the AI productivity narrative is now living inside it.

What ServiceNow Has and Has Not Done in 2026

Start with the things that did happen. Quietly enough that most hiring managers missed them.

On the April 22 earnings call covering Q1 fiscal 2026, McDermott told investors and then repeated to CNBC that ServiceNow expects to start 2027 with the same headcount it started 2026 with, even after closing Armis. The mechanism is attrition. “As you have attrition in the company, you don’t have to backfill it,” McDermott said, citing internal AI tooling productivity gains as the reason. It was the kind of line the market parses as both a margin signal and a hiring posture. The stock dropped 18 percent the next day. The hiring-side translation: every quarter through 2026, a slice of ServiceNow’s roughly 27,000-person workforce will leave naturally, and most of those seats will go unfilled.

One week earlier, on April 14, an internal memo eliminated the dedicated QE (Quality Engineering) function. QE engineers were given the option to transition into Software Developer roles or take severance. Most managers and senior QE leads were not given the transition option at all. The change has been corroborated across employee posts on Blind and TheLayoff and is the single most concrete role-level cut at the company this year.

On April 21, ServiceNow closed its $7.75 billion acquisition of Armis, the Tel Aviv-based cyber-asset visibility and OT security platform. Roughly 950 Armis employees joined ServiceNow, with about $500 million in retention grants spread across the incoming team. That averages over half a million dollars per person, weighted toward engineering and the senior commercial leadership. Big number, narrow window. Retention packages of that size typically cliff at 18 to 24 months, which sets up an Armis-side talent flow that hits the open market beginning in late 2027.

Then Knowledge 2026 in Las Vegas the first week of May. The Autonomous Workforce platform expanded from a single L1 IT Service Desk AI Specialist (now GA) to a sprawling lineup of AI specialists for IT operations, AIOps, site reliability engineering, asset lifecycle, portfolio planning, CRM, HR, finance, legal, procurement, workplace services, supplier management, health and safety, and security operations. IT-side specialists launch in June. Security and risk specialists preview in June and reach GA in September. Read the labels carefully. Those are job categories.

Two reads on that table. First, the no-backfill posture is the layoff. Not a memo with a date, not a 1,600-person morning email like Atlassian’s March cut, just a quarterly leak of seats that close behind whoever walked out the door. The math at 27,000 employees and a typical software-company attrition rate of 12 to 15 percent annually is roughly 3,300 to 4,000 seats per year that will not be replaced. Spread across job families. Concentrated in functions where the Autonomous Workforce specialists are landing first.

Second, the QE elimination is the canary. It is the only function ServiceNow has explicitly removed in 2026, and it maps almost one to one to one of the Now Assist tooling categories already in production internally. The pattern is informative for predicting which job families come next.

The Attrition-Plus-AI Model Is a Different Shape of Displacement

Most of the 2026 layoff stories we have written about followed a familiar shape. Atlassian cut 1,600 in one morning. SAP ran a structured reorg with a public 8-K. Snowflake trimmed entire functions like technical writing in a single week. The talent flow into our pipeline followed within thirty days each time.

ServiceNow looks nothing like that. No SEC filing. No restructuring charge. No company-wide town hall. Quarter by quarter, the open-req page lists slightly fewer roles than the prior period. Internal tooling absorbs the work that would have gone to a backfill hire. The people who leave are roughly the same as the people who would have left in any year, but the company simply does not replace them.

For hiring managers thinking about the displaced talent flow, the implications are uneven. The pool is harder to time because there is no firing event to anchor on. The candidates are not “laid off ServiceNow engineer” in the way “laid off Stripe engineer” was a year ago. They are people who left voluntarily, sometimes with a quiet performance push behind it, sometimes with a comp arbitrage opportunity at a competitor, and sometimes because they could read the org chart and saw their function on the Knowledge 2026 specialist lineup.

The exception is QE. Those engineers were given an unambiguous transition-or-leave choice in April, and the ones who left are in market right now. We have placed three in the last six weeks against ITSM platform engineering reqs. Two of the three were senior with eight-plus years of Now-platform automation work behind them. Both started under what their last Levels.fyi screenshot suggested they were worth. Pricing on this slice has not yet adjusted to the supply.

Four ServiceNow Profiles Most Hiring Managers Are Underestimating

“Ex-ServiceNow” on a résumé is the same problem as “ex-Stripe” or “ex-Atlassian.” The org is large enough that the title means almost nothing on its own. The signal is in the function, the products touched, and the level of platform depth. Four specific profiles are worth a careful read right now.

1. Senior QE and Test Automation Engineers Forced Into the Open Market

The April 14 elimination caught a deep bench of automation engineers who built ServiceNow’s internal test infrastructure across the Yokohama, Zurich, and Tokyo product releases. Their day-to-day was Selenium and Cypress against the Now Platform UI, scripted ATF (Automated Test Framework) suites against business rules and flows, custom test data factories, and the integration testing that catches a regression before it hits a customer instance.

That work transfers everywhere ServiceNow is deployed at scale. Any Fortune-500 IT org that runs a multi-instance ServiceNow footprint with dev, test, and prod separation needs exactly this skill set on the customer side. So does every SI partner staffing migration projects. The reason most hiring managers underprice the profile: QA broadly is treated as junior-adjacent on the receiving side, and recruiters skim past test automation experience to look for “developer” titles. Read the work history sections. The line “owned ATF coverage for the catalog request workflow at instance scale” is worth a lot more than the title suggests.

2. ServiceNow Platform Admins From the System-Integrator Bench

This is the largest of the four pools and the one most buyers will miss because it does not show up on a public layoff tracker. Accenture, Deloitte, Cognizant, IBM Consulting, and a half-dozen mid-tier SI partners staff their ServiceNow practices through a rolling bench model. When the AI Control Tower and Now Assist absorbed a measurable share of Tier-1 ITSM project scope through Q1, the bench started growing. Practitioners with five to ten years of Now-platform admin experience, certified across ITSM, ITOM, and HRSD, sitting unbilled for longer than the partners’ utilization thresholds allow, and starting to take outside calls.

Most of these admins know the unsexy work that keeps a production ServiceNow instance from rotting. Update set management. Source-control discipline against scoped apps. The slow strangler-fig migration off custom tables when Workspaces and Common Service Data Model would have done the job natively. Permission and role audit hygiene. Catalog item rationalization. The kind of work the customer’s in-house team rarely has time for.

Screen for: which products they have actually deployed in production versus which products their certifications list. Ask them to walk through a specific Common Service Data Model implementation they led. If the answer leads with the dependency model they chose for CI relationships and why they avoided the off-the-shelf reference patterns, you have a senior. If the answer is “I configured the OOTB tables and ran discovery,” they are mid-level. Price accordingly.

3. App Engine and Flow Designer Developers

The Now-platform developers are the rarer profile and the one ServiceNow itself is still hiring against. Custom application builds, Flow Designer workflows, IntegrationHub spoke development, GlideScript and server-side business rules, UI Builder and Service Portal customization. The skill ceiling is high because the platform-development idiom does not transfer cleanly out of the Now ecosystem.

That is also why the supply side here is narrower. The developers in this pool are typically coming out of the SI bench rather than directly out of ServiceNow itself. ServiceNow’s internal engineering org continues to net hire for the people who build Now Assist, the AI Control Tower, and the agentic Action Fabric infrastructure. The developers leaving are mostly customer-side App Engine builders whose end-customer reduced contractor spend after a Now Assist rollout absorbed the form-and-flow work that justified two contractors a year ago.

One specific anchor for hiring teams: ask candidates how they handle the trade-off between a Flow Designer subflow and a scripted business rule for the same logic. The right answer involves observability, version control through update sets, and the maintenance cost a year out. The wrong answer is “Flow Designer is easier.”

4. Armis-Side Cyber-Asset Visibility and OT Security Engineers

The 950 Armis engineers who joined ServiceNow on April 21 are the most under-discussed slice of the 2026 talent flow because most observers are reading the $500 million retention pool as a hard lock. It is not. Retention packages of that size typically vest over 18 to 24 months. A portion of the Armis team has already started taking outside calls, especially the OT and medical-device security specialists whose work does not map neatly to ServiceNow’s enterprise IT focus. Critical-infrastructure customers running on Claroty, Nozomi, Dragos, or in-house OT stacks are starting to see ex-Armis résumés land in their inboxes.

This profile is genuinely scarce. Asset-visibility specialists who can handle the IT-OT convergence problem, work with HL7 and DICOM-bearing medical device environments, and write production exposure scoring against a CTEM-style continuous-testing program do not show up in the broader cybersecurity hiring pipeline. The base of candidates is small enough that one good hire often shifts the maturity of a buyer’s whole asset program. Screen on specific deployment scale, not Armis tenure. The senior engineers who joined Armis from CyberX before the Microsoft acquisition in 2020 are the ones with the deepest OT background.

ServiceNow Talent Comp in 2026

Comp on the ServiceNow ecosystem is wider than most other tech specialties because it spans two very different markets. People employed by ServiceNow itself are on the company’s IC ladder, which Levels.fyi pegs at $152K for IC1 and well over $600K for IC6. People building on ServiceNow at customer sites or through SI partners are on a separate market that anchors closer to mid-market enterprise dev rates.

Sources: Levels.fyi ServiceNow software engineer compensation data, ZipRecruiter active job postings for ServiceNow developer and admin roles in May 2026, Glassdoor compensation aggregations for the customer-side roles, and our own ITSM and platform engineering placement history at KORE1 since February. Two-aggregator variance was meaningful on the App Engine developer tier. Levels.fyi runs about 12 to 16 percent above ZipRecruiter on the customer-side ranges, almost entirely because the Levels data overweights ServiceNow internal grants that do not carry over to the receiving employer. Anchor the offer to base cash plus first-year RSU value at the buying company, not to whatever the candidate’s last total-comp screenshot shows.

A geographic note. ServiceNow’s San Diego, Santa Clara, and Kirkland offices are heaviest with the QE and platform-engineering profiles. The Hyderabad and Dublin offices skew toward App Engine development and customer-facing engineering. For US clients open to a remote-EU or remote-APAC hire, the dollar value is significant and the productivity gap is narrower than the comp gap suggests. Our salary benchmark assistant will run your specific role through a city-level band in about ten minutes.

Where ServiceNow-Skilled Talent Is Landing

Three buyer profiles are absorbing most of the displaced ServiceNow talent right now, and the order has shifted since February in a way worth flagging.

The largest absorber is mid-market enterprise IT teams running their first or second ServiceNow modernization wave. Companies between 1,500 and 8,000 employees that bought Now Platform two to four years ago for ITSM and are now expanding into ITOM, HRSD, or SecOps. They cannot win senior ServiceNow talent against an Accenture or Deloitte bench rate, but they win against the Big 4 SI partners when they offer FTE roles with real ownership instead of a project-by-project staff-aug engagement. That has been the pattern across most of our 2026 ITSM placements.

The second-largest is banks and large insurers building CIRT (cybersecurity incident response team) and TPRM (third-party risk management) capabilities on top of the Now Platform plus Armis stack. The combination of asset visibility, exposure scoring, and integrated SOAR workflow is what most regulated industries have wanted for five years and could not stitch together cleanly. The buyers are specific (Fortune 500 financial services, regional bank holding companies, the large life and P&C insurers) and the comp is firm to slightly above the table above for the right cyber-asset profile.

The third is the same SI partners who staffed the original Now Platform implementations. The bench is growing on the ITSM admin side, but the partners are actively rebuilding their AI-side practice and need senior ServiceNow developers who can speak Now Assist, AI Control Tower, and Action Fabric fluently. The arbitrage opportunity for a candidate: go to the SI side for an 18-month window to credential up on the AI-platform layer, then move to a customer-side senior role at a 25 to 35 percent comp lift.

How to Move Faster Than the Big SI Partners

The Big 4 system integrators have a structural advantage on this talent. They can offer the credential ladder, a known career path through ServiceNow’s certification program, and project rotation across multiple customer environments. What they cannot offer is ownership of a single production instance, a tight feedback loop with the business, and the autonomy senior platform engineers want by year seven of their career.

Build the role around what the SI partners cannot match. A title that says “ServiceNow Platform Lead” or “Service Management Architect” rather than “Senior Developer.” A scope that includes the full lifecycle from intake through retirement of platform features, not just the build phase. An explicit budget line for ongoing certification and training. The hires who matter most are not chasing maximum cash. They are chasing the ability to put their fingerprints on something that ships and stays shipped.

Pace is the second lever. The candidates moving fastest in this window have three to five active processes by week two. Our average time-to-hire across IT placements is 17 days. For ServiceNow-platform roles right now we have been closing tighter than that since mid-March. If your loop runs longer than three weeks, you will be competing for the people no one else wanted.

If you have an open req that maps to any of the four profiles above, talk to a recruiter on our IT staffing desk. We have been working this specific pool since the April QE memo and can usually surface a qualified candidate in under a week.

Common Questions Hiring Managers Are Asking

Did ServiceNow actually lay off employees in 2026?

ServiceNow has not announced a company-wide reduction in 2026. The April 14 elimination of the QE function affected several hundred engineers, who were given the option to transition into Developer roles or take severance. Aside from QE, the cuts are happening through attrition and a no-backfill posture confirmed by CEO Bill McDermott on the April 22 earnings call. The company plans to start 2027 with the same headcount it started 2026 with, even after absorbing roughly 950 Armis employees.

What does “no backfill” actually mean for the open ServiceNow talent market?

At an annual attrition rate of 12 to 15 percent on a 27,000-person workforce, the no-backfill policy means 3,300 to 4,000 seats per year will not be replaced. The departures are not concentrated in a single event the way Atlassian’s March cut was. They roll quarter by quarter across job families, with the highest concentration in roles that map to the Autonomous Workforce specialist lineup announced at Knowledge 2026.

How does the Armis acquisition affect the displaced ServiceNow talent pool?

The Armis close on April 21 added roughly 950 employees and a $500 million retention pool. Most of that talent is locked in for 18 to 24 months by the vesting schedule. The early defectors are coming from the OT and medical-device security specialists whose skill set does not map cleanly to ServiceNow’s enterprise IT focus. That cohort is the most under-tapped slice of the 2026 cyber-asset talent flow.

Are displaced QE engineers worth hiring as developers?

For ServiceNow-platform work, often yes. The senior QE engineers ServiceNow displaced in April spent years writing test automation against the Now Platform, which is closer to scripted ATF and GlideScript work than to generic Selenium. Several of them transfer directly into App Engine or Flow Designer roles after a four-to-eight-week ramp. The mid-level ICs are a different conversation and should be screened on raw scripting depth rather than ServiceNow tenure.

How does this fit with the broader 2026 tech layoff picture?

ServiceNow is one of the quietest stories in the cycle. Atlassian cut 1,600 in a single morning. SAP ran a structured reorg with a public 8-K. Snowflake eliminated entire functions inside a week. ServiceNow is doing none of that visibly, but the cumulative attrition through 2026 plus the QE elimination plus the Armis integration is producing a real talent flow on a slower clock. See the 2026 tech layoffs overview for the cross-company picture.

Where is the talent geographically concentrated right now?

Domestically, San Diego, Santa Clara, and Kirkland carry the QE and senior platform profiles. The SI-bench platform admins are spread across Atlanta, Charlotte, Dallas, and Chicago, mirroring the Big 4 partners’ delivery hubs. Internationally, Dublin and Hyderabad are the deepest pools for App Engine developers, both increasingly open to fully remote engagements with US buyers. For Armis-side cyber-asset and OT specialists, the concentration is Tel Aviv and Palo Alto, with a strong remote-friendly default.