Lead Site Reliability Engineer - Imunify Reliability Platform (remote work)

Responsibilities

• 1. Define what "working" means for ~70 components
• Run SLI definition with squad leads and senior engineers. You facilitate and hold the standard; the owning squad signs the SLI.
• Build the taxonomy this product actually needs, which is broader than availability and latency
• Service SLIs — availability, latency, error rate for cloud-side services.
• Fleet SLIs — heartbeat reachability, version and configuration convergence across the installed base.
• Control-efficacy SLIs — the differentiator. What fraction of protected units have the control effectively enabled and current , not merely installed. Ruleset generation drift, signature age, scan coverage, enforcement-mode distribution.
• Delivery SLIs — artifact publish success, rule-to-fleet lead time, hotfix time-to-convergence.
• Pipeline SLIs — ingest lag, verdict latency, queue age, backlog burn.
• Enforce one non-negotiable design rule: an SLI must be measurable from outside the gate of the thing it measures. If the control being off also switches off the signal that would tell you it is off, the SLI is invalid. This is the lesson of the incident above and it is the reason this role exists.
• Attach an SLO, an error budget and an owning squad to each. Tiering is expected — not every component earns a 99.9% target or a pager.

Languages