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

Description

The company serves hundreds of millions of queries monthly.

Every answer, every Computer task and every enterprise deployment runs on production infrastructure that the Cloud Infrastructure team operates: a fleet of Kubernetes clusters across a multi-account AWS setup, private networks that reach hyperscalers and the neoclouds hosting its models, and the storage behind user data and agentic workloads.

The team wants SREs who see reliability as a software problem.

You will own compute, networking and storage at scale and keep production stable while the systems on top of them change quickly.

Responsibilities

• Own availability, latency and cost for the compute, networking and storage that support the consumer, Computer, API and enterprise products.
• Operate and upgrade the EKS clusters that run web services, search, datastores and secure sandboxes. Tune scheduling, autoscaling, node lifecycle, DNS and service networking so clusters hold up under bursty, fast-growing traffic.
• Design and run VPC architectures, Transit Gateway and PrivateLink connectivity, load balancing, DNS and egress across accounts, regions and cloud providers.
• Own the storage layer, including EBS, S3, DynamoDB and the managed databases and caches that services rely on. Cover performance, durability, backups, and restores that have been tested.
• Manage infrastructure through Terraform and CI/CD. Build reusable modules and guardrails so every change is reviewable, repeatable and easy to roll back.
• Define SLOs and build alerts that people can act on. Design for zone and regional failure, and run game days and disaster-recovery exercises that prove recovery works.
• Stay on the critical path during incidents. Drive them to resolution, write blameless postmortems, and ship fixes so the same failure does not page anyone twice.
• Plan capacity, quotas, reservations and cost so product launches and traffic spikes never wait on infrastructure.
• Build tooling, increasingly driven by agents, that makes provisioning, upgrades and remediation self-serve and hands-off for every engineering team.

Requirements

• The company expects real depth in most of the following.
• Deep knowledge of AWS services such as VPC, IAM, EC2, EKS, ELB, Route 53, S3 and EBS, including their limits, failure modes and costs.
• Production Kubernetes at scale: cluster upgrades, CNI, CoreDNS, autoscalers such as Karpenter, and debugging a faulty node at 3 a.m. Helm charts alone do not count.
• Terraform expertise: module design, state management across many accounts, and large refactors or imports done without taking production down.
• Solid networking fundamentals: TCP/IP, DNS, TLS, load balancing and routing.
• Python, Go or Rust for automation, tooling and controllers. You would rather automate a runbook than follow one.
• Familiarity with observability tools such as Datadog, Prometheus or Grafana, and the judgment to turn metrics, logs and traces into SLOs and alerts that matter.
• A record of leading production incidents and turning root-cause analysis into lasting fixes.
• You take ownership of problems end to end and work well when the path is not defined for you.
• Additional experience the company values:
• Multi-region active-active or failover architectures, and disaster-recovery programs with real recovery targets.
• Proxies, service meshes and kernel-level networking such as Envoy, Istio, Cilium or eBPF.
• GitOps and progressive delivery with Argo CD, Flux or similar tools.
• Enterprise and compliance settings: single-tenant or BYOC deployments, KMS or BYOK, and SOC 2 or similar controls.
• Running stateful systems in production, such as Postgres, Redis, Vespa or Elasticsearch.
• Multi-cloud or neocloud operations on GCP, CoreWeave or similar platforms.
• FinOps work: cost attribution, Savings Plans and reservations, and cutting infrastructure cost without adding fragility.