QA Engineer

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 bug you don't catch reaches a patient

Most QA jobs, the worst case is an angry customer and a hotfix on Friday night. Here it's a prescription that doesn't reach someone who needs it.

Foundation Health is building AI-native pharmacy infrastructure — the layer that sits between prescribers, health systems and pharmacies and makes the whole thing actually work. It plugs directly into EHRs. It's live with enterprise customers today. We're Series A and scaling the team that runs it.

That stakes-are-real thing is either the reason you'd take this job or the reason you wouldn't. Worth knowing which one you are early.

The Role

You're the person who decides whether something is safe to put in front of a Pharmacist.

Two things have to be true about you.

The fundamentals are genuinely solid. Regression testing, UAT you can own end to end with external healthcare clients, documentation someone else can actually pick up, and the instinct to know when a script won't catch it and you need to sit down and click through the thing yourself. Manual testing isn't the junior half of this job. Some of the worst bugs we've caught were found by someone being suspicious, not by a green pipeline.

And you're pushing into the new stuff. Testing AI features where the same input doesn't give you the same output twice. Using AI tooling to multiply your own output rather than as a party trick. Playwright MCP and agentic workflows — early enough that you're working it out rather than reading about it.

What "builder" actually means here

We're not handing you a framework to maintain.

You'll be writing tooling that doesn't exist yet: test data generators for clinical scenarios, harnesses for evaluating non-deterministic LLM output, MCP servers wired into our own stack, internal agents that handle the parts of the job you'd rather not do twice.

The best QA engineers we've met write code other people end up depending on. If your instinct when something's tedious is to build the thing that kills it, this fits. If you'd rather be handed a test plan, it won't.

The stack

Node.js, TypeScript, SvelteKit, GCP. Serverless, modern, no decade-old test suite anyone's frightened of.

Playwright for front-end automation, Postman for the API and integration layer, Playwright MCP and agents for the new territory — on real production features, not a sandbox.

Who you'd work with

You'll report into our VP of Engineering, ex-DeepMind/Google, who is closer to the code than most VPs you'll have worked for. You'll sit alongside our QA Lead, working daily with the engineers shipping the features — not through a ticket queue.

Small team, so your fingerprints are visible. That cuts both ways and you should want that.

What we're looking for

• 3+ years in QA or software testing, with real depth on web apps and APIs

• Strong Playwright skills and good judgement about when to automate versus when to test by hand

• Solid manual and UAT experience, including running UAT with external clients or providers

• Enterprise product experience — you know what's at stake when something breaks

• Already using AI tools day-to-day, or direct experience testing AI-powered products

• Strong technical foundation: a CS or numerate degree from a good school, or a promotion track that speaks for itself

• Healthcare, health-tech or pharmacy experience is a real plus. HIPAA, PHI handling, clinical data accuracy — if you know that world, lead with it

The setup

Remote-first across the US. However, we do prefer East Coast, and it's a practical reason rather than a preference we've invented: a big part of engineering sits in the UK, so you’d need a real working overlap with them. Further west and you're picking up their work the next morning instead of the same afternoon.

Orlando is our US hub. If you're there or open to relocating, great — we'll help make it work. If you're not, that's genuinely fine.

We do get everyone together properly, and we'd want you at those.