Product Manager (US)

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.

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."

• 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, what's worth doing now versus later. You're a thought partner, not an order-taker, and not an order-giver either.

• Speed. Not crashed-out hustle-culture speed. The kind that comes from deleting unnecessary work, making decisions quickly, and not being precious about being wrong.

• Range. You'll do customer success this morning, scope a release this afternoon, and write rollout docs tonight. You don't need to be a 10/10 at every part of the job. You do need to be willing to do whichever part the week demands.

• Technical literacy. You don't need to write code. You do need to be able to read a PRD with engineers and push back on the right things. You need to understand enough about how agents, LLMs, and our systems work that you can scope without hand-waving.

8+ years in product, with meaningful time owning a product or major surface end-to-end. We care more about the slope than the years — what you've shipped, what you learned the hard way, and what you'd do differently now. You've worked closely with customers, you've written PRDs that engineers actually liked, and you've seen at least one product go from zero to something real.

Bonus, not required:

• Healthcare, RCM, or vertical SaaS background. Helpful, but a great PM beats domain expertise. We'll teach the domain to the right person.

• Early-stage experience. You know what it feels like to be the only PM, with no playbook, talking to customers in the morning and writing tickets in the afternoon.

• Agentic AI / LLM products. You've shipped product where the system makes decisions, gets things wrong, and has to earn trust over time. You know how to design for that.

• Compensation. Salary in the $180K–$240K range plus meaningful founding-team equity, both calibrated to seniority and scope. We'll be specific in the first conversation.

• Health, dental, vision. Fully covered.

• 401(k) with match.

• In-person in the Bay Area is the default — small teams move faster in a room together. We'll consider remote or hybrid setups for exceptional candidates. Commuter benefits for those in office.

• Meals. Lunch, dinner, and snacks on the company.

We borrowed our process from Linear because we think they got it right.

1. Intro call with the CTO. ~30 minutes. We talk about you, the company, and whether the role fits. We'll discuss comp on this call.

2. Product conversation. ~60 minutes. We walk through a product you've shipped — the decisions you made, the things you cut, what you'd do differently — and we look at one of ours together.

3. Paid work trial. 2–5 days, paid at our standard daily rate. You work on something real. You talk to a customer, scope a piece of work, sit in on an operator session. You leave with a much clearer picture of whether Supa Health is the right place for you, and we leave with a much clearer picture of whether you're the right person for Supa Health.

4. Decision. Independent feedback from the trial team, then a debrief, then an offer (or honest feedback if not).

We aim to go from intro call to offer in 1–2 weeks.

We'd rather be honest now than waste your time later.

• If you manage product through documents and rituals, you'll be frustrated. We have a roadmap. We don't have a quarterly planning offsite. Most decisions happen in Slack and in person, not in Linear tickets.

• If you don't want to talk to customers, this won't work. Customer interactions are the core of the job, not something to delegate to a CSM later.

• If you want a 9-to-5, that's a legitimate choice, and it isn't this job. We don't expect crunch, but we expect founding-team intensity.

• If you need a data team to make decisions, you'll be slow. The data team is you for now. So is the CSM.

• If you want to manage other PMs, not yet. The team is small. People-management roles will exist later; this isn't one.

   

If you read all of that and you're more interested than when you started, we want to talk.