Senior Software Engineer - RPA

About this role

We’re Heidi. We're building the future of healthcare by giving every clinician the earth's finest AI Care Partner. In just 18 months, our clinical AI products have absorbed the administrative chaos of 73 million patient visits. Today, we support over 2.5 million patient sessions a week across 190+ countries. Healthcare systems are failing us; clinicians spend more time on documentation than on patients, and the human connection that makes medicine worth practicing is eroding. Our mission is simple: double the world’s healthcare capacity and strengthen the human connection at its heart. We found product-market fit with a freemium medical scribe that clinicians love. Now, we're expanding. Every task a clinician hands to Heidi is a patient who feels more attended to, a health system unclogged, and a clinician who gets to be a clinician again. If you don’t choose easy and you want to build something way bigger than yourself then, choose the challenge, choose Heidi. THE ROLE Most EHRs don't offer us an API, so where a direct integration isn't possible, or isn't fast enough for a health system that needs to go live now, we build our own automation engine that works the EHR the way a person would: reading the interface, mapping the fields and pushing structured data into the record. This is a code-first role, not a low-code studio one. We looked hard at the vendor RPA platforms and decided against building on someone else's engine as they were either too slow, too fragile for patient data, and we weren't comfortable that they could guarantee determinism. You'll build and harden ours in-house: the UI-automation layer, the mapping templates and the patient-matching logic that has to be right every single time, because it writes into a real patient record. AI helps us set automations up fast; deterministic code is what runs in production. You'll work hands-on with live NHS and private deployments where a native integration isn't on the table yet and automation is the route to going live. Sometimes that might mean being on site with our Commerical Team, watching how a coding team or clinic actually works rather than how the process doc says they do, and turning what you see into shipped automation within days. You'll work closely with the Product and Agents teams pushing this capability forward, taking the engine from working in a demo to working unattended, for every customer, at scale. We know that brilliant people can come from unlikely places; if you have a proven track record of making brittle, opaque systems behave predictably, regardless of industry, we want to meet you.   What you’ll do - Design, build, and maintain Heidi's deterministic automation engine for interacting with EHRs that lack a native integration. - Build UI-automation flows (accessibility-tree mapping, templated field entry, structured write-back) across web and desktop systems that reliably push data into third-party software. - Implement patient-matching and validation logic so data lands on the correct record every time, with patient data safety as a non-negotiable constraint. - Prototype with AI-assisted tools like Claude Code and Cursor to ship in days, then harden what works into production-grade code. - Embed with health systems and their IT teams during live rollouts: map the real workflow on site, close the gaps, get them live. - Engineer work queues, retries and exception handling so automations run unattended and failures are caught and explainable rather than silent. - Harden flows against UI drift and edge cases, and decide with Product and Integrations where automation is the right route versus where a native integration should be built instead. - Treat every automation as a product: instrument runs, measure reliability, and own the tooling and docs that let other engineers extend the engine to new EHRs.     What you'll need - Strong sense of ownership & strong problem-solving skills. - Proof you build: a tool, a script, an automation that solved a real problem for real users. A portfolio, GitHub or demo you can walk us through beats years on a CV. - Production experience with UI automation: Playwright, accessibility-tree frameworks like FlaUI, or an RPA platform you've since outgrown. - Python as your primary language; C# or TypeScript alongside it is a bonus. - Deterministic-systems instincts: queues, retries, idempotency and exception handling, and the discipline to make an automation fail loudly rather than wrongly. - Comfort with brittle, undocumented or legacy third-party interfaces, and building reliable logic around them. - Working fluency with LLM APIs and AI-assisted development. You've shipped something with these tools and know where the model helps and where it doesn't. - Data & application security knowledge, with a serious appreciation for handling patient data safely. - Comfort working directly with customers and field teams when a deployment needs eyes on the actual workflow. - Experience automating against regulated, high-stakes systems (payments, banking, healthcare) is a strong signal, not a requirement. - If your experience lives entirely inside a low-code studio, this probably isn't the fit. We're building the engine, not configuring one. How we show up - Build for the next decade, not next quarter. Our targets are outrageous on purpose. The world's health doesn't have the luxury of incrementalism. - Lead, don't wait. We treat tomorrow's problems today. Sometimes we build what's needed before it's wanted, and we're fine with that. - Follow the evidence. Trust the patient. We pursue truth relentlessly. But when the subjective and objective disagree, we treat the patient, not the numbers. Ego is a comorbidity we can't afford. - Own the outcome. Everyone here carries the company. Raise problems with solutions, solve them end-to-end, and never be a bystander. - Ship, measure, go again. A button today, a workflow tomorrow. Mor

View the original posting ↗