Site Reliability Engineering Lead
About The Position
The Site Reliability Engineering Team Lead owns application monitoring at Quavo, including what is detected, how alerts are routed, and the quality of monitoring signals. The role establishes accountability for monitoring that has previously been assigned based on where incidents began, resulting in coverage lapses or duplication. Reporting to the VP of Engineering, the role connects Product, Infrastructure, and Support through clear alert routing and agreed severity standards, and can assign remediation to the owning group. The goal is to detect issues before clients report them and ensure every alert has an owner before it fires. The role establishes and refines the SRE operating model, owns detection and the monitoring and paging stack, and applies software engineering to reduce operational toil. It also runs production readiness reviews and release coordination, and builds the team over time while introducing SLOs, incident command, and capacity reviews as signal quality and capacity allow.
Requirements
- 5–10 years of experience in SaaS, application operations, production support, SRE, or observability.
- Experience leading, mentoring, or coordinating a production operation, application support, SRE, observability, or monitoring team.
- Hands-on experience running customer-facing SaaS in production and troubleshooting across applications, platforms, integration, data, and cloud layers, with working knowledge of AWS and distributed architectures.
- Working knowledge of SRE principles, including service-level indicators and objectives, error budgets, toil reduction, and blameless post-incident reviews.
- Strong monitoring experience with Datadog, Amazon CloudWatch, or similar tools such as Prometheus, Grafana, or OpenTelemetry, including dashboards, synthetic tests, alerting, and PagerDuty.
- Ability to establish ownership and routing across teams without owning their work, and to influence senior leaders, including through escalation, with strong communication and judgment.
- Experience leading incident response, root cause analysis, runbooks, and corrective actions.
- Ability to automate diagnostics, monitoring, or remediation with Python, PowerShell, Bash, APIs, or similar tools as sustained engineering work rather than one-off scripts.
Nice To Haves
- Experience defining and operating SLIs, SLOs, or error budgets in production.
- Kubernetes/EKS and containerized application operations.
- Experience monitoring complex workflows, integrations, or data pipelines, including Snowflake.
- Experience establishing an SRE or monitoring-ownership function where none existed.
Responsibilities
- Establish and refine the SRE operating model with Product, Infrastructure, and Support, including the alert lifecycle and severity and response targets.
- Own detection end to end, including what is monitored, alert thresholds and content, and signal quality; tune or retire noisy monitors and ensure coverage remains current after incidents close.
- Route every alert to its owning group through PagerDuty; triage alerts without a mapped owner, assign remediation work, and verify closure.
- Own the monitoring and paging stack, including Datadog, Amazon CloudWatch, Snowflake-based alerting, Uptime.com, and PagerDuty.
- Apply software engineering to reduce toil through runbooks and automation.
- Run production readiness reviews and release coordination.
- Build the team over time and introduce SLOs, incident command, and capacity reviews as signal quality and capacity allow.
Stand Out From the Crowd
Upload your resume and get instant feedback on how well it matches this job.
What This Job Offers
Job Type
Full-time
Career Level
Senior
Education Level
No Education Listed
