Member of Technical Staff (Site Reliability Engineer, Cloud Infrastructure)
Perplexity · San Francisco
About this role
**Member of Technical Staff (Site Reliability Engineer, Cloud Infrastructure)** Perplexity serves hundreds of millions of queries a month, and every answer and deployment runs on production infrastructure owned by the Cloud Infrastructure team—spanning Kubernetes clusters across a multi-account AWS estate, private networks to hyperscalers and neoclouds, and the storage layer behind user data and agentic workloads. We’re looking for SREs who treat reliability as a software problem. You’ll own compute, networking, and storage at scale, keeping production stable while the platform built on top of it evolves quickly. --- ## Responsibilities - **Own production at scale:** Run the compute, networking, and storage foundation behind consumer, Computer, API, and enterprise products; own availability, latency, and cost. - **Run the Kubernetes fleet:** Operate and upgrade EKS clusters hosting web services, search, datastores, and secure sandboxes. Tune scheduling, autoscaling, node lifecycle, DNS, and service networking. - **Engineer the network:** Design and operate VPC architectures, Transit Gateway and PrivateLink connectivity, load balancing, DNS, and egress across accounts, regions, and cloud providers. - **Keep data durable and fast:** Own storage (EBS, S3, DynamoDB, and managed databases/caches), including performance, durability, backups, and restores (tested). - **Manage everything as code:** Use Terraform and CI/CD. Build reusable modules and guardrails; ensure changes are reviewable, repeatable, and safe to roll back. - **Prepare for failures:** Define SLOs, build actionable alerts, design for zone/regional failure, and run game days + disaster recovery exercises. - **Lead incident response:** Be on the critical path when things break; drive incidents to resolution; write blameless postmortems; land fixes so the same failure doesn’t page again. - **Scale ahead of demand:** Own capacity planning, quotas, reservations, and cost efficiency for launches and traffic spikes. - **Automate away toil:** Build tooling (increasingly agent-driven) to make provisioning, upgrades, and remediation self-serve and hands-off. --- ## Qualifications We expect real depth in most of these: - **Deep AWS expertise:** VPC, IAM, EC2, EKS, ELB, Route 53, S3, EBS, including limits, failure modes, and cost implications. - **Production Kubernetes at scale:** Cluster upgrades, CNI, CoreDNS, autoscalers like Karpenter, and debugging production issues (e.g., at 3 a.m.). Writing Helm charts alone doesn’t count. - **Terraform mastery:** Module design, state management across many accounts, and safe large refactors/imports without taking production down. - **Strong networking fundamentals:** TCP/IP, DNS, TLS, load balancing, routing. - **Real coding ability:** Python, Go, or Rust for automation, tooling, and controllers—prefer automating a runbook over following it. - **Observability fluency:** Datadog, Prometheus, Grafana (or similar) and the judgment to turn signals into meaningful SLOs and alerts. - **Incident leadership track record:** Turn root-cause analysis into durable fixes. - **Ownership mindset:** You own problems end-to-end and do well when the path forward isn’t pre-defined. --- ## Additional Experience We Value - Multi-region active-active/failover architectures and disaster recovery programs with real recovery targets. - Proxies, service meshes, and kernel-level networking (Envoy, Istio, Cilium, eBPF). - GitOps and progressive delivery (Argo CD, Flu
Listing freshness
CronJobs last confirmed this listing 1h ago. If its source stops confirming the opening for seven days, this page is removed from active inventory.