FREE ACCESS
5,000–10,000 jobs/day
See all jobs on Scoutfield
Search thousands of fresh jobs every day.
Discover
- Fresh listings
- Fast filters
- No subscription required
Create a free account and start exploring right away.

Site Reliability Engineering Lead
Quavo Fraud & Disputes. Establish and refine the SRE operating model with Product, Infrastructure, and Support .
Core Competencies
Role fitCore Competencies
Use this summary to align your resume positioning with the role.
Demonstrates expertise in Site Reliability Engineering (SRE) principles, including service-level indicators and objectives, incident response, and automation. Proficient in monitoring and alerting tools such as Datadog and Amazon CloudWatch, with a strong focus on operational excellence in SaaS environments.
Highest-signal resume keywords
Site Reliability Engineering (SRE)Monitoring Experience with DatadogIncident Response LeadershipAutomation with PythonAWS and Distributed Architectures
ATS Keywords
Tailor your resumeApplicant Tracking System Keywords
Tip: use these terms in your resume and cover letter to boost ATS matches.
Hard Skills
SaaS OperationsProduction SupportTroubleshootingRunbooksError BudgetsService-Level IndicatorsCapacity ReviewsRoot Cause AnalysisBlameless Post-Incident ReviewMonitoring Coverage
Soft Skills
Strong CommunicationJudgmentMentoringTeam CoordinationInfluencing Senior Leaders
Tools & Technologies
DatadogAmazon CloudWatchPagerDutySnowflakeUptime.comKubernetesEKSAPIsPowerShellBash
Industry Keywords
ObservabilityProduction Readiness ReviewsMonitoring OwnershipIncident CommandComplex Workflows
Tech Stack
Tools & technologiesAWSCloudKubernetesPythonSnowflake
About the role
Key responsibilities & impact- Establish and refine the SRE operating model with Product, Infrastructure, and Support
- Define alert lifecycle, severity, and response targets
- Own detection end to end, including monitoring scope, alert thresholds and content, and signal quality
- Tune or retire noisy monitors and maintain monitoring coverage 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, 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
- Report to the VP of Engineering and connect Product, Infrastructure, and Support
Requirements
What you’ll need- 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
- 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, including dashboards, synthetic tests, alerting, and PagerDuty
- Ability to establish ownership and routing across teams and influence senior leaders 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
- Preferred: experience defining and operating SLIs, SLOs, or error budgets in production
- Preferred: Kubernetes/EKS and containerized application operations
- Preferred: experience monitoring complex workflows, integrations, or data pipelines, including Snowflake
- Preferred: experience establishing an SRE or monitoring-ownership function where none existed