OT System Engineer

ROLE

OT System Engineer — Infrastructure Tower / Application Tower.

PURPOSE

As an OT System Engineer within the OT Operations team, you keep our clients' manufacturing IT environments running securely, reliably and efficiently — and you make them measurably better. Our scope sits at Purdue Levels 2 to 3.5.

You work either on the infrastructure layer (networks and segmentation, virtualization, operating systems, monitoring, backup, hardware) or on the application layer (MES, historians, databases, interfaces and integrations). Whichever your primary tower, you are expected to understand enough of the other to follow a problem across the boundary instead of handing it off.

You engage directly with clients to identify what they actually need, and translate their operational requirements into stable, scalable and well-documented implementations under the guidance of your Team Lead.

DIMENSIONS OF THE JOB

- You ensure operations run according to defined procedures, agreed service levels and planning, maintaining stability, reliability and security across client environments.

- You are accountable for the outcome of your assigned tasks within a defined scope, and you contribute proactively to process improvement rather than only responding to incidents.

- You own the operational and security side of the estate: run, support, patch, harden, monitor, back up, integrate, document and improve.

- You are assigned a primary tower by your Team Lead, and may be deployed across both towers as client demand and your skill profile allow.

- You escalan to Technical Leads and Subject Matter Experts when a problem exceeds your scope, with a clear and complete handover.

- The service is delivered on a rotating shift and on-call model. This is a structural condition of the role, not an occasional extra — see section 6.

KEY RESULT AREAS

4.1 Operational Service Delivery

Aim: Maintain system availability, operational stability and compliance within agreed service levels.

- Provide second-line support for the systems in your scope — incidents, requests and changes — following ITIL-based incident, request and change management.

- Work within the agreed SLA: respect priorities, response and resolution targets, escalation paths and communication rules towards the client.

- Perform proactive maintenance: patching and vulnerability mitigation, hardening, health checks, backup and restore verification.

- Register your time and ticket updates accurately and on time — service reporting and SLA evidence depend on it.

4.2 Structured Troubleshooting & Root Cause Analysis

Aim: Resolve problems at the cause, not only at the symptom — including problems that cross the infrastructure / application boundary.

- Diagnose systematically: reproduce, isolate, form and test hypotheses, and record what has been ruled out.

- Trace a transaction or data point end to end across the estate — from the shop-floor source, through interfaces and integration layers, into databases, applications and reports — to locate exactly where it breaks.

- Read and interpret logs, interface traces, database queries and monitoring data in the context of the client's production process.

#J-18808-Ljbffr