Before the detail, here's the challenge you'd help us solve.

We build the embodied intelligence that moves real vehicles safely, and the ecosystem a billion machines will run on in the future. Very few people in AI can say this. Every role here, whatever the team, plugs into that.

Here’s what this particular role covers.

🛠️ About our Site Reliability Engineering Teams

Wayve’s Site Reliability Engineering teams help make its technology reliable and resilient as deployments scale across AI infrastructure, cloud applications, and vehicle software.

This team builds the platforms, automation, and engineering practices that help engineers prepare for incidents, respond effectively, and turn lessons into lasting improvements. Working alongside engineers across Wayve, the team makes incident response simpler and more consistent, gives engineers the tools and confidence to own their systems’ reliability, and grows a strong community of responders. Its work supports engineering velocity, operational resilience, and safety as Wayve’s technology reaches more vehicles and markets.

🧠 Your day-to-day

Setting the technical strategy and multi-year roadmap for incident-management tooling, integrations, automation, data, and reporting

Treating incident management as an engineering platform: managing supported configuration with Terraform and building production-quality Python or Go automation, APIs, and webhooks

Evolving Wayve’s incident ecosystem across incident.io, Slack, Jira, service ownership, service catalogue, paging, observability, and reporting

Defining scalable standards for severity, incident roles, escalation, communications, cross-time-zone handovers, resolution, and closure

Building trustworthy incident data models and reporting that expose systemic risk and help leaders prioritise reliability investment

Raising the quality of post-incident reviews and corrective actions, turning incident learning into durable engineering improvements

Developing playbooks, training, and exercises that build a distributed community of capable Incident Commanders, communications leads, and responders

Partnering with embedded SREs and service-owning teams to improve on-call design, alert quality, runbooks, and production readiness, while preserving their operational accountability

Partnering with Safety on engineering-to-safety escalation, evidence, and handoffs

🧩 What you’ll be working on

Making incident-management configuration versioned, reviewable, and repeatable rather than dependent on manual administration

Giving engineering teams a consistent operating model while they retain ownership of their services and incidents

Getting responders timely, actionable context with less alert and coordination toil

Making incident data and post-incident learning influence reliability roadmaps and investment decisions

Growing a well-practised community of responders prepared for global operations

🙌 You should apply if

You have set technical direction, aligned multiple teams, and driven lasting improvements without reporting authority, communicating clearly with technical and non-technical stakeholders.

You have built or substantially improved platforms and tooling for incident response, on-call operations, or service reliability.

You have strong Terraform or equivalent infrastructure-as-code skills, alongside Python or Go experience building tested automation and API integrations.

You have deep practical knowledge of incident response, escalation, service ownership, and post-incident learning, including completing corrective actions.

You have defined reliable operational metrics and used incident data to identify recurring problems and prioritise improvements.

You have experience with incident-management platforms such as incident.io or PagerDuty, or integrating incident workflows with observability tools such as Datadog, Prometheus, or Grafana.

🌱 Not ticking every box? That’s totally okay! If you’re passionate about autonomy and keen to learn, we encourage you to apply even if you don’t meet every requirement.