Observability & Tooling Engineer

Overview

The Observability & Tooling Engineer will join a global infrastructure operations team on a 6-month contract, focusing on developing tooling and automation solutions that enhance observability within a large-scale distributed infrastructure. The role involves close collaboration with Site Reliability Engineering (SRE), DevOps, and Platform Engineering teams to create scalable systems that ensure operational efficiency and infrastructure reliability.

Responsibilities

  • Design, develop and maintain internal infrastructure tooling and observability platforms across large-scale distributed environments.
  • Build solutions that transform high-volume logs, metrics, and events into actionable operational insights.
  • Develop and enhance monitoring, alerting, and incident response capabilities using the Grafana observability stack.
  • Automate infrastructure operations, including provisioning, cluster onboarding, inventory management, and lifecycle processes.
  • Develop and maintain infrastructure automation workflows using Ansible and AWX.
  • Build tooling to support capacity planning, performance benchmarking, and infrastructure optimisation.
  • Develop and integrate services using Ruby/Rails, Go, and REST APIs.
  • Maintain and improve CI/CD pipelines using GitHub Actions and self-hosted runners.

Requirements

  • 6+ years of experience in Infrastructure Engineering, DevOps, SRE, or Software Engineering.
  • Strong experience developing production-grade infrastructure tooling, automation, or platform solutions.
  • Hands-on experience with Grafana, Prometheus, Loki, Mimir, and Grafana Alloy.
  • Strong programming experience in Ruby/Rails, Go, or similar languages.
  • Experience with Ansible and AWX for infrastructure automation.
  • Practical experience working with Kubernetes in production environments.
  • Strong understanding of infrastructure monitoring, alerting, incident management, and operational reliability.
  • Experience building and maintaining CI/CD pipelines, ideally using GitHub Actions.