Systems Integration LifeCycle Engineer

The Systems Integration Lifecycle Engineer is responsible for establishing, implementing, and operating the service management framework that governs all Systems Integration-controlled assets, processes, and operational changes across the Nscale data center portfolio.

As the first execution hire within the Systems Integration organization, this role builds the operational governance foundation required for hyperscale operations by developing and administering change management, incident management, problem management, configuration management, and service request processes while integrating them seamlessly with Engineering, Construction, Operations, Business Operations, AI Infrastructure, and enterprise IT service management functions.

The Systems Integration Lifecycle Engineer designs and configures the enterprise workflows, governance controls, approval processes, and operational automation that enable controlled execution throughout the asset lifecycle. This includes implementing Jira Service Management, establishing the Configuration Management Database (CMDB) for Systems Integration assets, governing Change Advisory Board (CAB) activities, coordinating operational readiness workflows, and integrating alerting, incident response, and on-call processes with Pager Duty and Operations.

Working closely with the Operational Data & Observability Engineer, Enterprise Systems Integration Architect, Controls & Automation Lead, and Business Operations, this role ensures that operational events, telemetry alerts, engineering changes, and configuration updates flow through standardized, auditable processes that support operational reliability, regulatory compliance, customer transparency, and enterprise governance.

During the initial growth of the organization, the Systems Integration Lifecycle Engineer both designs and operates the service management function. As the Systems Integration organization matures, responsibility transitions from daily operational execution to governance, automation, continuous improvement, and enterprise service management strategy.

• Build the change management process from scratch: change categories (standard, normal, emergency), approval workflow, CAB cadence, Jira ticket template, change calendar
• Coordinate with Operations on cross-team change visibility: SI changes that affect the facility go through a unified process, not two separate ones
• Run the change advisory process day-to-day: chair the CAB, track the change queue, ensure post-implementation reviews happen
• Build the change freeze calendar aligned with Ward County go-live windows and Microsoft tenant notification requirements
• Build the incident management process alignment, severity levels, escalation paths, ticket template, on-call rotation, post-mortem format
• Integrate incident management with the existing Operations Pager Duty setup, and Business Operations alerts route to on-call, escalating to Operations when MEP systems are affected
• Handoff to Business Ops the incident process on-call rotation, ensure incidents are documented, drive post-mortems within SLA hours of resolution
• Build the known-error database from the first 30 days of operation

• Onboard team to Pager Duty on-call schedules, alert routing rules, escalation policies, integration with alerting sources
• Coordinate with Operations and the Telemetry Engineer on alert routing: BMS/SCADA alerts land in the right Pager Duty service, not a black hole
• Administer the CMDB for SI-governed assets
• Write the 5 core SOPs required, document every process gap discovered in the first 30 days the backlog Phase 3 leadership inherits, and move to Business Operations

• 5–8+ years as an ITIL practitioner, IT service management engineer, or operations engineer — has personally built change and incident management processes, not just used them
• Hands‑on Service Now or Jira Service Management at admin/configuration level
• Pager Duty administration experience — schedules, routing rules, escalation policies, integrations
• Datacenter or infrastructure operational context strongly preferred
• Ab…