Tandem Health · posted · checked
Site Reliability Engineer
On-site · Stockholm
Who can apply
On-site · Stockholm
Location: Stockholm
BUILD SOMETHING MONUMENTAL FOR HEALTHCARE!
At Tandem Health we’re reimagining healthcare by putting clinicians first. Our platform - designed by clinicians, for clinicians - is built on deep insight into real-world pain points, with intuitive medical notes and workflows that truly support patient care.
We’re a fast-scaling health-tech company backed by top investors and expanding globally. We move fast, stay curious, and believe building something that matters starts with an extraordinary team. If you're passionate about impact and innovation, we'd love to meet you!
ABOUT THE ROLE
You like understanding how software behaves in production. When a service is slow or a failure keeps coming back, you want to trace the cause, change the system, and check that the fix holds up.
At Tandem, you’ll improve the reliability of the services clinicians use every day. You’ll write code, build tests and tooling, and work with service owners to make failures easier to find and recover from. Your work will cover how services behave under load, how they handle problems in their dependencies, and what engineers can see when something goes wrong.
You might investigate a slow workflow, build a realistic load test, or change an alert that keeps paging without giving anyone useful information. You’ll take improvements from investigation through implementation and production, working alongside product, platform, and infrastructure engineers.
WHAT YOU WILL DO
Investigate failures and performance problems across services, queues, databases, and external dependencies, then implement fixes with the teams that own them.
Improve metrics, logs, and tracing so engineers can understand what users experience and locate the cause of a problem.
Build dashboards and actionable alerts around service objectives, and tune alerts that create noise without helping responders.
Write load and recovery tests to find capacity limits and check how services behave when dependencies slow down or fail.
Automate recurring operational tasks and improve runbooks so response relies less on manual steps or individual knowledge.
Take part in incident response with service owners, and follow through on fixes and tests that prevent repeat failures.