Senior Site Reliability Engineer (AWS / Kubernetes) — US Pacific Time only

Location: candidates must be physically based in the US, within the Pacific time zone (GMT-7 to GMT-8), with the right to work in the US without sponsorship.

Format: remote, full-time, long-term

Rate: $30–40/h (contractor, net), long-term contract

Company: fast-growing, well-funded US product company (developer tools / data platform)

About the role

You will join the cloud infrastructure team responsible for the platform everything else runs on. This is not a "keep the lights on" role: the goal is to turn a large, fast-growing stateful system into a predictable, well-automated platform. Scale: petabytes of data, thousands of cores, constant ingestion, multi-region and multi-account AWS.

What you will do

• Operate EKS clusters across several environments (Karpenter, Cilium, ArgoCD / GitOps)
• Manage a multi-account AWS organization: provisioning, networking, IAM, cross-account connectivity
• Maintain and evolve the Terraform / Terragrunt IaC platform and its CI pipelines
• Improve tooling for deploys, schema changes, backups, restores and incident response
• Remove repeat operational pain through automation and self-healing systems
• Keep cloud spend under control
• Take part in on-call, with a focus on making incidents rarer

Requirements

• Deep production experience with Kubernetes (EKS preferred) at large scale
• Strong experience running production infrastructure on AWS across multiple accounts (IAM, networking)
• Terraform or Terragrunt at scale, including module design and state management
• Solid Linux knowledge (disk, memory, networking, failure modes) - Experience supporting stateful systems (databases, queues, storage)
• Comfortable owning systems end-to-end, including on-call - Fluent English

Nice to have

• ArgoCD and GitHub Actions
• Multi-region infrastructure
• Building infrastructure services for AI agents

To apply, please answer briefly in your cover letter: 1. Where are you physically based, and do you have the right to work in the US without sponsorship? 2. The largest Kubernetes / AWS setup you have operated: size, your role, and the stack. 3. Your expected rate (USD/h), and are you comfortable with a long-term contract engagement?