Product Engineer

About Supa Health

You ve probably been to a therapist, or know someone who has. You also probably know that paying for one is broken in ways most things in 2026 aren t. They  think  they take your insurance. The benefits summary you call to verify turns out to be wrong. Six weeks later, a bill arrives for an amount nobody warned you about.

Behind every one of those moments is a clinic doing the work by hand. Armies of people make eligibility calls, fax prior auths, type claims into payer portals one at a time, and chase denials months after the visit. Good clinicians leave the field over it.

Supa Health is building the agentic operating system that makes this work disappear — an AI scribe, an AI receptionist, and an agentic back office that handles benefits verification, prior auth, intake, and claims. Every call its agents make, every denial they work, every payer quirk they encounter feeds back into a system that gets sharper the next time. We re building software that compounds.

We re not selling dashboards. We re replacing the work itself.

Small team, $5M from Peak XV (formerly Sequoia India), shipping fast. Looking for our founding product engineer.

The honest answer is: whatever moves the product furthest. We have surface area in every direction and we d rather you pick the one that fits you than wedge you into a slot.

That could mean:

• Operator-facing surfaces. Real-time, dense, information-rich SPAs where our back-office team works through hundreds of cases a day. The interaction model matters as much as the engineering — operators live in these tools eight hours a day, and small wins compound into hours saved. Modern React stack, Type Script end-to-end, real-time over Web Sockets.

• The agent platform. The systems that let our agents do real work in the world — making calls, navigating systems built before APIs existed, parsing structured and unstructured payer responses, and writing back into our own state. Workflows for orchestration, Postgres as the source of truth, LLMs invoked deliberately rather than reflexively.

• The platform underneath both. Schema, services, auth, multi-tenancy, integrations, and the HIPAA-grade segregation that has to be right on day one. Postgres, Drizzle, Fastify, an Nx monorepo, WorkOS for auth.

• The next product wedge. We have a roadmap. We also have customers asking for things that aren t on it. Founding engineers at Supa Health get to argue for what we should build next, and then build it.

You ll talk to operators. You ll talk to clinic owners. You ll watch someone do their job for two hours and then go automate the painful parts of it. You ll ship something on Tuesday and see it running in production on Wednesday.

• Craft. You ve shipped real software to real users for years and it shows in how you think. You have opinions about schema design, about when to reach for a state machine, about what makes a UI feel fast. You can tell the difference between extra effort and meaningful quality, and you reach for the second one. Your code reviews make the people around you better — not because you re harsh, but because you re specific, and the team s standards rise around you.

• Judgment. Healthcare is full of edge cases that look like bugs and bugs that look like edge cases. The CTO can t be in every decision and we don t want to use process as a substitute for thinking. We want people who can reason through a tradeoff with incomplete information and make the call.

• Ownership. You don t wait for work to be handed to you. You see what s broken, what s slow, what s missing — and you write the doc, file the issue, or open the PR. You take a problem from  I noticed this  to  it s deployed and working,  which means talking to the user, designing the solution, writing the code, watching it land, and going back to fix what you got wrong.

• Direction. You work with users and teammates to figure out what to build and how to build it. You sit with operators, watch where they get stuck, and come back with a sharper definition of the problem than we started with. You re a thought partner to the team — not someone waiting for a spec, and not someone going off…