Director, Site Reliability Engineering at Vertafore
Denver, CO
$175,000–$220,000from the description
Jul 9, 2026
Denver, CO
Jul 20, 2026
What this job asks for AI summary
A senior leadership role overseeing site reliability engineering across a portfolio of SaaS insurance products. The position is responsible for defining and managing SLIs/SLOs, error budgets, incident response, and CI/CD pipelines, while leading multiple teams of managers and engineers. It suits a deeply experienced SRE or DevOps leader with a strong software engineering background and a track record managing reliability programs for large-scale distributed cloud systems.
Senior level · 15+ years · Remote · Bachelor's required · Full-time
Advertised as Principal, but the requirements read as Senior.
“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 1,450 people nationally plausibly meet what this posting asks for (computer and information systems managers). range 610–2,200
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 $178,991 (middle half $141,096–$225,584). 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 (10)
This is a people-management role (Director managing multiple Managers and Engineers), making 11-3021 the primary SOC. However, the JD places heavy emphasis on hands-on SRE/software-engineering practices (CI/CD, SLIs/SLOs, error budgets, automation), so 15-1252 is a credible runner-up.
The title 'Director' is treated as the level advertised in the title Principal (org-level leadership framing), but the actual requirements — even at 15+ years and 8+ years leadership — describe a Senior-band scope: leading a defined portfolio of products, not setting org-wide technical direction across the entire company.
GitLab and Jenkins appear together in a single illustrative list of CI/CD tools ('tools like GitLab, Jenkins, Ansible, LaunchDarkly') under a responsibilities section, not a hard-requirements block; they are marked preferred accordingly. Ansible and LaunchDarkly from the same list are similarly preferred.
F5 and ALB appear only in a cross-functional collaboration bullet (partnering with Cloud Ops on load balancing), not in the qualifications section; marked preferred.
SLI/SLO, observability, incident response, CI/CD, and AWS are all explicitly called out in the Qualifications section with firm language and are treated as hard gates.
'Container orchestration' is stated in Qualifications as 'experience with container orchestration' without naming a specific tool (e.g. Kubernetes); no alternatives are listed because the requirement is stated generically.
Background in financial services, healthcare, or regulated industries is explicitly marked Preferred in the JD; omitted from the skills list as it is a domain/background note rather than a named technology.
The role is Flexible First (remote-eligible) with a Denver HQ; remote is set to true.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): container orchestration.
This posting reads as a fully-remote role, so it was scored against the national candidate pool rather than a single metro.
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.