Observability Engineer

Skills

About the Role

You will build, maintain, and evolve a Honeycomb-based observability platform for a globally distributed trading environment. You will define standards, data models, and integration patterns for telemetry collection, storage, and querying. You will drive OpenTelemetry adoption and provide reusable instrumentation patterns for Java, Python, and C++ services. You will partner with development teams to improve traces, metrics, and logs across critical services and user journeys. You will help service owners define SLOs, burn rates, alert triggers, and actionable observability signals. You will join the support rota and incident response, accelerate diagnosis with observability tooling, and lead post-incident reviews. You will mentor engineers, create training materials and runbooks, and develop best-practice guides for observability.

Requirements

• 2–4 years of relevant experience in observability, SRE, or platform engineering.
• Hands-on experience with Honeycomb or a similar observability tool such as Grafana, including dataset design, query building, production debugging, and reliability analysis.
• Experience implementing OpenTelemetry instrumentation in Java, Python, or C++, including custom collectors, exporters, and sampling strategies.
• Experience working with distributed microservices environments with high transaction volumes or strict reliability requirements.
• Strong communication and collaboration skills.
• Experience using Terraform to manage observability infrastructure as code in a cloud environment.
• Ability and willingness to cover UK working hours.

Responsibilities

• Build, maintain, and evolve the Honeycomb-based observability platform.
• Define platform standards, data models, and integration patterns for telemetry collection, storage, and querying.
• Drive OpenTelemetry adoption and provide reusable instrumentation patterns for Java, Python, and C++ services.
• Partner with development teams to improve telemetry coverage across critical services and user journeys.
• Help service owners define SLOs, burn rates, alert triggers, and actionable observability signals.
• Drive SLO adoption with SRE teams and engineering teams.
• Join the support rota and incident response to accelerate diagnosis and reduce resolution time.
• Lead post-incident reviews and produce actionable system and observability improvements.
• Mentor and upskill engineers on observability practices.
• Develop training materials, runbooks, and best-practice guides.

Benefits

• Hybrid working model with 3 days in the office.
• Tailored development programs.
• Mentoring opportunities with leaders.
• Committees, sports clubs, and social clubs.
• Extra time off for volunteering and community work.