Product Designer (Bangalore)

Founding Product Designer

Supahealth is a US healthcare AI startup building the agentic operating system for behavioral health clinics. We are targeting the $250B behavioral health market, starting with the administrative work that makes care expensive, slow, and hard to scale.

Location: Bangalore

About Supahealth

Mental healthcare is growing fast, but the infrastructure behind it is broken. Clinicians spend hours on documentation. Clinics spend meaningful revenue on manual admin work. Back-office teams wait on hold with insurance payers, verify benefits by hand, file claims through payer portals, and chase denials months after a visit.

These workflows were built for a different era. They cannot scale to meet the demand coming online.

Supahealth automates the invisible work of running a mental health practice: intake, benefits verification, prior authorization, clinical documentation, claims filing, denial follow-up, payment tracking, and reporting. Our agents make calls, use browser workflows, reason through payer-specific rules, hand off to humans when needed, and learn from every outcome.

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

The Role

We are looking for a founding product designer to own design at Supahealth.

This is not a role for making screens after the product has already been decided. You will help shape the product from the beginning: how clinicians review AI-generated documentation, how operators supervise agents, how billers resolve edge cases, how customers understand what happened, and how our systems expose uncertainty, trust, and control.

The product is complex because the work is complex. A mental health practice is a dense system of intake, scheduling, documentation, eligibility, prior authorization, claims, denials, payments, and clinical operations. Our agents will make decisions across these workflows, and humans need to understand, correct, and trust them.

Your job is to make that complexity usable.

You may be the only designer for a while. That means high ownership, high taste, and willingness to move from user research to systems thinking to pixels to shipped product.

What You'll Own

- Product design across Supahealth's core surfaces: clinician workflows, operator tools, customer-facing experiences, agent supervision, exception handling, reporting, and internal systems.

- End-to-end UX for agentic systems: human-in-the-loop checkpoints, confidence states, decision traces, review queues, escalation paths, and recovery flows.

- Deep user understanding: sitting with clinicians, billers, operators, and practice owners to understand how the work actually happens.

- Interaction design for complex workflows where speed, clarity, accuracy, and trust matter more than decorative polish.

- Visual design and product craft: layouts, components, hierarchy, states, empty states, error states, and flows that feel calm, precise, and usable.

- Prototypes, wireframes, high-fidelity mocks, and design specs that help engineering move quickly without guessing.

- The early design system: components, patterns, interaction conventions, and product principles that can scale as the product grows.

- Collaboration with the founder, PM, engineering, operations, and customers to turn messy workflows into shipped product.

What We're Looking For

- 8-10 years in product design, with meaningful ownership of complex B2B, enterprise, vertical SaaS, healthcare, fintech, insurance, compliance, devtools, data, or workflow-heavy products.

- Strong systems thinking. You can map messy real-world workflows, find the underlying structure, and design interfaces that make them tractable.

- Strong interaction design. You care about states, edge cases, hierarchy, speed, density, and what happens when things go wrong.

- Excellent visual taste. The product should feel clear, modern, and trustworthy without becoming precious or overdesigned.

- Comfort designing for AI systems, automation, or ambiguous system behavior. You understand that AI products need transparency, control, feedback, and graceful failure.

- Customer obsession. You want to watch users work, ask sharp questions, and build from observed behavior rather than abstract personas.

- High technical literacy. You do not need to code, but you should be comfortable working closely with engineers, understanding constraints, and designing with implementation in mind.

- Strong written communication. You can explain your decisions clearly in specs, design notes, and product discussions.

- Early-stage temperament: fast iteration, low ego, high ambiguity, and a willingness to do whatever part of design the company needs that week.

You Might Be a Fit If

- You are energized by dense workflows and hard product problems.

- You like designing tools people use all day, not just landing pages or lightweight consumer flows.

- You can move from rough workflow maps to polished interface design quickly.

- You care as much about error states and review queues as you do about the first impression.

- You enjoy working directly with engineering and customers.

- You have strong opinions, but you update them when the product or user reality disagrees.

- You want to define what design means at an early company.

Not a Fit If

- You need a large design team, research team, or mature design system to do your best work.

- You are uncomfortable with ambiguity, incomplete information, or fast-changing priorities.

- You do not enjoy complex operational workflows.

- You prefer handing off polished mocks over staying close to implementation.

- You do not want to spend time with customers, operators, and engineers.

Hiring Process

- Intro conversation with the founder.

- Portfolio deep dive on a complex product you designed, including the tradeoffs, iterations, and what shipped.

- Product/design working session on one Supahealth workflow.

- Paid work trial on a real product problem.

- Decision and offer.

We aim to move quickly and give candidates a clear view into the company, the product, and the kind of design work this role actually requires.