Staff Site Reliability Engineer
Develocity
$180,000–$220,000from the description
Jul 23, 2026
—
Jul 24, 2026
What this job asks for AI summary
A founding member role on a newly formed SRE team, responsible for the reliability, availability, and performance of a SaaS toolchain observability platform running on Kubernetes and AWS. Day-to-day work spans incident response, on-call operations, automation, observability, disaster recovery, and shaping SRE practices such as SLOs, postmortems, and error budgets — while mentoring other SREs as the team scales. Suits an experienced SRE comfortable leading reliability efforts across engineering teams without direct authority.
Senior level · 7+ years · 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 9,300 people nationally plausibly meet what this posting asks for (software developers). range 5,600–14,000
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). This posting is about at that midpoint.
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 (7)
The role is titled 'Lead SRE' with no explicit seniority level word (Junior/Senior/Staff/etc.) in the title, so the title states no level; the 7+ years requirement and cross-team leadership scope support a Senior classification.
SOC classification is a genuine judgment call: the role is described as heavily automation- and code-focused ('drive automation', 'scripting proficiency', building observability tooling, IaC), which points to 15-1252 Software Developers. However, it also has a strong operational/infrastructure-operations dimension (on-call, incident response, managing production Kubernetes/AWS environments), which could support 15-1244. 15-1252 was chosen because the JD emphasizes building and automating systems rather than purely operating infrastructure someone else built.
AWS is listed as a hard requirement ('Cloud infrastructure expertise, preferably AWS'); the 'preferably' qualifies the specific cloud provider but the cloud infrastructure expertise itself is a hard gate. EKS, RDS, S3, and EC2 are listed as parenthetical examples under the same AWS bullet and are marked preferred rather than individually gated.
Prometheus and Grafana are listed together under 'observability tools' in the required qualifications; Terraform is listed under 'Infrastructure as Code' in the same section — all treated as hard gates.
Java and Kotlin appear together under Preferred qualifications as 'JVM language experience (Java, Kotlin)'; listed as preferred with Kotlin as an alternative.
The role is remote but restricted to EDT or CDT timezones; no specific US state or metro is given, so CBSA fields are left blank.
Compensation is stated as a US salary range of $180,000–$220,000/year.
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.