ServiceNow's 287 WARN: Where a Now Platform Resume Actually Converts

If your badge stops working Monday, you are the second wave, not the first. ServiceNow's July 28, 2026 WARN filing cuts 287 roles across Santa Clara and San Diego effective September 28, and the 117-person August 17 cohort has had a four-month head start on every recruiter you plan to email. The people who land fast this week are the ones who stop applying to "SaaS engineer" postings and start rewriting for the eight employers who actually hire titled ServiceNow developers.

What the WARN notice actually says

ServiceNow filed a WARN Act notice on July 28, 2026 covering 287 layoffs effective September 28, 2026, split across two addresses: 2225 Lawson Lane in Santa Clara (154) and 4801 Eastgate Mall in San Diego (133). This is the second California filing of the year, bringing the 2026 total to 404 roles.

A few operational facts that change how you should sequence the next 30 days:

• California's WARN Act requires 60 days of written notice, so most of the 287 have been quietly resume-building since late July.
• Former staff report the cuts hit solution consulting, sales, product marketing, and learning and development, not just engineering.
• CEO Bill McDermott told investors ServiceNow will exit 2026 at the same headcount it started with, even after three acquisitions. Flat headcount means more waves are possible, and you are competing with quiet attrition, not a one-time cohort.
• ServiceNow stock is down over 24% year-to-date on fears AI tools will replace traditional software work. That matters when you negotiate severance equity.
• The April 2026 elimination of the QA function already seeded the platform-talent market with senior Now-trained engineers before the WARN filings landed.

The number that should reshape your resume

There are roughly 3,964 U.S. professionals holding titles like "ServiceNow Developer," "ServiceNow Administrator," or "ServiceNow Consultant" in Refolk's index. There are roughly 78,844 who list ServiceNow or GlideScript as a skill. That 20x gap is your entire ATS problem in one ratio.

Most Now Platform work in the U.S. is done by people titled "Senior Software Engineer," "IT Systems Analyst," or "Digital & Technology Services VP." When you apply to a generic "Senior Software Engineer" req at a non-ServiceNow shop titled "ServiceNow Developer," you are outnumbered roughly 20 to 1 by a shadow pool that has the same skill under a more filter-friendly title. The keyword filter reads your title as a specialist and shelves you.

The rewrite goes the opposite direction from what most outplacement coaches will tell you. You keep the ServiceNow skills stack (Flow Designer, GlideScript, ITSM, ITOM, IntegrationHub, Service Portal) in the skills block. You de-specialize the title line on the resume. That is the exact tailoring work Refolk does automatically: paste the job posting, and Refolk rewrites your own history so the title and summary match the target's vocabulary while the underlying skill evidence stays intact.

Where a Now Platform resume actually converts

Four lanes convert. Everything else is a lottery ticket. Ranked by translation friction:

1. Enterprise ServiceNow customer shops (Walmart, JPMorganChase, Boeing, MBTA, GovCIO). Zero title translation. "ServiceNow Developer" is already a row on their org chart.
2. Boutique implementation partners (GlideFast Consulting, Kellton, Techila Global Services, ScreenMeet). Direct-hire path, no title translation needed, hiring managers who read GlideScript samples the way normal people read English.
3. Big 4 and system integrators (Deloitte, KPMG, Slalom, TCS). Slower loops, but the ServiceNow practice is a named cost center that gets budget even in cut cycles.
4. Skill-adjacent platforms (Salesforce, Workday, Pega). Real jobs exist, but the pool is smaller and the language does not port cleanly. Apex is not GlideScript no matter how confidently a recruiter tells you it is.

All counts from Refolk's index. The Salesforce row is the one that should stop you. It is nine times smaller as a titled market than the ServiceNow pool you are leaving. Every "just learn Apex" recruiter tip is pointing you at a market with fewer seats and stiffer competition than the one you just got cut from.

The four resumes you actually need

You do not have one resume this month. You have four, because each lane reads a different first page.

1. The customer-shop resume (Walmart, JPMC, Boeing, MBTA, GovCIO)

Keep the title. "Senior ServiceNow Developer" belongs at the top. These employers filter for the exact string. Lead the bullets with module names their internal roadmap already funds: ITSM catalog items shipped, HRSD case-type build-outs, SecOps playbooks, CMDB reconciliation health. Numbers that matter here are ticket-volume reductions, MTTR deltas, and the count of business services onboarded to the CMDB. Do not lead with "SaaS engineering" language. These teams do not think of themselves as SaaS teams. They think of themselves as internal platform teams, and they want a platform engineer.

2. The partner-shop resume (GlideFast, Kellton, Techila, ScreenMeet, Slalom, Deloitte)

Optimize for billability signal. Partner shops staff against statements of work, so their filter is looking for certifications (CSA, CAD, CIS-ITSM, CIS-ITOM, CIS-HR), client-facing evidence, and rate justification. Restructure bullets around projects delivered, industries touched, and modules certified. If you were internal at ServiceNow, translate internal deliverables into client-shaped outcomes: "led ITOM Discovery deployment across 12,000 CIs" reads better to a partner than "owned Discovery product enablement." Refolk's tailoring pass will pull the certifications forward and rewrite verbs from "enabled" to "delivered" without you rewriting a line.

3. The Salesforce or Pega crossover resume

