ServiceNow Developer (Service Catalog & Workflow)

REQUIRED SKILLS

• 3+ years of ServiceNow development, including 2+ complex Catalog Items deployed to production with conditional logic, variable sets/MRVS, and data-driven forms.
• Flow Designer expertise, including multi-level approvals, subflows, custom actions, approval rules, and error handling.
• REST integration experience, including IntegrationHub/outbound REST, OAuth 2.0, JSON, error handling, and retries.
• Inbound integration experience using Scripted REST API or Table API for callbacks and status updates.
• Strong ServiceNow JavaScript, including Business Rules, Script Includes, Client Scripts, GlideRecord, and GlideAjax.
• Experience with reference qualifiers, Catalog UI Policies, Data Lookup Rules, and custom tables.

Responsibilities:: Catalog design and build

• Build Service Catalog items, record producers and variable sets for each access type, including multi-row variable sets where they are needed.
• Make the forms data-driven: reference qualifiers and lookup select boxes read from a custom mapping table (access type target group scope approvers), so new access types can be added without code changes.
• Write catalog client scripts, UI policies and data lookup rules for conditional fields, validation and duplicate-request checks.
• Publish the items in Service Portal / Employee Center with clear help text for business users.

Approval workflow logic

• Build the approval flows in Flow Designer, using subflows and custom actions, so each access type can have its own approval chain.
• Drive approvers from a table rather than hard-coding them. Chains can include the manager, a data owner, Compliance or Privacy, sequenced or in parallel.
• Enforce approval controls: requesters and the person receiving access cannot approve, delegations are recorded, approvals time out and escalate, and a rejection ends the request cleanly.
• Capture the access end date and business justification, and handle requests that are cancelled or changed mid-flow.

REST integration

• After approval, send the request to PingIDM's REST API using IntegrationHub REST steps or outbound REST messages. Authentication is OAuth 2.0, set up with credential and connection aliases.
• Build a Scripted REST API, or an equivalent inbound endpoint, so PingIDM can report back that fulfilment succeeded or failed. The callback updates and closes the request item.
• Add retries, error handling and logging, and route failures to a support queue so none are lost silently.
• Write the request number, approvers and timestamps to the request record so they can serve as audit evidence.

Quality and delivery

• Follow the ServiceNow team's coding standards, code review and update set / application repository process, working within a scoped application.
• Write Automated Test Framework (ATF) tests for the catalog items and flows. Support user acceptance testing and fix the defects it finds.
• Document the design, configuration and support runbook, and hand it over to the ServiceNow team. Move changes through change management, with the evidence a SOX-controlled change requires.