Senior Site Reliability Engineer, Talkiatry

• 7+ years in software or infrastructure engineering, with substantial hands-on SRE or production reliability experience
• A track record of reducing incidents and improving detection—the outcomes this role is judged on
• Hands-on experience defining SLOs/SLIs and using error budgets to guide engineering decisions
• Deep observability expertise across metrics, logging, tracing, and alerting (e.g., Datadog, Prometheus, Grafana, or similar)
• Strong experience operating production systems on AWS
• Proficiency with infrastructure-as-code (e.g., Terraform) and comfort building automation and tooling (Python, TypeScript, or similar)
• Excellent communication skills, with the ability to influence and align teams you don't directly manage

Desirable

• We're hiring our first Site Reliability Engineer to join the central DevOps team and bring SRE principles to Talkiatry's engineering organization
• Across our six product teams, you'll be the person who defines what reliability means here and builds the practices, tooling, and culture to deliver it
• Reliability is foundational to safe, dependable patient care, and this role exists to make it a first-class part of how we build
• This is a high-leverage, founding role
• You won't inherit an SRE playbook—you'll write it
• Importantly, our product teams will continue to own on-call for their own services; you're not the pager
• Instead, you'll partner with engineers across patient-facing and platform teams to establish SLOs, sharpen observability, reduce toil, and shift incident detection from "a stakeholder told us" to "our monitoring caught it first"
• You'll act as a force multiplier, making reliability a shared responsibility rather than a separate function, and you'll measure your impact in fewer outages and calmer, quieter on-call rotations for the teams you support
• How Success Is Measured:
• This role is ultimately evaluated on its ability to minimize outages, specifically by:
• Reducing the frequency of production outages across the organization over time
• Increasing the share of production incidents that our monitoring and alerting catch first—before they're reported by stakeholders or end users
• Define and roll out an SRE practice for a six-team organization: SLOs/SLIs, error budgets, and reliability standards that teams genuinely adopt
• Build and improve observability—metrics, logging, distributed tracing, dashboards, and alerting—so that more incidents are detected by monitoring before anyone outside engineering notices
• Drive down outage frequency by surfacing systemic reliability risks and partnering with teams to remediate them at the root
• Reduce toil through automation, infrastructure-as-code, and self-service tooling that teams can own and extend themselves
• Own the health and usability of our observability tooling, providing documentation and training where necessary
• Run production readiness reviews for new services and partner with engineering leadership on reliability priorities and capacity planning