ServiceNow SOMT Architect

• Practice Cloud & Infrastructure

• Technologies ServiceNow

• Location London, United Kingdom

• Type Contract

ServiceNow SOMT Architect
Telecom service fulfilment architecture and technical leadership
Own the SOMT solution architecture and guide its implementation for two access-service journeys. Establish reusable service-order patterns, supported integrations and extensible inventory models, while making platform dependencies, technical decisions and delivery risks explicit.

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.
 

Essential experience and skills

• Demonstrable architecture ownership of ServiceNow telecom order-management or service-fulfilment implementations, with evidence of delivery beyond conceptual designs.
• Strong understanding of service-order lifecycles, CFS/RFS modelling, resource specifications, catalogue-driven decomposition, attribute propagation and service inventory.
• Practical ability to distinguish TMF622 product ordering, TMF641 service ordering and TMF638 service inventory, and to define usable contracts rather than rely on API labels alone.
• Hands-on understanding of ServiceNow workflows, scripting, native workspaces, integration patterns and supported extension mechanisms sufficient to review code and diagnose implementation gaps.
• Experience with CMDB and service-model alignment, access control, non-functional requirements, release compatibility, upgrade impact and operational supportability.
• Ability to lead vendor-engineering discussions, compare configuration and custom-development options, and communicate scope, effort and dependency impacts clearly.
• Experience establishing design decisions, acceptance evidence, technical handover and shared ownership across onsite, offshore and client teams.

• share
• 
• 
• 
•