À propos de ce poste Software Engineer chez Foundation Health
About Foundation Health
Foundation Health is an AI operating system for pharmacy - built by a team who lived the problem firsthand, not one that came to healthcare from the outside. Every day, prior authorizations delay prescriptions, pharmacists lose hours to paperwork instead of patients, and prescriptions slip through the cracks between health systems. We believe thoughtfully applied AI can finally change that - deep, integrated infrastructure that streamlines how care is coordinated, purpose-built for the complexity of specialty pharmacy.
We're building toward a world where pharmacy teams spend their time on patients, not paperwork - where AI handles the routine so clinicians can focus on what only humans can do. Getting there takes the right people. We're looking for curious, ambitious folks who want to help solve healthcare's hardest problems - for our patients, our partners, and each other.
The Role
This isn't a pitch deck. Our platform is live in production inside major US health systems — including Intermountain Health — where our AI handles real patient communication over voice and SMS and plugs directly into Epic workflows. We have a public partnership with Amazon Pharmacy. We raised a $20M Series A led by Define Ventures. Our CEO is a 2x founder; our VP of Engineering came from DeepMind. We're ~70 people, past PMF, with enterprise customers pulling us forward faster than we can hire.
Here's the early-career fork in the road: at a big company, you'll spend year one on internal tooling, ship through six layers of review, and learn how a large org works. Here, you'll ship to production in your first week, on systems pharmacists and patients actually depend on, sitting (virtually or in Orlando) next to engineers who've built at serious scale. Same years of your career. Very different compounding.
What you'll actually do
Ship well-scoped features and fixes independently, with proper test coverage, at a pace you'll be proud of
Work AI-native from day one — Claude, Cursor, the lot — as a first-class part of how you build, with the judgment to know when the output needs a second look
Learn the domain deeply: who the pharmacist is, what workflow they're stuck in, why your ticket exists — and ask "why" when a requirement feels off
File the bugs and UX issues you notice without waiting to be told
Level up fast through code review and pairing with engineers who've built serious systems — the feedback loop here is customers, not committees
What we're looking for
Sharp CS fundamentals and evidence you love building: side projects, internships, open source, a startup that didn't work — something you made because you couldn't not
Learning velocity. You pick things up fast and you enjoy the discomfort of not knowing yet
High agency and curiosity about the product, not just the code
Already building with AI tools, and thoughtful about their limits
Stack is Node/TypeScript/GCP. If you've not used it, that's fine — that's the point of learning velocity.
The practical stuff
We're remote-first across the US, though we've just opened a hub in Orlando if you ever wanted your comp to survive contact with your cost of living. And it's early enough that the equity is founding-role equity, not a rounding error.