Member of Technical Staff (Site Reliability Engineer, Cloud Infrastructure)New$220K–$405K

Perplexity
Apply now

The opportunity

Perplexity serves hundreds of millions of queries a month. Every answer, every Perplexity Computer task, and every enterprise deployment runs on production infrastructure owned by the Cloud Infrastructure team: a fleet of Kubernetes clusters across a multi-account AWS estate,…

What you'll do

  • Own production at scale. Run the compute, networking, and storage foundation: behind Perplexity's consumer, Computer, API, and enterprise products, and own its availability, latency, and cost.

  • Run our Kubernetes fleet. Operate and upgrade the EKS clusters that host web: services, search, datastores, and secure sandboxes. Tune scheduling, autoscaling, node lifecycle, DNS, and service networking so clusters stay healthy under bursty, fast-growing load.

  • 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 the storage layer (EBS, S3, DynamoDB, and the: managed databases and caches our services depend on), including performance, durability, backups, and restores that have actually been tested.

  • Manage everything as code. Run infrastructure through Terraform and CI/CD.: Build reusable modules and guardrails, and make every change reviewable, repeatable, and safe to roll back.

  • Prepare for failures. Define SLOs, build alerts that someone can act on,: design for zone and regional failure, and run game days and disaster-recovery exercises that prove recovery works.

What they're looking for

  • 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.