[Hiring] Site Reliability Engineering Lead @Quavo Fraud & Disputes

Role Description

The Site Reliability Engineering Team Lead owns application monitoring at Quavo: what gets detected, how alerts are routed, and how good the signal is. No team has been accountable for this until now, so monitoring has been assigned by where an incident started and has lapsed or been duplicated afterward. Reporting to the VP of Engineering, the role connects Product, Infrastructure, and Support through clear routing and agreed severity standards, with authority to assign remediation to the owning group. The result is that Quavo finds issues before clients report them, and every alert has an owner before it fires.

• Establish and refine the SRE operating model with Product, Infrastructure, and Support: alert lifecycle, severity and response targets.
• Own detection end to end: what is monitored, alert thresholds and content, and signal quality. Tune or retire noisy monitors and keep coverage from lapsing after incidents close.
• Route every alert to its owning group through PagerDuty, triage alerts with no mapped owner, assign remediation work, and verify closure.
• Own the monitoring and paging stack (Datadog, Amazon CloudWatch, Snowflake-based alerting, Uptime.com, PagerDuty) and apply software engineering to reduce toil through runbooks and automation.
• Run production readiness reviews and release coordination, and build the team over time, introducing SLOs, incident command, and capacity reviews as signal quality and capacity allow.

Qualifications

• 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: service-level indicators and objectives, error budgets, toil reduction, and blameless post-incident review.
• Strong monitoring experience with Datadog, Amazon CloudWatch, or similar (Prometheus, Grafana, 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.

Preferred Qualifications

• 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.