A ServiceNow system is a set of applications on one platform, each one a workflow that takes a request from someone, routes it to the right people, tracks it until it is done, and reports on how long it took. ServiceNow ITSM, IT service management, is the application named most by far: incidents when something breaks, requests for a new laptop or access, changes to a system that need approval, and problems that recur. It is the whole of the role at Accenture and the large services firms, where the platform is administered as part of running a client's systems, and it leads at the consulting arms, where the work is redesigning a client's service desk. The other applications, HR service delivery, customer service management, IT operations, security operations and the configuration database that records every server and application a company owns, are described in the text of job posts rather than named as skills. An engineer who knows one of them well knows how a ticket, a task, an approval and a service level fit together, and that understanding carries across all of them.
The platform is configured first and coded second. Forms, fields, tables, roles, approval rules, notifications and service catalogues are set up through the platform's own screens, and a large part of the everyday work, especially in the administration-heavy job posts, is this configuration rather than code. Flow Designer is the tool for building a workflow without code, by dragging the steps a request goes through, and it is named in a fair share of job posts and in most at the GCCs and the product companies. Where configuration runs out, the developer writes JavaScript.
ServiceNow is scripted in JavaScript, and it is the second most-named skill in the role, named in most job posts at the GCCs, the infrastructure services firms and the consulting arms, and far less at Accenture, whose posts describe administration more than development. The platform's own forms of it appear by name. Client Scripts run in the user's browser, to show, hide or check fields as a form is filled in. Script Includes are reusable server-side functions that other scripts call. GlideScript is the platform's server-side API, the set of objects a developer uses to read and write records, run queries and send notifications. Business rules, which run when a record is saved, and scheduled jobs are described in the text of posts. Together these make a ServiceNow developer, and they are asked for most at the banks' GCCs, where the centre builds and runs the parent's platform, and on the staffing companies' placements.
Most of what a user sees in ServiceNow is the standard interface and the service portal, where staff raise requests and track them. Customising that portal is frontend work, and frontend skills are tagged on a fair share of job posts, most at the GCCs and the staffing companies. HTML and CSS are named for styling the portal and its widgets, and Angular appears because the older service portal was built on it, with React in a few job posts for the newer workspaces. This is a small part of the role, and it is a plus rather than a requirement.
A service desk is only useful if it knows about the rest of the company. A new-joiner request has to create accounts in the HR system and the identity system, an incident has to come in from the monitoring tools, and a change has to be checked against the configuration database. IntegrationHub is the platform's own integration toolkit, with ready-made connectors to common systems, and it is named in a fair share of job posts and in a large share at the manufacturers' GCCs and the product companies. REST integrations, written by hand where no connector exists, are described in the text of posts. Data movement between systems is tagged on a fair share of job posts, most on the staffing companies' placements and at the product companies. A few of Accenture's job posts list Oracle Integration Cloud and the Sales Cloud, Service Cloud, Marketing Cloud and Experience Cloud beside ServiceNow, which is the same multi-platform integration role that appears in its SAP posts. Where a GCC also runs Workday or Salesforce, those appear beside ServiceNow in its job posts.
SQL is named in a fair share of job posts, most at the GCCs, because the engineer reads the platform's tables and builds reports from them, and reporting with Power BI or Tableau is tagged on a small share. ServiceNow itself is hosted by ServiceNow, so the cloud is named less than in any engineering role; Azure appears most, then AWS and GCP, mostly at the GCCs where the engineer also touches the systems the platform connects to. Build and release is tagged on a fair share of job posts and on most at the GCCs, and it means something particular here: ServiceNow moves changes between its development, test and production instances through update sets, and the newer practice of keeping those in Git and releasing them through Azure DevOps, Jenkins or GitHub Actions is what the tag reflects.
A minority of job posts, mostly at the GCCs, want Java or .NET beside the platform, for the applications that sit around it, and a few want the engineer to be the company's platform generalist, with Workday, Salesforce, Power Apps and Power Automate or the Pega Platform named alongside. In the ordinary ServiceNow job these are a plus.
Underneath all of it sits the way platform work is done: requirements gathered from the service owners, configuration and scripts built on a development instance, tested, moved through update sets with sign-off, and supported once live. ServiceNow itself releases a new version twice a year, and keeping a company's customisations working through each upgrade is a regular part of the job. Job posts count these as given and rarely list them as skills.
A ServiceNow engineer who knows ServiceNow ITSM well, can configure forms, catalogues and approvals, builds workflows in Flow Designer, writes JavaScript in Client Scripts, Script Includes and GlideScript, connects the platform to other systems through IntegrationHub and REST, and can read the tables in SQL, meets the core of nearly every job post. The variations belong to the employer. Accenture and the large services firms, the widest door, want ServiceNow ITSM administrators and developers at the mid level, with the role often described in general terms. The infrastructure services firms and the consulting arms want developers, with JavaScript on most job posts beside ITSM. The GCCs of banks, insurers, manufacturers and pharma groups want developers who build and run the parent's platform, with JavaScript, Flow Designer, IntegrationHub, SQL, the most frontend work and the most release process, and they are the most open to juniors. The staffing companies place developers with the full scripting set. Across all of them, the engineer who understands how a request moves through a company, and can make the platform move it, is the one every job post describes.