Site Reliability Engineer at Workiy
Scottsdale, AZ
—
Aug 6, 2026
Scottsdale, AZ
Sep 24, 2026
What this job asks for AI summary
A Site Reliability Engineer role focused on keeping large-scale, high-performance applications running across hybrid on-premises and cloud environments. The work spans automation scripting, observability instrumentation (distributed tracing, dashboards), containerized workload management on GKE/RKE, and production incident response. Suits engineers comfortable writing code in Go or Python while also owning platform reliability and cloud migration work.
Senior level
“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
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 Aug 8, 2026. It is a model, not a headcount.
Why we read it this way (7)
The job description is duplicated verbatim — all requirements appear twice with identical wording. The extraction is based on a single pass; no additional requirements were found in the repeated block.
No work location is specified anywhere in the posting; CBSA and state fields are left blank. Remote status is unknown and defaults to false.
The role title is 'Site Reliability Engineer' with no level modifier, so advertised seniority is Unspecified. The breadth of requirements (hybrid cloud, containerization, observability, automation coding) supports a Senior classification.
The SOC classification is a close call: the role writes automation code and builds tooling (pointing to 15-1252 Software Developers) but also has a strong operations/infrastructure flavor (pointing to 15-1244). 15-1252 was chosen as primary because the JD explicitly requires writing automation scripts and building dashboards in programming languages.
The database requirement lists several options as alternatives ('one or more'); Oracle is used as the primary name with the others captured as alternatives. All are drawn from the same required-skills block.
The GraphQL framework examples (Apollo, Prisma, Hasura) appear with 'etc.' suggesting they are illustrative; Apollo is listed as the primary with the others as alternatives, and the group is marked preferred since the framing is 'experience working with specific GraphQL Framework' without firm gating language beyond the broader GraphQL requirement.
No compensation, benefits, or employment-type information is provided in the posting.
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.