ServiceNow Developer

We're looking for a ServiceNow developer who is a software engineer first. You'll build on the platform where the platform is the right answer, and build outside it when it isn't — then integrate the two cleanly. Much of the work is deciding which of those two things a given requirement actually needs, and being able to defend that call.

Day to day you'll take business problems that arrive as vague requests, work out what they really require, and deliver working solutions across ServiceNow and the surrounding estate.

What you'll do

• Design and build on ServiceNow: catalog items, workflows and Flow Designer, Business Rules, Script Includes, UI Actions and Policies, Scoped Applications, ACLs and role models
• Write server-side and client-side script that holds up — code that survives an upgrade
• Build integrations both ways: REST and SOAP, IntegrationHub spokes and custom actions, MID Server patterns, OAuth and token handling, scheduled and event-driven flows
• Build the parts that don't belong in ServiceNow — a Python or Node service, a scheduled job, a data pipeline, a lightweight UI — and integrate them properly rather than forcing everything into the platform
• Debug across boundaries: instance logs, transaction traces, API payloads, upstream systems, network and auth failures
• Push back on solutions that will cost more in technical debt than they save, and propose the alternative
• Own quality: version control, code review, ATF or equivalent test coverage, update set and CI/CD discipline, documentation someone else can pick up

What you need

• 4+ years building on ServiceNow, with real scripting depth rather than configuration-only experience
• Strong JavaScript, and at least one other language you're productive in — Python, Java, Go or similar
• Practical integration experience: REST APIs, authentication patterns, error handling, retries, idempotency, dealing with systems that behave badly
• SQL and a working understanding of data modelling
• Familiarity with Git, CI/CD, and the basics of running something in production
• Judgment about platform boundaries — when a requirement is a good fit for ServiceNow, when it's being shoehorned in, and what the alternative looks like
• Ability to work directly with business stakeholders and translate an ambiguous ask into a design

Nice to have

• ServiceNow CSA or CAD certification, or ITSM, ITOM, SecOps, HRSD or CSM module experience
• Cloud platform experience (AWS, Azure or GCP), containers, serverless
• Experience with an enterprise integration layer — Kafka, MuleSoft, message queues
• Front-end work outside the platform: React, Angular, Service Portal or UI Builder
• Exposure to AI-assisted development and applying LLMs to service workflows sensibly

What this role is not

This is not a configuration or admin role, and it is not a ticket-queue role. If your experience is mainly clicking through the platform UI and your instinct for every requirement is a new ServiceNow customization, this won't be a good fit — for you or for us. We need someone who reaches for the platform because it's the right tool, not because it's the only one they know.