QA Lead

About the company

Heidi Health builds AI-powered medical scribe and care-partner software that removes administrative burdens from clinicians.

About this role

We’re Heidi. We're building the future of healthcare by giving every clinician the earth's finest AI Care Partner. In just 18 months, our clinical AI products have absorbed the administrative chaos of 73 million patient visits. Today, we support over 2.5 million patient sessions a week across 190+ countries. Healthcare systems are failing us; clinicians spend more time on documentation than on patients, and the human connection that makes medicine worth practicing is eroding. Our mission is simple: double the world’s healthcare capacity and strengthen the human connection at its heart. We found product-market fit with a freemium medical scribe that clinicians love. Now, we're expanding. Every task a clinician hands to Heidi is a patient who feels more attended to, a health system unclogged, and a clinician who gets to be a clinician again. If you don’t choose easy and you want to build something way bigger than yourself then, choose the challenge, choose Heidi. About the Role We ship atoms daily. Two million patient visits a week run through what we ship, and a clinician mid-shift has no appetite for our bugs. This role owns quality at Heidi. Not as a gate at the end, but as the thing that lets every engineer here ship fast and be right. You'll decide what good testing looks like across our stack, build the frameworks and infrastructure that make writing a good test the easy path, and make deploying to production a boring, verifiable event rather than an act of faith. You'll lead the QA function and stay in the code while you do it. Release management sits inside this role, because the person who understands the risk should be the person who decides it's safe What You’ll Do   - Own the testing strategy across Heidi's stack, from web and mobile to our AI pipelines and EHR-connected enterprise deployments, and make deliberate calls about what belongs in unit tests, what needs integration coverage, what only a real end-to-end run will catch and what we're better off detecting in production. - Choose and build the frameworks. You'll select the tooling, write the harnesses and fixtures, and get our test suites to the point where engineers reach for them because they're fast and reliable rather than because a policy says so. - Make deployment safe by design. Quality gates in CI/CD, staged rollouts, canaries, feature flags and rollback paths that get exercised before anyone needs them, so a bad change is caught by the pipeline instead of by a clinic. - Raise the testing bar across the engineering team through code review, pairing and documentation, so quality is something every engineer owns rather than something they hand to you. - Own the quality signal end to end: escaped defect rate, change failure rate and time to detect, alongside the DORA metrics we already run on. You'll be the person who can say what our real quality is, with evidence. - Run release readiness and go/no-go, weighing coverage, change size, dependency risk and prior incidents alongside engineering leads, and own the release cadence so teams ship predictably and health system customers know what's coming. - Work with our internal compliance team on medical device requirements, so our test evidence and release records hold up to clinical safety and regulatory review without slowing the team down. What We’re Looking For   - Deep QA or test engineering experience at a fast-moving SaaS company, including ownership of a quality function or a team. A regulated environment (healthcare, fintech, clinical technology) is a strong plus. - You write code. Python, TypeScript, Java or similar, with real fluency in modern automation frameworks (Playwright, Cypress, Selenium, Appium, pytest, Jest) and a track record of building test infrastructure from nothing. - Strong grasp of API and contract testing, mobile testing, performance testing, and how to make a flaky suite reliable rather than muted. - Working knowledge of CI/CD, observability tools, source control workflows, feature flagging and modern deployment patterns. You can read a pipeline, question a risk assessment and tell a sound rollback plan from a hopeful one. - Experience owning releases, not just testing them: cadence, go/no-go, coordination and the comms that go with it. - Comfort with data. You track quality signals, spot the bottleneck in the numbers and bring evidence to the go/no-go table. - A bias for velocity paired with the discipline enterprise healthcare demands. Process should make shipping faster, and you cut it when it doesn't. Other Things to Know - This role is hybrid in Sydney or Melbourne. We believe in the energy and focus of being in the room together. - You'll work across a significant timezone gap with our teams in the US, UK and Europe. - You'll work closely with the Head of Engineering, and other engineering leaders and have real influence over how Heidi ships globally. How we show up - Build for the next decade, not next quarter. Our targets are outrageous on purpose. The world's health doesn't have the luxury of incrementalism. - Lead, don't wait. We treat tomorrow's problems today. Sometimes we build what's needed before it's wanted, and we're fine with that. - Follow the evidence. Trust the patient. We pursue truth relentlessly. But when the subjective and objective disagree, we treat the patient, not the numbers. Ego is a comorbidity we can't afford. - Own the outcome. Everyone here carries the company. Raise problems with solutions, solve them end-to-end, and never be a bystander. - Ship, measure, go again. A button today, a workflow tomorrow. More iterations beat better planning. We're precise at pace, not reckless. - Live in clinicians' reality. Not the ideal workflow, the twenty-patients-before-lunch actual one. We build for exhausted humans, and we'd better be decent ones while we do it. Why Heidi? You’ll join a team focused on real-world impact over