A 287-person cut takes effect on September 28

ServiceNow separates 287 people in California on September 28, 2026. The company filed the notice with state authorities on July 28, and the effective date is the one to hold on to, because the reporting by Lily Wright for the Los Angeles Times is dated August 1. The separations are permanent rather than temporary, and they split into 154 roles at the Santa Clara headquarters and 133 in San Diego.

Four California filings this year cover 404 roles in total. The two earlier ones accounted for 63 and 54 people with an effective date of August 17, which makes the cut landing now the largest ServiceNow has notified in the state during 2026.

One caveat on those figures. The state labour register could not be reached directly, so the numbers here rest on trackers citing federal notice data alongside the newspaper report rather than on the register itself.

The statement says headcount ends 2026 where it started

ServiceNow gave a statement about the reduction that is more direct than most vendors offer on this subject. It reads: "ServiceNow is committed to having the right talent in the right roles, and that means making necessary changes to how we are structured. We are driving efficiencies across the business, actively investing in and hiring for AI-focused skills, and managing headcount with discipline to end 2026 where we started."

Company headcount was roughly 29,000 at the start of 2026 and is roughly 30,000 now. Set against 404 Californian roles cut across four notices and a stated intention to hire for AI-focused skills, that describes a reallocation rather than a contraction, and the company says so itself rather than leaving anyone to infer it.

The Los Angeles Times report also attributes to the chief executive an expectation of roughly 700 further cuts before the end of the year. That figure is reported rather than quoted, so we would hold it loosely until it turns up in a filing or a transcript.

Flat totals do not soften an individual redundancy

Taking the statement at face value is the fair thing to do. Saying you are managing headcount with discipline to end the year where you started is a clear and unusually specific commitment for a vendor to make in public, and it does not read as evasion.

A flat company total still says nothing about what happens to the 287. The people leaving Santa Clara and San Diego built and supported the platform customers run, and a number that holds steady at the company level does not make one redundancy any smaller. Neither the notice nor the reporting says which teams were affected, and guessing would not help anybody.

What the hiring signal is worth to a practitioner

For anyone building a career on this platform, the readable part of the statement is where the hiring is pointed. ServiceNow says it is actively investing in and hiring for AI-focused skills, which lines up with where the company has been putting product work across its agent and AI product line. That is a signal a career plan can act on.

One company reallocating roles is not a labour market. Salesforce describing twenty thousand redesigned roles and Oracle's restructuring alongside its NetSuite work in India point in a similar direction, and three vendors still do not settle the question. Read this one as a data point, then check it against what your own employer and your clients are hiring for this quarter.

The question to put to your account team

For a customer, the question the notice raises is continuity, and the notice cannot answer it. Nothing in the filing or the reporting identifies which functions the 287 roles sit in, so there is no honest way to work out from public documents whether the people who support your implementation are among them.

Ask instead. Send your ServiceNow account team a short written question naming your assigned technical contacts, your customer success manager and your support escalation path, and ask whether any of those named people or roles change before the end of the year. A written answer is something you can hold against a renewal conversation, and the question takes ten minutes to write.

If you are mid-project, put the same question to your implementation partner about its own staffing. Send both this week and keep the replies with your renewal file.