Senior Site Reliability Engineer

Novellia is a health tech startup providing access to personal health data for patients in the U.S. They are seeking a Senior Site Reliability Engineer to establish the reliability foundations for their platform. The role involves designing reliability processes, shaping the platform roadmap, and contributing to compliance and security for health data.

Responsibilities:

• Design the human side of reliability: on-call rotations, incident roles and communication, blameless postmortems, and change management that adds safety without adding drag
• Help shape the platform roadmap: bring us the problems you're seeing, propose solutions, and own them through to adoption
• Build and operate the core reliability toolkit: observability (metrics, logging, tracing, alerting), CI/CD, infrastructure as code, and incident response
• Embed with product engineers to make services more operable, and to raise the operational literacy of the whole team rather than becoming its single point of failure
• Define our first SLOs in partnership with product and engineering stakeholders, grounded in what actually matters to patients and customers rather than what's easy to measure
• Investigate incidents and recurring pain end to end, and be equally willing to conclude "this needs a process change" as "this needs a code change."
• Contribute to the compliance and security posture that health data demands (audit trails, access controls, environment isolation), working alongside the Head of Platform Engineering. Reliability here is also about patient trust: people share their health history with us because we're transparent about how it's handled, and the systems you keep running are what make that promise real

Requirements:

• 5+ years in SRE, platform, DevOps, or backend roles with meaningful production ownership: you've carried a pager, owned services through real incidents, and made systems measurably better afterward
• Comfortable in at least one general-purpose language (Python, Go, TypeScript, or similar), and willing to go into application code and change it when that's where the fix lives. This isn't about cleaning up someone else's work; it's about having skin in the game and being ready to lean in when a problem calls for it
• A track record of solving problems, not just closing tickets. You can walk us through real problems you identified, how you decided what to do, and what changed as a result
• Evidence you treat process as a legitimate engineering tool: you've improved a review workflow, restructured an on-call, introduced a postmortem practice, or otherwise fixed something by changing how people work
• Strong collaboration instincts: you seek out the people affected by a problem, listen well, write clearly, and bring stakeholders along rather than presenting them with a finished decision
• Self-directed and used to operating without a playbook. You'll get problems and a close working partner, not a queue of tasks, and you're comfortable setting direction others will build on
• Experience in a regulated environment (healthcare, fintech) or working with HIPAA, SOC 2, or similar frameworks
• You've been an early or first infrastructure/reliability hire and know what greenfield ownership actually feels like day to day
• Experience introducing reliability practices to teams that didn't have them