Tandem Health · posted · checked
Lead Software Engineer – Internal Tooling
On-site · StockholmStaff+
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 enjoy building software that helps colleagues get their work done. You’re comfortable going from a conversation about a broken process to the code behind a better one, and helping other engineers do the same.
At Tandem, you’ll lead the development of internal products used across the company. You’ll work closely with stakeholders to understand their workflows and agree priorities that support Tandem’s wider goals.
We’re building a small team, so this is a hands-on technical leadership role. You’ll build applications, integrations, and workflow automation, and follow through as colleagues start using them. You’ll also help recruit engineers and support them as they take ownership.
WHAT YOU WILL DO
Develop the internal tooling roadmap with stakeholders and engineering leadership, aligning priorities with company initiatives.
Work directly with stakeholders to understand where their workflows break down and decide where custom software, existing tools, or a process change will help most.
Build and maintain internal applications, admin interfaces, APIs, and automations that reduce manual work and help colleagues make decisions.
Connect our systems with third-party software, keeping data consistent and making failed or incomplete updates visible and recoverable.
Work with business owners to clarify rules, exceptions, and permissions, and agree which parts of a workflow our products should support.
Set practical engineering standards for the tools we build, including usable interfaces, access controls, validation, audit trails, testing, and careful rollout.