Bury the ServiceNow title. Elevate the platform primitives you built and let the reader map them: workflow orchestration, low-code app development, integration middleware, record-based data modeling, role-based access, custom UI on a metadata platform. Name Apex, Flow, and Lightning only if you have actually shipped them; recruiters at Salesforce will sniff out padding in the phone screen. For Pega, lean on case management and BPM vocabulary. This is the lane where a generic ServiceNow developer resume gets filtered out inside 40 seconds, so the rewrite is heavier than the other three combined.

4. The Armis and SecOps resume

The April 2026 Armis acquisition ($7.75 billion in cash) is a hidden hiring signal. ITOM engineers with Discovery and Service Mapping backgrounds have a real pivot into cyber asset attack surface management (CAASM) roles. Reframe CMDB experience as asset inventory, Discovery as unauthenticated asset detection, and Service Mapping as business-context enrichment. Same skills, different buyer, different budget: the buyer is a CISO, not an ITSM manager, and the comp band reflects that.

Solution consultants have the hardest pivot

Solution consulting is the toughest resume in this cohort because the artifact trail is thin. Engineers have GitHub, Update Sets, and Now Community answers. Solution consultants have demos, RFP responses, and Discovery documents that mostly belong to the customer.

Three moves work:

• Pre-sales at a competitor. Pega, Workday, Salesforce, and Freshworks all staff solution consultants who can walk a CIO through a platform demo. Your ServiceNow demo reps translate one-to-one. The resume needs to lead with deals influenced, ARR sourced, win rates, and technical validation counts, not module names.
• Customer Success Engineering at a ServiceNow customer. A JPMC or Walmart runs an internal ServiceNow practice with a Center of Excellence. That CoE hires former ServiceNow SCs at a premium because you already speak the vendor's language back to the vendor.
• Product marketing at an ITSM-adjacent vendor. Atlassian, Freshworks, BMC, and Ivanti all want writers who understand the buyer. The transition works because you have spent years listening to CIOs complain about ServiceNow, and that voice-of-customer signal is exactly what product marketing runs on.

The one move that does not work is applying to generic "Sales Engineer" postings at seed-stage startups. The comp will disappoint you and the platform depth will be wasted.

Sequencing the next 30 days

Speed beats polish because the August 17 cohort already has a four-month head start and Refolk's index shows the titled pool is small enough that recruiter attention is finite. A workable order:

1. Day 1 to 3: File for unemployment, confirm severance terms including any equity acceleration (relevant given the 24% YTD stock drop), and export your LinkedIn and resume to a permanent location.
2. Day 3 to 7: Draft the four resumes in parallel from one history rather than rewriting a single master four times.
3. Day 7 to 14: Apply into the enterprise customer lane first (Walmart, JPMC, Boeing, MBTA, GovCIO, KPMG). These are the fastest loops because the title matches and the internal ServiceNow team already knows they need bodies.
4. Day 14 to 21: Partner shops in parallel. GlideFast, Slalom, and TCS run continuous requisitions.
5. Day 21 to 30: Crossover and SecOps applications, plus outbound to the Knowledge 2026 alumni network. Knowledge (first week of May in Las Vegas) is where recruiter density for this stack is highest, and the alumni Slack channels from prior years are live.

Track everything on Layoffs.fyi and WARNTracker for follow-on waves. If ServiceNow files a third California WARN before December, the market gets crowded fast and the sequencing above needs to compress into two weeks.

FAQ

Should I stay in Now Platform work or pivot to a different platform entirely?

Stay in Now Platform work if you can. The titled pool is 3,964, and the top eight employers of it (Walmart, Slalom, TCS, Boeing, JPMorganChase, MBTA, GovCIO, KPMG) run continuous requisitions because their internal ServiceNow practices are cost centers that survive most budget cycles. Pivoting to Salesforce sounds intuitive but the titled market is roughly a ninth the size, and Apex versus GlideScript is a real learning curve that hiring managers will test on the phone screen. Pivot only if you already have shipped code on the target platform.

How do I handle the ATS problem if my title is "Senior ServiceNow Developer"?

Split your applications into two tracks. For ServiceNow customer shops and partner shops, keep the title verbatim; their filters look for it. For non-ServiceNow employers, de-specialize the title on the resume to something like "Senior Platform Engineer" or "Senior Software Engineer" and let the skills block carry the Now Platform detail. This is the exact rewrite Refolk does per posting, which is why running one resume through it for every application beats maintaining a master doc by hand.

Is severance negotiable given the stock is down 24% year-to-date?

The cash portion is usually formula-driven and not negotiable, but the equity acceleration and the departure date are. The 24% YTD stock decline means unvested RSUs are worth less than you counted on when you joined, so ask for either accelerated vesting of the next tranche or a cash equivalent based on grant-date value. Also negotiate the effective end date; a September 28 termination versus an October 15 termination can matter for a full vesting cliff. Get any changes in writing before you sign the separation agreement.

What if I'm a solution consultant, not an engineer?

Your pivot targets are pre-sales at Pega, Workday, Salesforce, or Freshworks, or Customer Success Engineering at a ServiceNow customer like JPMC or Walmart. Rewrite around deals influenced, ARR sourced, and technical win rates rather than module depth, because pre-sales hiring managers read comp-plan-shaped bullets faster than technical ones. Avoid seed-stage startup Sales Engineer roles; the comp band will not match what you were making at ServiceNow, and the platform depth you have is wasted on a five-customer product.