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 easy: 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.

The role

A clinician mid-visit does not care which region an availability zone sits in. They care that Heidi is there when they press record, and that the note is waiting when they finish. Two million patient visits a week now depend on that being true.

This role leads the team that makes it true. You'll own Heidi's cloud platform and our reliability practice as one function: the infrastructure everything runs on, the SLOs we hold ourselves to, the on-call rotation that answers when they slip, and the tooling that lets every engineer at Heidi ship without filing a ticket. You'll lead a small team of cloud and reliability engineers, and you'll still be close enough to the systems to be useful at 3am.

What you’ll do





- Lead and grow the foundations team covering build, deploy, frontend platform and backend platform. Set direction, run hiring, coach engineers through hard technical calls and keep the team's work legible to the product teams it serves.

- Own the path from commit to production: build times, test reliability, preview environments, feature flags, canary and staged rollouts and rollback paths that get exercised before they're needed. Move deployment frequency and change lead time without moving change failure rate.

- Set the frontend foundations. The component library and design system implementation, app shell and routing, state and data-fetching patterns, plus bundle size and client performance budgets that hold as the surface area grows.

- Set the backend foundations. Service scaffolding, shared libraries, API and schema conventions, data access patterns, background jobs and the test infrastructure underneath all of it. Make the standard path the fast one so teams stop inventing their own.

- Kill the flaky test, the 40-minute CI run and the deploy that needs a human babysitter. Treat developer experience as a product with real users, a roadmap and metrics you report on honestly.

- Partner with the Release Manager, the cloud and reliability team and engineering leads across product.



Foundations only land when the teams building on them helped make the call.

What you'll need

- Significant experience owning developer platform, build and release, or core frontend and backend infrastructure, including time leading engineers. A regulated environment (healthcare, fintech, clinical technology) is a strong plus.

- Deep, current, hands-on skill on both sides of the stack: modern TypeScript and React, a major backend language and framework, and the CI/CD tooling, monorepo and build systems that hold them together.

- A record of making other engineers faster, with numbers behind it. CI times cut, flake rates driven down, release frequency raised, onboarding shortened.

- Judgment about migrations. You've moved a large codebase onto a new framework, build system or API pattern incrementally, without a two-quarter freeze and without leaving it half-finished.

- A service mindset toward product engineers. You measure the platform by whether it makes other teams faster, not by how elegant it is.

- Comfort with the guardrails that come with clinical data: change control, audit trails and code review standards that hold up under a customer security review.

Other things to note

- This role is in-office in Sydney or Melbourne. We believe in the energy and focus of being in the room together.

- You'll be in the on-call rotation you design. Leaders here carry the pager.

- You'll work closely with the Head of Engineering, Security and product engineering leads, with real influence over how Heidi runs 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 th

📌 Engineering Lead (Melbourne)
🏢 Alt
📍 Melbourne