×

Partner or End User: Where Should You Take Your ServiceNow Career?

It comes up on nearly every candidate call I have, usually about twenty minutes in, once we’ve got past the money.

“Should I stay in consulting, or should I go in-house?”

There isn’t a right answer. There’s a right answer for you, at this point in your career. Here’s how I’d think about it, based on the hundreds of ServiceNow professionals we’ve placed on both sides of it.

Project variety

Partner side wins this one, and it isn’t close.

At a partner you might touch six or seven customers a year. Different industries, different maturity levels, different problems. One quarter you’re on a greenfield ITSM build for a retailer, the next you’re untangling a CMDB after three years of neglect. You watch a lot of organisations solve the same problem badly, which is how people get good quickly.

End user is the opposite. One platform, one set of stakeholders, one roadmap. That sounds narrower because it is. But you go deeper. You find out what happens after go-live, which most consultants never see, because they’ve moved on by month four.

Partner work builds range. End user work builds depth. Early on, range compounds faster.

Ownership

End user side, comfortably.

At a partner, you build it and you hand it over. The SOW closes, the invoice goes out, and whatever happens next is someone else’s problem. Plenty of consultants find that frustrating after a few years. You never find out whether the thing you designed actually worked.

In-house, you live with your decisions. The shortcut you took in year one shows up in year three. That’s uncomfortable, and it’s also the fastest way to learn what good architecture really means.

People who come to us wanting to move from partner to end user almost always say the same sentence: “I want to own something.”

Commercial pressure

Different kind, not more or less.

At a partner, the pressure is utilisation. Billable hours, scope creep you have to police, the awkward conversation when the customer wants something the SOW doesn’t cover. Your value gets measured weekly and everyone can see it.

In-house, the pressure is political. You’re competing for budget with every other function. You’re justifying platform spend to people who still think ServiceNow is a ticketing tool. The timeline slips because a stakeholder went quiet for three weeks and nobody is chasing them but you.

Consultants moving in-house often expect the pressure to disappear. It doesn’t. It changes shape and gets slower.

Progression and money

More nuanced than people expect.

Partner progression is structured. Consultant, senior, lead, principal, practice lead. The ladder exists, and if you’re billing well and customers ask for you by name, you climb it. Certifications count for more here too, because they’re a commercial asset the partner can sell.

End user progression is flatter. There often isn’t a role above you. If the platform owner isn’t going anywhere, neither are you, and the only answer is to move companies. In last year’s survey, 49% said they’d start looking if a promotion hadn’t happened inside twelve months. That ceiling gets noticed fast.

On money, the headline numbers are closer than the myth suggests. The difference is usually in the shape of the package. Partner side carries bonus and sometimes commission, with more variance. End user tends to be steadier, with a better pension and more predictable hours.

So which one?

Rough rule, and it holds more often than not.

First five years, go partner. You’ll see more, break more and fix more, and that’s the quickest route to being properly good.

If you want to own a platform, build a team and stop living in a delivery cycle, go end user. Just check there’s a role above you before you sign.

And if you’re going in-house purely to escape the pressure, don’t. You’re swapping it, not losing it.

This is where you come in

We’ve run the ServiceNow Salary Survey for four years now. Every year somebody asks us to break the numbers down by partner versus end user. Every year we’ve had enough responses for a solid average, but not enough to split it properly and stand behind the answer.

This year we’re fixing that. Partner versus customer is one of the four sections in the 2026 report, alongside salaries and benefits, ways of working, and culture and progression. Same questions, split by which side of the fence you sit on.

The survey is open now and it takes about five minutes. The more responses we get, the sharper that split is, and the better the answer is next time someone asks you this question over a coffee.

I want to take part in the salary survey. Click here.

Much appreciated.

Want to see what came out of last year’s? Last year’s UK average was £76,000 and the US average was $148,000, 74% had taken a pay rise in the previous twelve months, and 82% held at least one certification. The full 2025 Global report is free here: 2025 Global ServiceNow Salary Survey.

The ServiceNow Job Nobody Trained For Is The One Everybody Now Needs

In the last fortnight ServiceNow patched three vulnerabilities in its AI Platform that each scored a perfect 10.0, none of which required authentication to exploit. In the same window it expanded the AI Control Tower to govern AI across any system in the enterprise, whoever built it. I think those two events point at the same career opportunity, and at a profile the market is short of.

What happened

The advisory came out on 27 August. CVE-2026-18885 allowed arbitrary code execution. CVE-2026-18886 allowed privilege escalation through improper access control. CVE-2026-74820 was a SQL injection flaw against the underlying database. All three scored 10.0, none required authentication or user interaction, and all three were rated low complexity. A fourth, a sandbox escape, scored 8.7.

ServiceNow patched hosted instances directly and released hotfixes for self-hosted deployments across Xanadu, Yokohama, Zurich and Australia.

