ServiceNow SOMT Architect

We are looking for " ServiceNow SOMT Architect " for a Global IT Organisation baased out of UK

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.

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

• Lead discovery and produce the HLD, component LLDs and architecture decisions with client architects, product owners, business analysts and engineering teams.
• Define the TMF641-led service-order architecture, preserving upstream commercial-product ownership. Specify decomposition, attribute propagation, task orchestration and inventory outcomes.
• Approve CFS, RFS and ResourceSpec boundaries with the modeller. Define identifier ownership, model versioning, service relationships and the mapping to shared CMDB and assurance needs.
• Design the integration boundary for order handling, status and milestones, tactical TMF638-style inventory events, authentication, correlation, retries, error recovery and observability.
• Validate installed product capabilities and platform/application versions. Investigate service-order mapping gaps with vendor engineering and document supported extension or interim options.
• Define production-compatible milestone and notification behaviour, the conditions for adopting native APIs, and the testing and retirement approach for any interim implementation.
• Guide native Build workspace and manual fulfilment design. Preserve extension points for later southbound adapters without expanding the initial release into network automation.
• Set design and code-review standards, quality gates and release evidence. Review standalone test coverage and support client-led SIT, UAT and operational readiness decisions.
• Lead architecture walkthroughs, technical troubleshooting and developer enablement. Prepare support teams to understand dependencies, diagnose failures and deploy the delivered solution.

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.

Desirable experience

• TSOM, CSDM and telecom inventory experience; broadband, CPE, satellite connectivity or multi-domain fulfilment knowledge.
• TMF633 catalogue and event-management patterns, and architecture for later controller or supplier integrations.
• Relevant ServiceNow implementation or architecture credentials, supported by practical delivery evidence.

Expected deliverables

• Approved architecture, component designs, interface contracts, model decisions and a platform/version dependency assessment.
• Technical validation of representative order journeys, documented gap-resolution options and reviewed release and recovery designs.
• A complete technical handover, reusable extension guidance and a prioritised backlog for future capabilities.