As the organization shifts from a legacy, tiered support model to a flat service operations structure built on end-to-end ownership, the team needs an engineer who can turn operational lessons into automated, self-service, and observable systems. This role is the technical engine behind that shift — replacing manual, reactive work with repeatable, automated, and continuously improving practices.
Beyond technical skill, this role calls for someone with a genuine can-do attitude — comfortable rolling up their sleeves, prototyping a fix rather than waiting for a perfect spec, and treating ambiguity as a starting point rather than a blocker. We're looking for someone who sees automation, security, and observability not as separate disciplines but as one continuous practice of making service operations faster, safer, and more self-sufficient over time.
Key Responsibilities
Automation Engineering & Infrastructure as Code
Design, build, and maintain infrastructure as code (IaC) using tools such as Terraform, Ansible, or equivalent, replacing manual provisioning and configuration with version-controlled, repeatable automation.
Build self-service tooling and pipelines that let SOT staff provision, deploy, and remediate common issues without engineering intervention.
Continuously identify manual, repetitive operational tasks and automate them, treating toil reduction as an ongoing responsibility rather than a one-time project.
Rapid, Secure Delivery
Own and evolve CI/CD pipelines to enable fast, frequent, low-risk releases, embedding security scanning and policy-as-code checks directly into the pipeline rather than as a separate gate.
Partner with development and operations staff to shrink lead time from code commit to production, removing bottlenecks wherever they appear.
Champion a shift-left security mindset, building guardrails that let teams move fast safely rather than relying on after-the-fact review.
Observability & Service Operations
Build and maintain observability across infrastructure and applications (metrics, logging, tracing, alerting) so issues are detected and diagnosed before they impact users.
Design dashboards and alerting that give the SOT actionable, real-time signal — not noise — supporting the team's end-to-end ticket ownership model.
Use observability data to drive proactive capacity planning, performance tuning, and reliability improvements.