Staff Software Engineer (Reporting Integrations)

• Radiologists don’t work in a single application — they move between a PACS, a worklist, and our reporting platform, and they expect all of them to stay in lockstep. This role owns those integrations
• You’ll build and standardize the real-time context synchronization and data exchange that make Rad AI’s reporting platform feel native inside any radiology environment, whether that’s a modern FHIRcast session or a decades-old system that only speaks XML dropped in a folder
• As a Staff Software Engineer for Reporting Integrations, you’ll set the technical direction for the platform those integrations are built on — the foundation that lets us support new partners and new types of systems without rebuilding from scratch each time
• Integrations are where our software meets each customer’s existing systems, and getting them right often decides whether a customer goes live in weeks or months
• Design, build, and own real-time context synchronization integrations — primarily FHIRcast for context sharing, alongside file-based (XML/JSON drop) integrations with PACS, worklists, and EHRs
• Help architect a flexible, evolvable integration platform — one where new integrations are composed from reusable building blocks rather than rebuilt from scratch, so we can adapt quickly to the needs of a growing and diverse customer base
• Work hand-in-hand with Product to shape what’s possible with third-party systems — bringing an integrations-first engineering perspective early, when we’re weighing the challenges and opportunities of building something new
• Extend that platform into new categories of integration partners beyond the traditional reporting workflow — non-clinical analytics tools, CDI (clinical document integrity) tools, and clinical AI tools that generate draft reports, among others. You’ll design the frameworks that make each new class of integration repeatable
• Collaborate across a wide set of stakeholders including internal teams, customers, external vendors and integration partners to align on how these integrations should work and where they should head
• Partner directly with customers and vendors: get on calls, map out their clinical workflows and edge cases, and carry integrations through go-lives and escalations into production
• Coordinate the connectivity that gets cloud-delivered integrations live by working with hospital IT, security, and identity teams on firewall access, certificate handling, and SSO
• Drive standardization: turn one-off, customer-specific integrations into reusable connectors that shorten every future go-live
• Own reliability and observability for integrations including build the logging, tracing, and staging/E2E testing that make issues diagnosable without re-engaging customers and vendors to reproduce them
• Debug and resolve integration issues end-to-end, often across systems you don’t control, using logs, traces, and a strong mental model of how the pieces fit together
• Raise the bar for the team: document hard-won knowledge about vendor quirks and workflow scenarios, and mentor other engineers working in this space

Benefits

• 100% health, dental, & vision
• Flexible PTO
• WFH stipend
• 401k plan
• Stock options
• Socials & off-sites- Strong communication skills where you can run a technical call with a customer, vendor, or partner, diagnose the problem, and propose a standardized path forward in the same conversation
• Practical hands-on experience with healthcare context-sharing and data-exchange technologies like FHIRcast, SMART on FHIR, FHIR, or equivalent standards and protocols
• Expertise in part of this stack (TypeScript, Node, React, Electron), with interest in picking up the gaps
• Experience thinking at the platform level by building integrations as reusable, extensible frameworks rather than a pile of one-offs
• A backend leaning full stack engineer who is passionate about integrations in healthcare. This is a niche, and we want someone who wants to go deep in it
• A track record of shipping and supporting production integrations with third-party clinical systems
• Experience building and operating production services in a cloud environment
• Direct radiology experience — this is a major plus
• Familiarity with HL7 or DICOM
• Hands-on experience integrating with PACS, radiology worklists, or Epic
• Familiarity navigating legacy desktop integration mechanisms used by older clinical systems — enough to meet them where they are while pushing toward modern, standards-based approaches
• Participation in IHE Connectathons, or experience implementing IHE profiles such as IRA (Integrated Reporting Applications), SWF (Scheduled Workflow)