Senior SRE

Kestra Cloud is our fully managed SaaS edition of Kestra. Each customer gets a dedicated Kestra instance on dedicated infrastructure, so the platform is a fleet of isolated stacks rather than one shared cluster. It is in Beta today, running production workloads for early customers, with General Availability planned for 2027. Each instance runs arbitrary user code (scripts, containers, queries against their own systems) through hundreds of plugins, and the fleet grows with every new customer. Provisioning, upgrading, and observing dozens to hundreds of identical stacks without drift is the core problem.

We're looking for a Senior SRE to build and run Kestra Cloud: the infrastructure, the delivery pipeline, the monitoring, and the day-to-day reliability of the platform. You take ownership of large parts of the platform, from design to production, and ship them with the team.

You would join a team of three. You report to the Lead SRE and work alongside another SRE. Most of your week is hands-on (Terraform, Kubernetes manifests, CI/CD, and incident work), with real input on how the platform is designed.

You work closely with the Lead SRE, the platform engineering teams building the Kestra core, and our security engineer. This is a senior individual contributor role with real ownership, not a ticket-taking one.

• 5+ years in SRE, platform, or infrastructure engineering, with production ownership of the systems you built.
• Deep, production-grade Kubernetes expertise: you have operated multiple production clusters and know where they break (upgrades, configuration drift, networking, resource sizing).
• Strong Google Cloud experience: GKE, IAM, networking (VPC, private clusters, load balancing), and managed data services. Equivalent depth on AWS or Azure is not a substitute here.
• Strong Terraform: you have built reusable modules and managed state across many environments, not just written resources.
• Ability to design and document: you can show design docs or RFCs you wrote and explain the trade-offs you made.
• Real on-call and incident experience, including writing postmortems and turning them into durable fixes.
• SaaS operations background: you have run production systems for paying customers, with SLOs that mattered.
• Fluent in English and comfortable working autonomously in a fully remote environment.
• Pragmatism: you pick the boring solution when it works and can explain why.