> Markdown version of [/jobs/ext/3966253-senior-software-engineer-clinical](https://www.wearedevelopers.com/jobs/ext/3966253-senior-software-engineer-clinical). 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). --- # Senior Software Engineer, Clinical - **Company:** Extended Care Professional, LLC - **Location:** Denver, CO, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Hospital Information Systems, Software as a Service, Adobe Coldfusion, Database Models, Microsoft SQL Server, Node.Js, Software Engineering, TypeScript, ReactJS, AngularJS, Playwright, Domain Driven Design - **Published:** October 27, 2026 - **Apply:** https://www.careerbuilder.com/job-details/senior-software-engineer-clinical-denver-co--945c73b6-7e91-41b5-9b63-e7e7486fa642 ## About the Role Software Engineering, Clinical Information Systems, ECP Standards, Product/Service Launch, Software as a Service (SaaS), High Tech Industry, Quality of Life, Process Improvement, Medical Products, Medication Administration ## Description The clinical product is ECP's flagship, and caregivers are in it every shift. When a nurse documents a medication administration or a care aide records an overnight observation, that's our software. The team you'd join builds the next generation of it. The new platform is live and customers are using it, but most clinical functionality still sits in ColdFusion and AngularJS. We move customers a function at a time, so a caregiver can be in the new platform for one task and in ColdFusion for the next. Finishing that migration is the near-term work, and we're doing it with AI. The hard part is proving a migrated workflow still does what it did before. You'd report to the Senior Engineering Manager for Clinical, on a team of four engineers with a tech lead and a dedicated product manager. You'd own clinical domains end to end, moving them onto the new platform for most of your first year and building new capability on them after that. The stack: The new code is Node, React, and TypeScript on AWS, with domain-driven design and an event bus between the products. Data is SQL Server on a single-tenant database model, one per community. You won't write much ColdFusion, but you'll read plenty of it. What You'll Build The migration. You'll take a workflow that lives in ColdFusion today, work out what it does including the parts nobody wrote down, and rebuild it. You own that domain through to production, and you write the tests that prove it works. Not all of it carries over unchanged. The medication administration workflow is already redesigned and waiting, and you'll settle with product up front which differences are deliberate, so nobody reads one as a regression later. New clinical capability. Once a domain lands on the new platform, the team builds on it. You'll work with the product manager on scope and sequencing, and we expect you to push back when there's a cheaper way to get a caregiver the same outcome. The quality bar. The team is moving toward engineer-owned automated coverage in Playwright, and we want it to go further. You carry the pager for the domains you build. What Success Looks Like At six months the migration is well underway, and several of the domains that moved are yours. Caregivers are using them. The team has taken its cues from you on what AI-generated work is fit to merge, and review isn't where the migration slows down.