Site Reliability Engineer - Vice President
iCapital · Salt Lake City, UT
$130,000–$160,000from the description
Jul 6, 2026
Salt Lake City, UT
Jul 21, 2026
What this job asks for AI summary
A senior SRE role focused on building and owning reliability infrastructure for a Kubernetes-based platform on AWS. Day-to-day work spans defining SLOs/SLIs, standardizing observability across metrics, logs, and traces using infrastructure-as-code, leading incident response and postmortems, and driving automation to reduce operational toil. Suited to engineers with deep production experience across distributed systems and multiple observability toolchains.
Senior level · 7+ years · New York-Newark-Jersey City, NY-NJ-PA · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 2 times — it's one opening, so apply once.
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 830 people in the New York-Newark-Jersey City, NY-NJ-PA area plausibly meet what this posting asks for (software developers). range 620–1,100
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.
What the occupation pays Median $170,499 (middle half $133,523–$210,499). 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 title is 'Site Reliability Engineer' with no level modifier, so advertised seniority is Unspecified; the 7+ years requirement and scope (leading incidents, driving org-wide standards, cross-team influence) firmly support Senior.
SOC classification is a genuine judgment call: the JD emphasizes building automation, IaC, and observability tooling (shipping code → 15-1252 Software Developers), but also has a strong operations/incident-response component; 15-1244 is the runner-up.
Terraform is listed as 'preferred' in the IaC sentence but sits squarely in the required Qualifications section ('Strong IaC skills (Terraform preferred)'), making it a hard gate on IaC capability with Terraform as the named primary tool.
The observability-stack requirement ('experience with at least two') names Prometheus/Grafana, New Relic, Splunk, CloudWatch, and ELK as examples; these are captured as alternatives under a single skill since the requirement is for breadth across stacks, not all of them.
OpenTelemetry appears only in the Responsibilities section ('where applicable'), not in Qualifications, so it is marked preferred.
Data stores (Postgres, MongoDB, DynamoDB) appear under Qualifications as 'familiarity with … and how they fail', framed as contextual knowledge rather than a hard gate; marked preferred accordingly.
The role is hybrid (Mon–Thu in office, Fri remote), not fully remote.
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.