Loading this job…
You will own features end to end across the Nimbus hospital platform: the React interface a ward nurse uses, the Node API behind it and the MongoDB collections underneath. Feature ownership here really is end to end, including the conversation with the hospital that asked for it.
A hospital tells us that discharge summaries take twenty minutes because the doctor retypes information that already exists in three other screens. You spend a morning watching how it is actually done, design a flow that pre-fills what we already know, build the API and the interface, roll it out to two friendly hospitals and then to everyone. Four weeks, one engineer, a measurable change to somebody real workday.
Two to five years across both ends of a web stack. You do not need equal depth on each side, but you should be able to design a reasonable schema, write an API you would not be embarrassed to document, and build an interface that a tired person can use correctly on the first try.
Healthcare experience is not required. Patience with domain complexity is, because hospital workflows are genuinely intricate and the shortcuts are usually wrong.
Nimbus makes the software that runs mid-sized Indian hospitals: appointments, electronic records, pharmacy stock, insurance claims and discharge summaries. Around 140 hospitals across seven states use it every day.
Our users are nurses and front-desk staff on shared desktops and ageing Android tablets, often over an unreliable connection. That constraint shapes everything we build, from offline-first flows to small payloads to interfaces that survive being used at speed by someone at the end of a double shift.
We are a compact team in Gachibowli, Hyderabad, and we hire people who are comfortable sitting with clinicians to find out what they actually need.
Swiss Digital Workplace Employer🇨🇭 Winterthur
Swiss Digital Solutions Provider🇨🇭 Winterthur


Peregrine Remote🌍 Remote (Worldwide)
Northwind Systems🇨🇦 Toronto, ON