Technical Lead, Observability - London

Hcompany

London +1 more

Hybrid

Who this role is best for

Geared toward hands-on technical leaders comfortable with cross-functional collaboration and observability system design, with a hybrid work arrangement and a focus on enterprise-scale infrastructure in London or Paris.

Best fit for

Candidates with experience leading observability initiatives across multiple technical stacks and teams
— “You'll work with every team at H, across infrastructure, product, engineering and research.”
Individuals who have designed and implemented observability systems using tools like OTEL, Prometheus, or Grafana
— “Have built self-managed observability systems, such as OTEL, Prometheus, Grafana, Loki, Mimir, Alloy, Elasticsearch or Kibana.”
Candidates who can define and measure complex technical and product-level SLAs, SLOs, and SLIs
— “Have defined both product-level and technical-level SLAs, SLOs and SLIs.”

Things to consider

Hybrid work requires three days a week in either London or Paris office, with occasional travel between the two
— “The role is hybrid, with three days a week in either our Paris or our London office and occasional travel between the two.”
The role demands a high level of autonomy and ownership over end-to-end observability strategy and implementation
— “You'll own observability across H: the strategy, technical design and rollout.”

How to stand out

Highlight experience in defining and measuring SLAs, SLOs, and SLIs across technical and product domains
— “Defining SLAs, SLOs and SLIs with our product, research and infrastructure teams.”
Showcase hands-on experience with building observability systems, not just managing them
— “Have built production instrumentation and telemetry integrations yourself.”
Emphasize your ability to set and execute engineering direction, with team adoption as a key outcome
— “Have set the direction for a substantial piece of engineering work, delivered it and got other teams to adopt it.”

Pace · SteadyCollaboration · HighAutonomy · HighDecision Impact · Company

Derived from job-description analysis by Serendipath's career intelligence engine.

What success looks like

Implementing observability systems across H
Defining and measuring SLAs, SLOs, SLIs

Typical background

Experience in observability and instrumentation

Skills & requirements

Required

Observability StrategyMetrics, Logs, Traces, Alerts, DashboardsSlas, Slos, SlisSystem Dependencies VisualizationSRE MeasurementsSelf-managed Observability SystemsKubernetes At ScaleEnterprise Multi-tenancyAsynchronous Agent Workflows

Preferred

AI Experience

Stack & domain

ObservabilityMetricsLogsTracesAlertsDashboardsSlasSlosSlisKubernetesEnterprise Multi-tenancyInferenceAsynchronous Agent WorkflowsOTELPrometheusGrafanaLokiMimirAlloyElasticsearchKibanaLeadershipTechnical DirectionTeamworkAdoptionProduct-level SlasTechnical-level SlasSRE MeasurementsError BudgetsBurn RatesMTTAMTTRMTTMComputer-use AgentsBrowsersDesktop ApplicationsInfrastructureProductEngineeringResearch

About the role

Original posting from Hcompany via Ashby

You'll own observability across H: the strategy, technical design and rollout. Your work will give visibility of the entire stack and surface the information the company relies on to make key decisions and quantify progress.
H builds computer-use agents that take actions in browsers and desktop applications. This role covers every technical system we run.
WHAT YOU OWN
The whole problem space. This is a lead role that stays hands-on: you will set the direction, design the stack, lead others through building it and work with internal teams on adoption. You'll be responsible for ensuring our teams measure what matters, and for learning our products and services in depth.
WHAT YOU'D BE DOING
Setting one observability strategy that can be applied across teams and technical stacks
Owning the implementation of the systems that manage metrics, logs, traces, alerts and dashboards
Defining SLAs, SLOs and SLIs with our product, research and infrastructure teams
Building end-to-end visibility of system dependencies, providing visualisations for users and context for agents
Automating how we track coverage, reliability, alert quality and the cost of execution
THE FIRST YEAR
By month 3, every H product has SLAs, SLOs and SLIs defined and measured in code, with compliance reports produced automatically. By month 6, a single complete solution covers metric collection, log processing and tracing. By month 12, every system at H uses the same SDKs and interfaces, whether for alarms, metrics, logs or traces.
WHO YOU'D WORK WITH
You'll work with every team at H, across infrastructure, product, engineering and research. Our VP of Engineering is the hiring manager.
WHAT WE THINK IT TAKES
Likely a good fit if you
Have set the direction for a substantial piece of engineering work, delivered it and got other teams to adopt it.
Have built production instrumentation and telemetry integrations yourself.
Have defined both product-level and technical-level SLAs, SLOs and SLIs.
Have used SRE measurements such as error budgets, burn rates and MTTA/MTTR/MTTM.
Have built self-managed observability systems, such as OTEL, Prometheus, Grafana, Loki, Mimir, Alloy, Elasticsearch or Kibana.
Have worked with Kubernetes at scale, enterprise multi-tenancy, inference or asynchronous agent workflows.
You do not need any experience in AI. If you match most of this but not every point, don't hesitate to apply.
HOW WE HIRE
Four stages: a 30-minute call with our Talent team, a 60-minute technical assessment, a 60-minute system design interview and a closing 30-minute conversation with the hiring manager.
Our process is tailored to the requirements for this specific role: the system design interview and the technical assessment closely match the work you would be delivering from day one.
PRACTICALITIES
The role is hybrid, with three days a week in either our Paris or our London office and occasional travel between the two. We offer a competitive package.

Source: Hcompany careers (Ashby)