Member of Technical Staff (Site Reliability Engineer, Cloud Infrastructure)
PerplexityRemote · US onlyFull-timePosted 25 days ago
$220k–$405k/yr listed by the employer
Above the typical $216k a year for staff-level remote DevOps, SRE & Cloud Engineer jobsHow we compare
How we compare. Typical is the median yearly pay of 72 staff-level remote DevOps, SRE & Cloud Engineer jobs that list pay, from the employers' own postings. About means within 5%.
Operate and improve production compute, networking, storage, and Kubernetes infrastructure across AWS accounts and regions.
Manage infrastructure as code, build reusable modules and guardrails, and automate provisioning, upgrades, and remediation.
Define SLOs and alerts, plan for capacity and failures, and run game days and disaster-recovery exercises.
Lead production incident response, write postmortems, and implement durable fixes.
Summarised from the posting by AI and can be wrong. The full description is the source.
Requirements
Experience
Production Kubernetes experience at scale, including cluster upgrades, CNI, CoreDNS, autoscalers such as Karpenter, and node debugging
Track record of leading production incidents and turning root-cause analysis into durable fixes
Ability to own problems end-to-end and work when the path forward is not laid out
Experience with multi-region active-active or failover architectures and disaster-recovery programs with real recovery targets (preferred)
Experience with proxies, service meshes, and kernel-level networking, such as Envoy, Istio, Cilium, or eBPF (preferred)
Experience with GitOps and progressive delivery tools such as Argo CD or Flux (preferred)
Experience with enterprise and compliance environments, including single-tenant or BYOC deployments, KMS/BYOK, and SOC 2 or similar controls (preferred)
Experience running stateful systems in production, such as Postgres, Redis, Vespa, or Elasticsearch (preferred)
Experience with multi-cloud or neocloud operations, such as GCP or CoreWeave (preferred)
FinOps experience with cost attribution, Savings Plans, reservations, and infrastructure cost optimization (preferred)
Skills
Deep AWS expertise, including VPC, IAM, EC2, EKS, ELB, Route 53, S3, and EBS
Terraform mastery, including designing modules, managing state across many accounts, and performing large refactors and imports
Strong networking fundamentals: TCP/IP, DNS, TLS, load balancing, and routing
Ability to write automation, tooling, and controllers in Python, Go, or Rust
Fluency with observability tools such as Datadog, Prometheus, or Grafana, and using metrics, logs, and traces to create SLOs and actionable alerts
Your match
Sign in and add your resume to see which of this job's requirements it shows.
Saved to your account, encrypted. The AI that reads it doesn't keep it or train on it.
Full job description
From Perplexity’s careers site
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, private networks that reach hyperscalers and the neoclouds serving our models, and the storage underneath our 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 and keep production stable while everything built on top of it is changing fast.
RESPONSIBILITIES
Show full descriptionShow less
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.
Lead incident response. Be on the critical path when things break. Drive incidents to resolution, write blameless postmortems, and land the fixes so the same failure never pages anyone twice.
Scale ahead of demand. Own capacity planning, quotas, reservations, and cost efficiency so product launches and traffic spikes never wait on infrastructure.
Automate away the toil. Build tooling, increasingly agent-driven, that turns provisioning, upgrades, and remediation into self-serve, hands-off workflows for every engineering team.
QUALIFICATIONS
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.
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.
GitOps and progressive delivery: Argo CD, Flux, or similar.
Enterprise and compliance environments: single-tenant or BYOC deployments, KMS/BYOK, SOC 2 or similar controls.
Running stateful systems in production: Postgres, Redis, or search engines like Vespa or Elasticsearch.
Multi-cloud or neocloud operations (GCP, CoreWeave, or similar).
FinOps: cost attribution, Savings Plans and reservations, and making infrastructure cheaper without making it fragile.