ServiceNoq SOMT Developer

Develop and test ServiceNow service-order workflows, integrations and workspace configuration. Translate approved stories and designs into maintainable components that support manual fulfilment now and provide extension points for future automation.

Proposed arrangement

Offshore delivery with regular collaboration during agreed UK working hours

Implementation through March 2027; selected resources may support April enablement

Exact start date, office location, allocation and engagement terms will be confirmed during selection and mobilisation.

Programme context

The programme establishes ServiceNow Order Management for Telecommunications (SOMT) for offnet broadband and low Earth orbit satellite access services. Orders arrive through an upstream integration layer using TMF641. The first release combines manual fulfilment, a native Build team workspace, lightweight service inventory and outbound notifications. Delivery progresses from Create to Cease, bounded MACDs, in-flight amendments and cancellations.

Responsibilities

• Configure service-order intake, validation, decomposition and fulfilment using approved service specifications, relationships, rules and reusable flows or subflows.
• Implement TMF641 request and response mappings, order status and milestone events, and tactical TMF638-style service-inventory notifications through the agreed mediation layer.
• Build manual tasks, approvals, queues and native workspace forms for Build engineers to record supplier references, service identifiers, fulfilment data and exceptions.
• Implement Create, Cease and approved change journeys with state validation, audit history and controlled recovery. Distinguish in-flight order amendments from changes to an active service.
• Implement correlation, validation, authentication, duplicate handling, retries and diagnostic logging. Keep order events and service-inventory events distinct.
• Work with the architect and modeller on catalogue mappings, stable identifiers, inventory updates and model version compatibility; reproduce platform gaps using agreed payloads.
• Own component, API contract, negative-path and regression tests before each release. Support client-led SIT, UAT and operational testing with evidence, diagnosis and correction of assigned defects.
• Maintain reviewed source and configuration, deployment packages, rollback guidance and technical notes. Assess affected components when platform patches or API contracts change.
• Demonstrate delivered features and coach client developers through code walkthroughs, small changes, testing and troubleshooting. Senior developers also lead component reviews and mentor colleagues.