Build software that
a doctor keeps using.
Most clinical software is abandoned in week five. We are hiring people who find that a more interesting problem than the feature list — because it is the only one that matters here.
The measurement that decides everything here is whether a clinic is still using it three weeks after we stopped visiting. That is an unusually honest place to work.
Constraints that are real.
A hard, specific problem
Thirty seconds, a ₹8,000 phone, no network, three languages, and a clinician who owes you nothing.
Measured honestly
Retention is measured unsupported, by someone who did not onboard the clinic. Nobody here grades their own work.
Reaches patients
The output is a legible prescription in someone's hand, in a language they read. Not a dashboard.
Founding roles across the stack.
Clinical informatics
Terminology bindings, index curation, clinical review of mappings.
Android engineering
The client is the product. Offline-first, low-end devices, real constraints.
Backend engineering
FHIR repository, sync, terminology service, rules.
Field operations
Clinic onboarding and the honest retention measurement that follows it.
Product & design
Ninety-second workflows. Interfaces that survive a real waiting room.
Integration
ABDM registries, consent, certification — a process with its own cadence.
Security
Assessment, audit liaison, ongoing posture on a patient-data platform.
Operations
People, finance, delivery.
Not seeing your exact role?
We are early — strong people define their own scope. Send us something you built.