Solution Architect (ServiceNow & Integrations) - Fixed Term Contract (12 Months)

The Solution Architecture team within IT Delivery defines, governs, and communicates end-to-end business and technical solution designs for IFS. We act as a bridge between business capability needs and technical implementation, ensuring solutions align with enterprise standards, security, and operational excellence.

This role is focused on ServiceNow as a strategic platform for service management and customer service workflows, and on the integrations that connect ServiceNow to the wider enterprise ecosystem (Salesforce Service Cloud, Azure DevOps, P2 Central, P2 Store, and the Qbyte knowledge base).

You will own architecture decisions and integration contracts, guide delivery teams through design and implementation, and ensure solutions are resilient, observable, and supportable in production. You will work closely with Service Operations, Security, Product Owners, and Engineering teams across geographies.

Our Senior Solution Architects lead the design of scalable ServiceNow solutions and integrations, balancing speed of delivery with long-term maintainability, governance, and a high-quality customer and employee experience.

Role summary

As a Senior Solution Architect (ServiceNow & Integrations) - Fixed Term Contract (12 Months), you will own end-to-end solution architecture for ServiceNow capabilities and their integrations across a multi-system service ecosystem. The role requires strong ServiceNow platform expertise plus deep integration experience spanning ServiceNow, Salesforce Service Cloud, Azure DevOps, and internal platforms including P2 Central, P2 Store, and the Qbyte Wiki/knowledge base.

You will lead architecture definition, integration design, and governance for service-related processes such as tenant provisioning triggers, case/work item synchronization, file/attachment handling, customer communications (email-to-case), and service feedback (SurveyVista). You will ensure solution quality, security, operability, and long-term maintainability—while enabling delivery teams with clear patterns, standards, and implementation guidance.

Key responsibilities

1. Solution architecture & technical leadership

• Own solution architecture for ServiceNow-driven initiatives and related integrations across the service ecosystem.
• Translate business needs into high-quality solution designs (HLD/LLD), integration contracts, and delivery-ready specifications.
• Define target architecture, principles, and patterns (integration, data ownership, security, observability), and ensure consistent application across initiatives.
• Lead architecture governance: design authorities, peer reviews, risk/issue mitigation, and technical decision records.

1. ServiceNow platform architecture (CSM/ITSM and beyond)

• Architect ServiceNow solutions using platform best practices (data model, access controls, performance, maintainability).
• Design and guide implementation for workflows using Flow Designer, scripting where required, and automation patterns suitable for enterprise scale.
• Drive platform quality: upgrade readiness, non-functional requirements, monitoring/alerting, and operational runbooks.

1. Integration architecture (core requirement)

• Design secure, resilient integrations using REST/SOAP APIs, event/webhook patterns, and integration best practices (idempotency, retries, dead-letter handling, correlation IDs, and SLA monitoring).
• Leverage ServiceNow Integration Hub (spokes, actions, subflows) and MID Server approaches where needed for secure connectivity.
• Define interface contracts, error models, data mapping, throughput expectations, and operational support model for each integration.
• Partner with engineering teams to implement and validate integrations end-to-end, including testing strategy and production cutover planning.

1. Salesforce Service Cloud & service intake alignment

• Provide architectural guidance for coexistence and/or migration scenarios involving Salesforce Service Cloud and ServiceNow.
• Ensure correct handling of:
  • Email-to-Case patterns and behaviours, including attachment capture and visibility.
  • Email-to-Case Premium (third-party enhancement) where in scope, including operational impacts and constraints.
  • Apex Case Attachment patterns and Salesforce file/attachment model (Attachment vs Files, Content Document Link/Content Version), especially where downstream systems (e.g., P2 Store) are involved.
  • SurveyVista survey capture and reporting integration requirements.

1. Azure DevOps integration & delivery enablement

• Architect and govern integrations between ServiceNow and Azure DevOps for case/work item synchronization and delivery transparency.
• Apply appropriate patterns using ServiceNow’s Azure DevOps integration capabilities (e.g., triggers/webhooks where applicable) and ADO APIs.
• Align DevOps/change processes where needed (e.g., gated releases / change approvals).

1. P2 Central & P2 Store (domain-specific platforms)

• Own solution design for integrations involving:
  • P2 Central: tenant provisioning triggers, entitlement/admin workflows, and contract-compatible interface changes.
  • P2 Store: file provisioning, large attachment handling, and case comment/notification flows.
• Define system-of-record boundaries (especially for entitlements and provisioning status), integration triggers, and auditability requirements.
• Ensure parity with existing flows (where migrating from Salesforce to ServiceNow) while improving clarity, supportability, and security.

1. Knowledge base / documentation governance (Qbyte Wiki)

• Ensure architecture decisions, integration specs, and operational runbooks are captured and maintained in the agreed knowledge system.
• Demonstrate working knowledge of IFS Qbyte wiki/knowledge base usage and (where required) the process patterns for enabling Qbyte REST API access via service accounts and controlled access.

1. Stakeholder management & collaboration

• Work closely with Product Owners, Service Operations, Delivery, Security, and Platform teams to drive alignment and delivery outcomes.
• Communicate architecture clearly to both technical and non-technical stakeholders; proactively surface risks, dependencies, and trade-offs.

1. Coaching and capability uplift

• Mentor Solution Architects/BSAs/developers in platform and integration best practices.
• Promote reusable integration patterns, reference architectures, and consistent documentation standards.