Site Reliability Engineer (London)

About this role

About Edra Edra is solving one of the hardest problems in enterprise AI: AI models are generic but company processes are specific. We build AI agents that learn how processes actually run, and then run their operations. We're a Series A startup, backed by Sequoia and other leading VC firms, led by Co-Founders who created and led Forward Deployed AI Engineering at Palantir, and we're growing our team in New York and London.

We're a deeply technical team of engineers, AI researchers, and strategists with a high bar for talent and a shared belief that exceptional people are the foundation of everything great we'll build. The Role We're looking for a Site Reliability Engineer to join our infrastructure team as the second-in-seat hire. Our team ships fast enough that we're starting to hit GitHub's rate limits, and infrastructure has to stay a month ahead of that.

You'll be in key engineering meetings to ensure our infrastructure is ready before anyone asks, and to catch any decisions that may become infrastructure problems later. This is not a ticket queue. You'll decide what gets built, push back when a managed service already does what someone wants to hand-roll, and invent when no pattern exists. You'll also write real software, not just the infrastructure code underneath it.

We run containerized workloads on AWS and GCP, defined in infrastructure as code, with Postgres underneath. Some of our early infrastructure was built quickly before anyone owned it full-time. Part of the job is untangling that while keeping the team moving. What You'll Do Own our cloud infrastructure end to end: provisioning, security, reliability, and the infrastructure as code that defines it. Stay ahead of the engineering roadmap and have infrastructure ready before features land, working directly with the founders on where the infrastructure goes next Find where developers are waiting and remove the wait, whether that's CI, deployment, or environment spin-up.

A person sat waiting is the most expensive thing we run, so rational spend on velocity is always on the table Run the reliability practice: monitoring, logging, and alerting that fails loudly with a clear signal, and the response when it does Lead large infrastructure builds and own our product security posture Make the build-vs-managed-service call, and hold the line when the simpler path is the right one Read and write Python well enough to see the infrastructure implications of what the team's building and catch problems before they land Own AI model safety and the governance of agentic processes.