Separately, coverage in early September described the AI Control Tower being expanded to discover, observe, govern, secure and measure AI deployed across any system, not just ServiceNow’s own. I have not pinned the exact announcement date, so take the timing loosely. Alongside that, this year’s acquisitions tell a consistent story: Armis for asset visibility, Veza for identity governance, and Sweep, which ServiceNow confirmed as completed on 1 September, for a governance layer spanning ServiceNow, Salesforce and HubSpot.

Read those together

ServiceNow is becoming the place enterprises govern all their AI. Which makes the ServiceNow platform itself a very high-value target, and makes the person who secures it a very hard person to replace.

The role that is forming

There is a gap opening between two established professions and it does not yet have a settled job title.

Security teams own vulnerability management but frequently lack depth on the ServiceNow platform itself. Platform teams own the instance but sit inside IT service management, where security advisories are not the daily rhythm. Advisories land in the space between and both sides assume the other has it.

The people who can occupy that gap need three things at once: real hands-on platform knowledge, enough security literacy to read an advisory and work out what it touches in a specific configuration, and enough standing to force an out-of-cycle change when it matters. That is an unusual combination. My expectation is that scarcity of that kind gets priced eventually, though I am not going to pretend I can show you a published benchmark for a role that does not yet have a settled title.

It is also getting broader. When agents hold credentials and act autonomously inside your environment, they become identities that need governing like any other. The controls we built over two decades for human insider risk mostly have not been applied to them, because attention has been on the productivity gain. Somebody has to close that, and it will not be a pure security person or a pure platform person.

How to move towards it

1. Start with what you already have. If you are a platform person, you are closer to this than a security generalist is. Platform depth is the harder half to acquire. Security literacy on top of real ServiceNow experience is a shorter journey than the reverse.

2. Learn the machine identity side. The Zurich release documentation covers capability for securing machine-to-machine integrations, including the Vault and Machine Identity consoles. Check the release notes for what is in your version, then get hands-on. This is the concrete, learnable part of the agent governance problem, and it comes up far less often in conversations than the strategy layer does.

3. Read the advisories, properly. Not the headline. Go and understand which components each CVE touched and why. Doing that four times will teach you more about the platform’s attack surface than any course, and it costs nothing.

4. Build one governance story. How you handled access, auditability, or the decision not to automate something. Even small. Hiring managers are nervous about exactly this and hardly any candidate raises it unprompted.

5. Learn to talk about risk in business terms. The question that decides these interviews is some version of: an agent takes a wrong action against customer data at 2am on a Sunday, what happens? If you can answer that with a clear account of accountability, detection and rollback, you are ahead of nearly everyone.

A realistic word on timing

I am not going to tell you this is an easy pivot or that a certification unlocks it. It is a genuinely senior profile and it usually forms out of an architect or senior developer who has been pulled into governance work informally and then made it their identity.

What I will say, and I want to be clear this is my read rather than a measured finding, is that the demand side is visible in what ServiceNow is buying and building, while the supply side looks thin to me from where I sit. If that is right, it is a good window. If I am wrong about the supply side, the worst case is that you have gone deep on security and governance skills on a platform that is becoming the enterprise control plane for AI, which is not a bad place to be wrong.

If you are three or four years into ServiceNow and wondering where to go deep, this is the most defensible direction I can point you at.

Thinking about your next move? We speak to ServiceNow professionals across the UK, Europe and North America every day and we are happy to give you an honest read on your profile, whether or not you are actively looking. Start a conversation.


Sources: ServiceNow security advisory, 27 August 2026 · SecurityWeek, 31 August 2026 · ServiceNow newsroom

ServiceNow’s June 2026 Layoffs: What We’re Hearing

For most ServiceNow professionals, getting a role there was the goal. Not a goal. The goal. I’ve had that conversation hundreds of times with TCs, AEs, and developers across the ecosystem: “If anything comes up at ServiceNow, let me know.”

This past week, I’ve been speaking to a lot of those same people. Most of them are now on the outside.

Here’s what we’re hearing.

The scale

On the morning of 10 June 2026, thousands of ServiceNow employees joined what they thought were routine meetings and found HR on the call. Within minutes, roles were eliminated. By the time the call ended, laptops were locked.

Numbers internally range from 300 to 2,500. California WARN notices filed with the California EDD confirm significant cuts at both the Santa Clara HQ and San Diego office. Multiple directors told us that even VPs were given less than 24 hours’ notice and a script. Nobody below SVP level knew who was on the list or why.

Who got cut, and there’s no clean pattern

This is the part that keeps coming up in every conversation we’re having. Normally in a restructuring, you can find the logic: a product being wound down, a layer of management being removed. Here, nobody can.

The cuts hit sales, solution consulting, marketing, engineering, training, product, CEG, and ServiceNow University. In India, 70% of the DemoHub organisation went in a single Zoom call. In ANZ, entire SSE teams were eliminated. In LATAM, top-performing SC managers got the call.

