kestra - Lead Tech SRE

• 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 • Queuing: Redis, Kafka, AMQP • Programming language: Java, TypeScript (you read it; you don't need to write it daily) • 8+ years in SRE, platform, or infrastructure engineering, including at least 2 years leading the technical direction of a team or a platform. • Deep, production-grade Kubernetes expertise: you have operated fleets of clusters at scale 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. • Expert Terraform: you have designed module structures and state layouts that scale to many identical customer environments, not just written resources. • Proven ability to architect, spec, and dispatch: you can show design docs you wrote, explain the trade-offs you made, and describe how you split the work and delivered it. • Real on-call and incident experience, including running postmortems and turning them into durable fixes. • SaaS operations background: you have run a product 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. • Experience running workloads that execute untrusted or user-defined code (sandboxing, gVisor, node pool isolation). • Built or operated a fleet control plane for per-customer environments (Kubernetes operators, Crossplane, GKE Fleet / Config Sync, or custom provisioning services). • FinOps practice on GCP: per-customer cost attribution, committed use discounts, spot node pools. • Exposure to SOC 2 or ISO 27001 audits from the infrastructure side. • Familiarity with workflow orchestration (Kestra, Airflow, Temporal, or similar) or the JVM in production. • YOUR FIRST SIX MONTHS • 1. Month 1: take over the current architecture, audit the current Kestra Cloud architecture, and map the gaps between Beta and GA. • 2. Months 2 to 3: publish the GA architecture spec and the SLOs, agree on them with the CTO, and turn them into a roadmap the team can execute. • 3. Months 4 to 6: deliver the first GA milestones (one-click provisioning of a customer instance, observability coverage, safe upgrade path) with your two SREs. • 4. After month 6: drive continuous improvement of the platform, including a re-architecture of the first version of Kestra Cloud based on what Beta and the first GA customers taught us.