Site Reliability Engineer (US - Central/Eastern time) at PostHog
—
Jul 15, 2026
—
Jul 21, 2026
What this job asks for AI summary
A site reliability engineering role focused on taming a large-scale, stateful AWS platform rather than routine operations work. Day-to-day involves managing multi-account AWS infrastructure, EKS clusters, Terraform/Terragrunt IaC pipelines, and building automation that reduces manual toil across petabyte-scale, multi-region systems. Suits engineers who enjoy deep ownership of complex production infrastructure and want to design self-healing systems rather than just respond to alerts.
Senior level · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 14,200 people nationally plausibly meet what this posting asks for (software developers). range 8,500–21,300
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (6)
The role title is 'SRE' but the JD emphasizes building automation, self-healing tooling, IaC pipelines, and platform-layer code — not merely operating existing systems — which places it closer to Software Developers (15-1252) than Systems Administrators (15-1244). The runner-up is 15-1244 given the strong operational/on-call framing.
Terraform and Terragrunt are listed together as a single requirement ('Terraform or Terragrunt'); Terragrunt is captured as an alternative.
Karpenter, Cilium, ArgoCD, GitHub Actions, and GitOps appear either in the job narrative describing the current stack or under the explicit 'Nice to have' section — none are hard gates in the Requirements block.
No compensation range is stated in the posting.
The posting targets US Central/Eastern timezone candidates; the caller has confirmed this is fully remote with a national candidate pool.
Caller marked this a fully-remote role — scored against the national candidate pool.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.