People with 10 years at the company were let go alongside people who started 90 days ago. Directors were cut on the same calls as junior ICs. One person we spoke to was mid-treatment for a serious illness with strong performance reviews. Another was on maternity leave.

The consistent message from management: “This is not performance related.”

The consistent reality: managers couldn’t explain who was chosen or why. One director summed it up well: “There is no logic, and there is no communication coming from the top.”

The acquisitions

This is almost certainly part of it. ServiceNow acquired Moveworks for around $3 billion (600-plus employees), Armis for a reported figure that brought in over 1,300 people, and Veza on top of that. One well-placed partner contact put it plainly: “They’re offsetting the headcount from the acquisitions. The 2,500 number makes sense when you add it up.”

The Moveworks deal has taken a lot of the heat internally. ServiceNow paid an enormous amount for an AI service management tool that many people we speak to think overlaps heavily with existing platform capability, and that some argue Microsoft will simply replicate through Teams within a couple of years. The view we keep hearing: it was a bad call made at scale.

What people are most frustrated about is that the people paying the price for that decision are not the people who made it.

And for those wondering whether staff who came across from the acquired companies were affected: some appear to have survived, while long-serving ServiceNow employees did not.

What this does to ServiceNow as a place to work

This is the question that matters most to us, because it affects everyone in the ecosystem.

For a long time, working at ServiceNow carried real weight. The culture under founder Fred Luddy was well regarded. People stayed. Loyalty felt like it went both ways. That reputation was a big part of why the company could attract strong talent away from bigger names.

What we’re hearing now is that the culture has been shifting for a while, and this is the moment people are naming as confirmation of something they’d already sensed. There’s frustration about spending on celebrity endorsements and sports hospitality while the people doing the actual work get cut. There’s frustration about an influx of leadership from Salesforce, a company with a notoriously volatile culture, and the sense that some of that has been imported.

One person who ran a team at ServiceNow for nearly a decade said it simply: “I recognised this wasn’t the company I joined eight years ago.”

The employer brand has taken a hit. Whether that’s recoverable depends on what happens next and how quickly.

The general feel

Shocked. Angry at the manner of it, more than the fact of it. But not beaten.

What stings most in the conversations we’re having isn’t the job loss. It’s being locked out of a laptop before the call finished. It’s a manager who had no idea it was coming and had nothing to offer. It’s 14-hour days and years of work, then a Tuesday morning Zoom with HR on the invite.

One person, nearly ten years in and a consistent top performer, said: “People got rich off my dedication. Shame on me for letting them use me like that.”

That’s the tone of a lot of conversations right now.

For what it’s worth: ServiceNow experience carries genuine weight in the market. The calls we’re already having from partners and customers looking to bring people in confirm that. If you’ve been affected, you’re not starting from scratch.

If you’ve been impacted

Get in touch. We know who’s hiring in the ServiceNow space, we’ll give you a straight conversation, and we won’t waste your time.

And if your organisation is looking at a market with a lot of exceptional ServiceNow talent suddenly available, we can help you move quickly on the right people.

ServiceNow Eyes $7 Billion Acquisition of Cybersecurity Startup Armis

ServiceNow is reportedly in advanced discussions to acquire Armis, a San Francisco-based cybersecurity startup, in a deal valued at approximately $7 billion. This acquisition would mark one of ServiceNow’s most significant strategic moves as the workflow automation giant continues to expand its security capabilities and strengthen its position in the enterprise technology market.

About Armis

Founded in 2015 by Yevgeny Dibrov and Nadir Izrael, both Israel Institute of Technology graduates with backgrounds in the Israel Defence Forces software units, Armis has become a leader in cybersecurity asset management. The company’s flagship Centrix platform provides real-time visibility, risk assessment, and protection across an organisation’s entire digital attack surface.

Armis has demonstrated impressive growth, reaching $300 million in annual recurring revenue earlier this year, up from $200 million the previous year. The company was last valued at $6.1 billion following a $435 million funding round in November 2024. Its client roster includes major organisations such as Colgate-Palmolive, United Airlines, and NHS South Wales.

Strategic Implications

This acquisition aligns with ServiceNow’s aggressive expansion strategy in the security space. Earlier this month, ServiceNow acquired identity security startup Veza for an undisclosed sum, and in March, the company purchased AI firm Moveworks. The potential Armis deal represents ServiceNow’s commitment to building a comprehensive security portfolio that complements its workflow automation platform.

For ServiceNow professionals and organisations invested in the ecosystem, this acquisition signals continued innovation and expansion of security capabilities within the platform. As the deal nears completion, industry watchers expect the integration of Armis’s technology to enhance ServiceNow’s security offerings and create new opportunities for implementation and specialisation.

The deal is expected to be announced within days, pending final negotiations.

Let's get started

Talk to one of our consultants todays, if you're looking to register a vacancy and apply for a role.

Upload your CV

Submit CV

This field is for validation purposes and should be left unchanged.
Name(Required)
Max. file size: 2 GB.