Supa Health - Staff Software Engineer (India)

• ₹40L – ₹75L • Offers Equity • Calibrated to seniority and scope • 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 • 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. • 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. • Architecture and direction. • 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. • The quality bar. • 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. • Project execution. • 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. • Technical communication. • 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. • Building, still. • 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 • 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. • Craft as a discipline. • 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. • Architectural judgment. • 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. • Code review as leverage. • 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. You communicate status without being asked. You name risks early. • Project ownership. • Direction. You work with users, product, and the CTO 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 — not someone waiting for a spec, and not someone going off in a vacuum. • Direction. • 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. • Speed. • Range. You don't need to be a 10/10 at frontend, backend, infra, AI, and product. You do need to be the person on the team who can dive into whichever of those is on fire this week. • Range. • The technical bar • The technical bar • 8+ years building production software, with meaningful time at the senior or staff level. We care about the slope as much as the years — what you've shipped, what you learned the hard way, and what you'd do differently now. You've lived in TypeScript and Postgres long enough to have real opinions about both, and you've designed systems that other engineers had to live with for years. • Compensation. Salary in the 40L-75L range plus meaningful early-stage equity, both calibrated to seniority and scope. We'll be specific in the first conversation. • Health, dental, vision. Fully covered. • Health, dental, vision. • PF with match. • In-person in the Bangalore is the default — small teams move faster in a room together. We'll consider remote or hybrid setups for exceptional candidates. • In-person in the Bangalore • Meals. Lunch, dinner, and snacks on the company. • Meals. • How we hire • How we hire • We borrowed our process from Linear because we think they got it right. • Intro call • Technical conversation. ~60 minutes. We work through a real problem together. No leetcode. • Technical conversation. • Architecture conversation. ~60 minutes. We walk through a system you've designed and built, and we look at one of ours. • Architecture conversation. • Paid work trial. 2–5 days, paid at our standard daily rate. You work on something real. You meet the team. 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. • Paid work trial. • Decision. Independent feedback from the trial team, then a debrief, then an offer (or honest feedback if not). • Decision. • We aim to go from intro call to offer in 1–2 weeks. • Who this isn't for • Who this isn't for • We'd rather be honest now than waste your time later. • If you've moved away from writing code, this isn't it. Staff here means staff-level IC work, not architecture astronaut. • If you've moved away from writing code, • If you set direction by writing documents and waiting for buy-in, you'll be frustrated. Direction here is set by talking to the team, sketching, prototyping, and arguing the right calls into existence. • If you set direction by writing documents and waiting for buy-in, • 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 early-team intensity. • If you want a 9-to-5, • If you're allergic to talking to users, this won't work. Operators and clinic owners are part of your job, not someone else's. • If you're allergic to talking to users, • If you want a corner of the system to be solely yours, the Staff role spans surfaces by design. You'll have a point of view on all of it. • If you want a corner of the system to be solely yours, • If you read all of that and you're more interested than when you started, we want to talk..