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 You'll own the entire product function. That means the work you do this year will set the shape of what product looks like at Supa Health for the next five — the rituals, the documents, the way decisions get made, the way customers and engineering and operations talk to each other. Concretely: - Customers. You're the person customers know. You run the relationship from first onboarding through the long tail — what they need, what they're stuck on, what they'd build next if they could. They text you. You text back. - Operations. Our back-office team runs the agents that run the work. You sit with them, watch where they get stuck, and feed what you learn into the roadmap. The faster their feedback turns into shipped product, the faster the whole company gets. - Product direction and PRDs. You define what we're building, why, and what done looks like. You write the doc, you make the calls on scope, you defend the cuts. Engineering doesn't have to guess what you mean. - Project execution. Scoping, milestones, releases. You break large initiatives into shippable pieces, drive them, and unblock people. You communicate status without being asked. You name risks early. - Onboarding and rollout. New clinics, new features, new agent capabilities. You design the rollout, run the first few yourself, then turn it into something repeatable. - The feedback loop. Every customer call, every operator pain point, every denial pattern is signal. You're the one who closes the loop between what we hear and what we ship. You may be the only PM for a while. That means more leverage, less hiding. The bar is not "ship features" — it's "make the company smarter every week."   WHAT WE LOOK FOR - Customer obsession. You know your customers' work better than they do. You've sat in their offices, watched them click, taken the panicked support call at 11pm. You can recite their workflows from memory and you have opinions about which parts are dumb. - Communication. You write clearly. You run a meeting that ends on time with decisions made. You can hold a room that includes a clinician, an operator, a Staff engineer, and the CTO, and leave everyone aligned. You over-communicate by default because the cost of misalignment is high and the cost of one more Slack message is zero. - Project ownership. You take a piece of work from "we should probably do this" through scoping, milestones, scope cuts, and the unglamorous middle, all the way to shipped and adopted. Status updates show up before they're asked for. Risks get named early. Slips don't surprise anyone. - Direction. You sit with users, sharpen the problem, and bring it back. You work with engineering and the CTO to figure out not just what to build but how to build it — phasing, scope, wha