remote

Salary
$260,000–$280,000from the description
Posted
Jul 15, 2026
Location
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

A leadership role focused on building a Site Reliability Engineering function from the ground up at a cybersecurity company. The hire will recruit and manage a team of four to six engineers, establish incident management processes, define SLOs, and drive observability and reliability practices across engineering. It suits an experienced SRE who has previously led or built similar functions and is comfortable being hands-on during the team's early growth.

Senior level · Remote · Full-time

Must have (7)
SREobservabilitySLO/SLA definitionPagerDuty or FirehydrantAWS, GCP or Azureon-call programspostmortems

“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

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 (8)

This is a people-management role (Engineering Manager / Head of SRE) responsible for building a team from scratch, hiring, mentoring, and owning a roadmap — 11-3021 is the clear primary SOC. The alt SOC 15-1244 reflects the hands-on SRE/infrastructure component the JD explicitly requires ('comfortable being hands-on').

The title carries no explicit seniority level word; the title states no level. The scope (building a function, managing 4–6 direct reports, engaging with senior leadership) is consistent with a Senior manager band.

AWS is listed as preferred over GCP/Azure, but all three appear under the hard-requirements block ('strong working knowledge of at least one major cloud provider'), so the capability is a hard gate with AWS as the preferred option.

PagerDuty and FireHydrant are cited as illustrative examples ('e.g.') of incident management tooling under the requirements section; they are treated as interchangeable named options for the same hard-gate requirement.

'Observability' here encompasses application performance management, logs, traces, and golden signals/metrics as described in the requirements block — no single named tool is mandated.

Equity (stock options) is offered in addition to the stated base salary range.

Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): incident management.

Caller marked this a fully-remote role — scored against the national candidate pool.

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.

Apply

Apply on employer site ↗