Senior Software Engineer, SRE

What you ll be doing:

• Design & Infrastructure
  • Contribute to postmortem culture by facilitating comprehensive, blameless post-incident reviews that identify root causes, contributing factors, and actionable remediation items. Track incident trends to identify systemic issues and prioritize reliability improvements.
  • Implement chaos engineering practices to proactively identify failure modes, validate system resilience, and build confidence in recovery procedures. Conduct game days and disaster recovery exercises.
• SRE Process & Principles Implementation
  • Deploy and evolve SRE practices across the organization by establishing core SRE principles, frameworks, and methodologies. Define and implement service reliability practices, including Service Level Objectives (SLOs), Service Level Indicators (SLIs), and Error Budgets, to balance innovation velocity with system reliability.
  • Manage Error Budgets as a mechanism for making data-driven decisions about feature velocity vs. reliability. Track, report, and enforce error budget policies, facilitating conversations between engineering and product teams about risk tolerance and release decisions.
• Reliability Engineering & Infrastructure
  • Reduce toil through automation by identifying repetitive operational work and systematically eliminating it through infrastructure-as-code, automation frameworks, and intelligent tooling. Measure and track toil reduction efforts, aiming to keep toil below 50% of team time.
  • Implement capacity planning processes that ensure systems have adequate headroom to meet SLOs during peak traffic, unexpected load spikes, and degraded states. Develop predictive models and automated scaling mechanisms.
• Observability, Monitoring & Reporting
  • Build comprehensive observability systems that provide deep visibility into service health, performance, and user experience. Implement monitoring strategies based on the Four Golden Signals (latency, traffic, errors, saturation) and USE/RED methodologies.
  • Create SRE dashboards and reporting mechanisms that provide real-time visibility into SLO compliance, error budget consumption, and system reliability metrics. Develop executive-level reporting on reliability trends, incident impact, and improvement initiatives.
  • Establish alerting strategies that are actionable, symptom-based, and aligned with SLOs. Reduce alert fatigue by tuning thresholds and eliminating noise while ensuring critical issues trigger appropriate responses.
• Collaboration and Leadership
  • Partner with development teams to implement reliability from the design phase using SRE principles. Conduct design reviews focused on failure modes, scalability, observability, and operational concerns. Guide teams in building services that meet SLO requirements.
  • Collaborate through code reviews and design reviews, ensuring infrastructure-as-code, automation scripts, and reliability improvements follow best practices, are well-documented, and maintain high-quality standards.
  • Manage project priorities using error budgets as a decision-making framework. Leverage agile methodologies while ensuring reliability work gets appropriate prioritization alongside feature development.
• Operational Excellence & Continuous Improvement
  • Identify and eliminate performance bottlenecks through detailed analysis of metrics, traces, and profiles. Optimize system resources, tune configurations, and implement auto-scaling to ensure SLO compliance during varying load conditions.
  • Drive continuous improvement through SRE feedback loops by analyzing SLO violations, incident trends, and toil metrics to identify systemic improvements. Champion the reliability roadmap and advocate for technical debt reduction.
  • Maintain a culture of documentation and knowledge sharing by creating comprehensive runbooks, operational guides, system architecture documentation, and disaster recovery procedures. Ensure operational knowledge is distributed across the team.
  • Track and report on SRE metrics, including SLO compliance rates, error budget consumption, mean time to detection (MTTD), mean time to resolution (MTTR), toil percentage, and reliability improvement velocity.
• On-call & reliability
  • Participate in a 12x7 on-call rotation and be available to work with global teams in the event of critical outages

We re excited if you have:

• Preferably 8+ years of experience in DevOps/SRE roles, with demonstrated expertise in implementing SRE pr…