The New Bets squad builds Heidi’s next products. Scribe already powers millions of patient visits a week, and Evidence and Remote are scaling behind it. Your job, alongside the New Bets PM and Team, is to build what comes next.
This is zero-to-one engineering with a distribution advantage most early products never get. Your v1s don’t launch into silence, instead they go in front of clinicians who already open Heidi every day, and who will tell you within a week whether you have built something they need.
The squad is small on purpose. You’ll build the whole thing: the React front end, the Python services behind it, and the prompts, retrieval and eval harnesses that make an LLM feature safe enough to put in front of a clinician. When a bet needs an onboarding flow, a data migration or a quick internal dashboard, that’s you too. There’s no one else to hand it to, so you will own the build from PoC through to production.
Some of what you build will be killed. Ultimately, most bets don’t survive contact with a real clinic, and the winners graduate into staffed product lines that inherit your code. For this to work, the code that dies has to have been fast to write, and the code that lives has to be worth inheriting.
To fit in well with this team, you need to be the engineer who ships, ideally with: a few years of production software behind you, real judgment about what’s good enough for a prototype versus what has to be right, and the appetite to own more surface area than any normal role would give you. If you’re mid-level and impatient about it, this role is a fast-track to exposing yourself to complex problems and pushing towards a Senior level.