Site Reliability Engineer
Summary
Staff-level SRE to help run and evolve the infrastructure behind Akka's platform for AI agents and distributed systems: writing/operating Go Kubernetes operators, managing AWS/Azure/GCP clusters via Crossplane, Terraform and Flux, running managed Postgres, and building observability and security with Prometheus and OpenTelemetry.
- 7+ years in infrastructure or platform engineering, with production experience across AWS and Azure. GCP is a plus.
- Experience operating Kubernetes controllers built on controller-runtime in production: CRDs, admission webhooks, finalizers, status conditions, and debugging a reconcile loop that isn't converging. You can read Go well enough to trace a reconciler to a root cause.
- Infrastructure as code with real production work, Terraform, and Crossplane at the level of authoring Compositions and XRDs rather than only applying claims, delivered through Flux and Kustomize.
- Operating managed Postgres (RDS, Cloud SQL, or Azure Flexible Server) in production, point-in-time restore, major-version upgrades, and moving a live database between instances inside a bounded outage window.
- Observability at scale with the Prometheus operator, scrape and relabel configuration, cardinality and cost control, alert rules as code, and distributed tracing with OpenTelemetry. Running a long-term metrics store (Cortex, Mimir, Thanos) is a plus, not a requirement.
- Securing Kubernetes clusters, service mesh (Linkerd or similar), OIDC/workload identity, mTLS, cert-manager for PKI including trust-anchor rotation, and secrets management via cloud KMS.
- Production on-call experience, you've carried a pager and written up what happened afterward.
- Skilled use of LLMs as a tool to sharpen your work, not to run on autopilot.
- Strong written communication, we weigh this heavily in our process.
- Sizing JVM services in containers, heap versus container limits, direct memory, GC behavior, and reading a heap dump. Our platform computes JVM flags per service, and getting it wrong shows up as OOMKilled.
- Operating event-sourced systems, projection lag, offsets, replay semantics, and what a journal replay does to a read model. Our own control plane is event-sourced, and so are our customers' workloads.
- Messaging or streaming systems (Kafka, Pub/Sub, or similar) at production scale.
- Teleport or a similar access plane, managed as code.
- Distributed, stateful, or actor-based systems (Akka, Erlang/OTP).
- Competitive salary with performance-based incentives.
- Comprehensive health and wellness benefits.
- Opportunities for professional development and continuous learning.
- Flexible remote working environment.
- Collaborative, inclusive, and innovative company culture.
- A transparent, distributed work environment with a strong focus on work-life balance.
- Challenging work that interacts with innovative applications used by millions.
- A collaborative culture that attracts the "brightest minds" in the technology community.