H CompanyTechnical Lead, Observability - London
H Company is hiring a Technical Lead, Observability - London (United Kingdom). Level rates it ; you can apply on Level.
AI in this role
Own observability strategy, technical design, and rollout for infrastructure supporting computer-use AI agents.
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.
How we rate this
Technical Lead, Observability - London at H Company rates 30 out of 100 for how much of the daily work is AI. That makes it Little AI (AI Level 1 of 4). The level is about AI in the job, not seniority.
Little AI. AI is not part of the work.
- ●●●● Builds AI80 to 100
- ●●●○ Works on AI60 to 79
- ●●○○ Uses AI40 to 59
- ●○○○ Little AI0 to 39
Levels come from how often the tools, models and workflows of the role are named in the posting itself. Open the description and count.
Prepare for this job
Built from this posting and from similar jobs on Level.
Skills and AI tools this role asks for
Questions you could be asked
- Tell me about a project where observability was part of your work. What did you do?
- Tell me about a project where site reliability engineering was part of your work. What did you do?
- Tell me about a project where system architecture was part of your work. What did you do?
- Tell me about a project where monitoring was part of your work. What did you do?
- Tell me about a project where distributed systems was part of your work. What did you do?
Adapt your resume
- List these exact terms on your resume: Observability, Site Reliability Engineering, System Architecture, Monitoring, and Distributed Systems. An applicant tracking system matches the wording, not the idea.
- Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.
Want an expert to read your CV for this job?
Free. Send your CV and the role you want next. We reply by email within 2 to 4 business days.
Get new remote AI jobs by email
One email a week with the new remote AI jobs, each rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.
Free. One email a week. Unsubscribe in one click.
Similar roles
Other roles that involve little AI, at other companies.
What kind of AI work fits you?
Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.
Find my next step