T

Twilio

Runs the texts and calls behind business apps

Staff Site Reliability Engineer

Site Reliability EngineeringUpdated on Nov 10
Full-timeRemote in IrelandNo salary listed

About the Job

Requirements

  • At least 8 years of related engineering experience, with a substantial portion focused on reliability, infrastructure, or platform engineering.
  • Demonstrated accountability for production systems, including carrying a pager for important services and owning outcomes when they fail.
  • Strong software engineering fundamentals, including building and shipping production code rather than only configuring tooling.
  • Experience defining and operating against service-level indicators (SLIs) and service-level objectives (SLOs), and using error budgets to inform engineering priorities.
  • Depth in production operations, including incident command, post-mortem analysis, capacity planning, and observability.
  • A record of preventing incident recurrence by reducing incident classes and operational toil, rather than only closing tickets.
  • Experience driving changes across multiple teams and building alignment without formal authority.
  • A track record of improving engineers through code review, design feedback, and mentorship.
  • Experience with large-scale distributed systems in a cloud environment.

Responsibilities

  • Own the reliability posture of production services in the assigned area, including availability, latency, capacity, efficiency, performance, monitoring, and alerting.
  • Define, instrument, and operate against SLIs and SLOs, using error budgets to drive engineering priorities.
  • Identify trends and problem areas that threaten stability, and develop a path to mitigate risks before they reach customers.
  • Reduce repair items and prevent classes of incidents rather than resolving incidents one at a time.
  • Improve detection, response, and recovery by reducing time to acknowledge, engage, mitigate, and restore, while involving fewer people.
  • Design for failure by strengthening failure domains, validating recovery paths, and making production changes safer to ship and roll back.
  • Participate in on-call for supported services and lead responses when production is degraded.
  • Write post-mortems that identify root causes and drive follow-up work to completion.
  • Oversee identification, diagnosis, reporting, and documentation of production problems across reliability dimensions.
  • Write, configure, and deploy maintainable, reviewed, documented, and well-tested code that measurably improves service reliability.
  • Orchestrate complex changes across systems and services, documenting design changes, technical decisions, migration plans, and upgrades.
  • Lead debugging, troubleshooting, and analysis of service architecture and design.
  • Use code review to improve coworkers' code quality.
  • Reduce the operational overhead required to run infrastructure and services.
  • Drive projects from conception to completion for efforts spanning the team's concerns.
  • Coordinate across programs, collaborate with others to estimate and communicate delivery timelines, break projects into milestones and tasks, track progress, and update stakeholders.
  • Identify and communicate changes that may affect stability.

Desired Qualifications

  • Familiarity with infrastructure-as-code, container orchestration, and GitOps-style delivery.
  • Experience with multi-region architecture, failure-domain design, or regional expansion work.
  • Background in chaos engineering, game days, or other proactive resilience validation.

About the Company

Twilio

Runs the texts and calls behind business apps

Twilio builds cloud software that lets businesses add text messages, phone calls, email, and identity checks to their own apps and websites through code their developers write. In 2011, Uber moved its rider texts to Twilio, which later let the ride app expand abroad without signing deals with each country's phone carriers. Developers call Twilio's programming interfaces to send texts and WhatsApp messages, run calls that people or AI voice agents answer, send email through its SendGrid service, and confirm logins with one-time codes. Customers pay mostly per message, call minute, or check, plus subscriptions for email. Twilio was founded in 2008 and is based in San Francisco.

Company size
5,001-10,000
Company stage
IPO
Headquarters
San Francisco, CA
Founded
2008

Recently Posted Jobs

Explore more opportunities at Twilio

See more jobs