# Senior SRE at Kestra

> Remote · Europe · Senior · DevOps / SRE / Infra · open. Source: https://alderhq.app/jobs/ashby%3Akestra%3A70662b46-8fdb-486c-96eb-33fe71c5514a (read 2026-11-21).

## Facts (observed)

- Company: [Kestra](https://alderhq.app/companies/kestra)
- Location text: Europe
- Where it can be done from (inferred): Remote · Europe (evidence: "Remote role open worldwide")
- Posted: 2026-10-29 (23 days ago)
- First seen by alder: 2026-11-02 · last verified: 2026-11-19
- Reposted: 0 times · edited: 1 times
- Apply on the employer's site: https://jobs.ashbyhq.com/kestra/70662b46-8fdb-486c-96eb-33fe71c5514a
- Skills listed (inferred): Node.js, PostgreSQL, Elasticsearch, GCP, Kubernetes, Docker, Terraform, SQL

## Pay and sponsorship

- Posted pay: not posted

## Description (the employer's text)

### About Kestra

Kestra is the universal orchestration platform: open source, declarative, and designed to orchestrate data pipelines, IT automation, business workflows, and AI/agentic systems.

Trusted by over 10,000 organizations worldwide, including JPMorgan Chase, Bloomberg, FILA, and Crédit Agricole, Kestra orchestrates mission-critical workloads at scale. The open-source project has close to 30,000 GitHub stars, hundreds of contributors, and a fast-growing global community.

### About the role

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.

### What you would do

### Architecture & specs

Contribute to the target architecture of Kestra Cloud on GCP: the per-customer dedicated stack (cluster, network, databases, queues), how it is templated and versioned, and the path from Beta to GA.

Write design docs (RFCs, ADRs) for the components you own, and argue the trade-offs: cost per customer vs isolation level, GCP project vs cluster vs node pool per customer, managed service vs self-run.

Implement SLOs and error budgets per service and per tier: the SLIs, the dashboards, and the burn-rate alerts behind them.

### Delivery

Build Terraform modules and Helm charts that scale to a fleet of identical customer environments, and apply (and improve) the team's GitOps conventions. You review your peers' work and they review yours.

Automate the customer instance lifecycle: provisioning, upgrades, scaling, backups, migration, and decommissioning, with no manual steps.

Run the release path of Kestra Cloud with ArgoCD and GitHub Actions: progressive rollouts, rollback, and upgrade safety across the whole fleet of customer instances.

### Monitoring & operations

Build and extend the observability stack (metrics, logs, traces, alerting) so that issues are caught before customers report them.

Take part in on-call and incident response: write runbooks, lead incidents when you are on call, run blameless postmortems, and ship the follow-ups.

Plan capacity for a workload that is bursty by nature, and keep autoscaling honest.

### Continuous improvement

Improve cost efficiency (FinOps) on GCP: per-customer cost visibility, right-sizing, committed use, and spot where it fits.

Harden the platform with our security engineer: network policies, workload identity, secrets, and audit trails toward SOC 2 expectations.

Feed back into the product: when Kestra itself makes the cloud hard to run, you write the issue, propose the fix, and work with core engineering to land it.

### Our Tech Stack

Cloud: GCP (GKE, Cloud SQL, GCS, Cloud Load Balancing, IAM / Workload Identity)

Infrastructure as Code: Terraform, Helm

Orchestration: Kubernetes, Docker

Deployment & Repository: GitHub Actions, ArgoCD

Monitoring & Logs: OpenTelemetry, Elastic, Prometheus, Grafana

Datastore: PostgreSQL, Elasticsearch

---
Data: alder (https://alderhq.app). Cite https://alderhq.app/jobs/ashby%3Akestra%3A70662b46-8fdb-486c-96eb-33fe71c5514a and the date you read it. Observed facts come from the employer's own listing; location reach, level, family and skills are inferences.
