Senior Site Reliability Engineer
Latitude AI · Pittsburgh, PA
$179,200–$268,800from the description
Jul 9, 2026
Pittsburgh, PA
Jul 21, 2026
What this job asks for AI summary
A Site Reliability Engineer role focused on keeping large-scale, mission-critical autonomous driving infrastructure healthy and observable. Day-to-day work involves building monitoring, alerting, and runbooks, writing Kubernetes controllers in Go, and collaborating with multiple engineering teams on incident response and postmortems. Suits engineers with production Kubernetes experience, cloud infrastructure skills, and a background in observability tooling.
Senior level · 4+ years · Pittsburgh, PA · Bachelor's required · 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 140 people in the Pittsburgh, PA area plausibly meet what this posting asks for (software developers). range 60–250
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $127,238 (middle half $97,661–$159,195). 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 'Site Reliability Engineer' with no level modifier, so advertised seniority is Unspecified; the 4+ years requirement and scope (production Kubernetes at scale, on-call, cross-team incident response, designing platform components) support a Senior classification.
Go and Python are listed together as a single hands-on development requirement ('Go or Python') — they are interchangeable options for the same gate, so each is emitted as a required/preferred flag with the other as its alternative.
Cloud experience is gated on 'AWS, GCP' as examples of cloud or cloud-native environments — AWS is the primary with GCP as an alternative.
Infrastructure-as-code is required; Terraform and CloudFormation are named as examples ('e.g.'), so Terraform is primary with CloudFormation as an alternative.
Observability tooling (metrics, logging, tracing) is required; the JD uses 'e.g.' for specific tools (Prometheus, Elasticsearch/Loki, Jaeger/Tempo), meaning the capability is gated but the specific tool is interchangeable — each named tool is captured with its peer as an alternative.
The salary range ($179,200–$268,800) is explicitly stated as applicable to California locations (Palo Alto). The role has offices in Pittsburgh, Dearborn, and Palo Alto; Pittsburgh is used as the primary CBSA since it is the stated HQ, but compensation may differ by location.
SOC confidence is Medium: the role writes Kubernetes controllers and production software in Go (pointing to 15-1252 Software Developers), but also has a strong operational/SRE flavor (monitoring, on-call, incident response) that could suggest 15-1244. The primary day-to-day work — building controllers, automation code, and platform components — tips it to 15-1252.
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.