Foundationhealthcareers Principal Software Engineer at Foundation Health owns architecture across product areas and designs scalable systems for AI in specialty pharmacy. Leads engineering practices and mentors teams to improve output and quality.
Responsibilities
This isn’t a pitch deck. Our platform is live in production inside major US health systems. Our AI handles real patient communication over voice and SMS and plugs directly into Epic workflows. If it gets something wrong, there’s no funny screenshot: a real person doesn’t get their medication. That’s the standard we build to.
You’ll own architecture across several product areas and design systems that can grow 10–100x without a rewrite. When the hardest problem in the company comes up, you’re the one who opens the editor and builds the first version.
You’ll also make the rest of engineering better. That means mentoring, leading projects across teams, and changing how we build, including how we use AI to ship faster without shipping worse. If you’ve already rolled out agentic dev practices at a team or company level and can show what happened to output and quality, we’d love to hear about it.
You’ll work directly with our VP of Engineering (ex-DeepMind) and CEO. Nobody here manages from a distance, at any level, and that includes the Principal.
The problems you’d own
Agentic AI that’s safe to put in front of patients. This covers voice and SMS agents, plus the evals, guardrails, red teaming and pharmacist-oversight design that make them trustworthy. If you’ve worked on AI safety or LLM security in production, this is where that experience pays off.
Deep EHR integration. Epic queues, prior authorization automation and 340B compliance, where correctness really matters and the specs are older than some of our engineers.
Our target-state architecture. You’ll take the platform from a handful of health systems to hundreds and build the first mile of that migration yourself.
How we do AI engineering. That includes model selection, context management, cost and latency tradeoffs, and evaluation methodology.
Who tends to do well here
You’ve built serious systems with your own hands recently, and you can go deep on the details of anything you’ve shipped. Your title doesn’t matter much. Plenty of great Principals have spent time as directors or heads of something without ever stopping building.
You’ve worked at Staff+ level somewhere with a high bar, and you can point to architectural decisions a company still runs on.