Staff Software Engineer, AI-Native Systems
We are
Virtual care only works if the infrastructure behind it does. […] builds that infrastructure: the systems that let telehealth run at scale for the patients, clinicians, and companies that depend on it. We're not bolting AI onto old workflows; we're rebuilding how care gets delivered, with AI in the product and in how we build it.
We do this in a live, regulated healthcare environment where getting it right matters. This is the next architecture of virtual care, and we're building it now.
You are
A staff-level engineer who has built software in a regulated, high-stakes domain (ideally health tech; fintech and insurtech count too) and knows what that demands: sensitive data, regulatory constraints, and the cost of getting it wrong. You've designed and shipped AI and agentic systems in production, you know where they break, and you have opinions, held loosely and argued well, about building them safely.
You're a builder first, and you've done real work in small, scrappy teams. You still write the hard parts of the code yourself, and you've done it recently. You don't need a platform org, TPMs, or layers of review to move.
You operate as a domain owner, not a task owner. You take a problem that isn't well-formed, define it, tie it to what the business has committed to, and lead a group of engineers to a shipped, measured outcome. Your impact shows up in other people's work: the patterns they reus