Member of Technical Staff (Site Reliability Engineer, Cloud Infrastructure)

Required

• We expect you to have real depth in most of these:
• Deep AWS expertise. You know VPC, IAM, EC2, EKS, ELB, Route 53, S3, EBS, etc. well past the console, including their limits, failure modes, and the bill that comes with them.
• Production Kubernetes at scale: cluster upgrades, CNI, CoreDNS, autoscalers like Karpenter, and debugging a misbehaving node at 3 a.m. Writing Helm charts alone doesn't count.
• Terraform mastery. You've designed module structures, managed state across many accounts, and run large refactors and imports without taking production down.
• Strong networking fundamentals (TCP/IP, DNS, TLS, load balancing, routing).
• You write real code in Python, Go, or Rust for automation, tooling, and controllers, and you'd rather automate a runbook than follow it.
• Fluency with observability tools like Datadog, Prometheus, or Grafana, and the judgment to turn metrics, logs, and traces into SLOs and alerts that matter.
• A track record of leading production incidents and turning root-cause analysis into durable fixes.
• You own problems end-to-end and do well when the path forward isn't laid out for you.
• Additional experience we value
• Multi-region active-active or failover architectures, and disaster-recovery programs with real recovery targets.
• Proxies, service meshes, and kernel-level networking: Envoy, Istio, Cilium, or eBPF.