> Markdown version of [/jobs/ext/1758464-backend-leaning-full-stack-engineer](https://www.wearedevelopers.com/jobs/ext/1758464-backend-leaning-full-stack-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # backend leaning full stack engineer - **Company:** Rad Ai - **Location:** United States - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Software Debugging, Dicom, JSON, Node.Js, E2e Testing, Systems Integration, TypeScript, Extensible Markup Language (XML), Data Logging, ReactJS, Fast Healthcare Interoperability Resources, Electron (Programming Language), Backend, Health Level Seven International - **Published:** July 31, 2026 - **Apply:** https://www.dice.com/job-detail/4541acc1-3030-45a6-b215-9fbef7db51ed ## About the Role * 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. * Expertise in part of this stack (TypeScript, Node, React, Electron), with interest in picking up the gaps. * Experience building and operating production services in a cloud environment. * Practical hands-on experience with healthcare context-sharing and data-exchange technologies like FHIRcast, SMART on FHIR, FHIR, or equivalent standards and protocols. * A track record of shipping and supporting production integrations with third-party clinical systems. * Experience thinking at the platform level by building integrations as reusable, extensible frameworks rather than a pile of one-offs. * 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. Nice to Haves * Direct radiology experience - this is a major plus. * Hands-on experience integrating with PACS, radiology worklists, or Epic. * Familiarity with HL7 or DICOM * 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) Join our world-class team as we build and deploy AI solutions that empower physicians and transform patient care-making a meaningful impact on millions of lives. Driven by our mission, we prioritize transparency, inclusion, and close collaboration, bringing together exceptional people to revolutionize healthcare. If you're passionate about driving innovation and delivering impactful healthcare solutions, we'd love to hear from you! ## Description 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. What You'll Be Doing * 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. ## Related Videos - [ZEISS & Microsoft - Building the Next Generation Medical Ecosystem in the Cloud](https://www.wearedevelopers.com/videos/424-zeiss-microsoft-building-the-next-generation-medical-ecosystem-in-the-cloud) - [Shipping Faster with Less: Render on Cloud Hosting, AI Workloads, and the Future of DevOps](https://www.wearedevelopers.com/videos/1894-shipping-faster-with-less-render-on-cloud-hosting-ai-workloads-and-the-future-of-devops) - [Stop using Node.js like in 2020! What changed and what you can do today with Node.js](https://www.wearedevelopers.com/videos/100011-stop-using-node-js-like-in-2020-what-changed-and-what-you-can-do-today-with-node-js) - [Tips and Tricks for Working with JSON](https://www.wearedevelopers.com/videos/1229-tips-and-tricks-for-working-with-json) - [AI in High-Stakes Industries: Lessons Learned](https://www.wearedevelopers.com/videos/100253-ai-in-high-stakes-industries-lessons-learned) - [Stop Using Node.js Like It’s 2020! - Alfonso Graziano](https://www.wearedevelopers.com/videos/1863-stop-using-node-js-like-it-s-2020-alfonso-graziano) ## Related Articles - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Coffee with Developers - Maria Apazoglou - Making AI understandable for all in production](https://www.wearedevelopers.com/magazine/475-coffee-with-developers-maria-apazoglou-making-ai-understandable-for-all-in-production) - [What’s the Difference Between Frontend and Backend Development?](https://www.wearedevelopers.com/magazine/240-what-s-the-difference-between-frontend-and-backend-development) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Find a Developer Job: 12 Best Job Sites For Developers](https://www.wearedevelopers.com/magazine/165-find-a-developer-job-12-best-job-sites-for-developers)