Job Opportunities API

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.   WHAT YOU'LL WORK ON The Staff engineer at Supa Health is the technical center of gravity for the team. You'll partner directly with the CTO and product to shape where we go and how we get there, and you'll be the person who makes sure the work actually gets there. That means: - Architecture and direction. You own the hard architectural calls — how the agent platform evolves, how data flows across surfaces, how we keep multi-tenancy and HIPAA-grade segregation honest as the system grows. You phase the work in a way that lets us ship every week, not every quarter. - The quality bar. You set what "good" looks like here. Code reviews, conventions, testing, observability, the standards we hold each other to. Not by writing a 40-page wiki nobody reads, but by example — and by being the person whose review the team most wants to get. - Project execution. You break large pieces of work into milestones, drive them to completion, and unblock the people working on them. You know when to cut scope, when to spend the extra week getting it right, and when to throw the prototype away. - Technical communication. You're the translation layer between engineering and the rest of the company. Product knows what's possible because you told them. The CTO trusts your read on technical risk. Customers get the right answer because you helped shape it. - Building, still. This is not a hands-off role. You write code, you ship, you stay close enough to the system that your judgment is grounded in what's actually there. 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.   WHAT WE LOOK FOR - Craft as a discipline. You take pride in the details — naming, structure, the difference between code that works and code that lasts. You advocate for high-quality engineering not as a luxury but as the thing that lets us move fast for years instead of months. You can articulate why a design is better, not just that it is. - Architectural judgment. You can hold the whole system in your head and make calls about where complexity should live. You know when to invest in abstraction and when to cut a straight line through. You phase migrations and rewrites so the team keeps shipping the entire time. - Code review as leverage. You review code that makes the people around you better — specific, kind, and consistently raising the bar. You see review as one of the highest-leverage things a Staff engineer does, not as a chore between meetings. - Project ownership. You take a piece of work from "we should probably do this" through milestones, scope cuts, and the unglamorous middle, all the way to shipped. Yo