> Markdown version of [/jobs/ext/4662574-senior-software-engineer-platform](https://www.wearedevelopers.com/jobs/ext/4662574-senior-software-engineer-platform). 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, Platform - **Company:** Extended Care Professional, LLC - **Location:** Denver, CO, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Amazon Web Services, User Authentication, Software as a Service, Adobe Coldfusion, Data Sharing, Data Warehousing, PostgreSQL, Microsoft SQL Server, Node.Js, Operational Data Store, Software Engineering, TypeScript, Event Driven Architecture, Domain Driven Design - **Published:** November 10, 2026 - **Apply:** https://www.careerbuilder.com/job-details/senior-software-engineer-platform-denver-co--c14e0cc5-f336-4b20-8645-5f27c148df19 ## About the Role Software Engineering, ECP Standards, Product/Service Launch, Software as a Service (SaaS), High Tech Industry, Quality of Life, Process Improvement, Authentication, Marketing/Promotional Messaging, HIPAA (Health Insurance Portability and Accountability Act) ## Description Every delivery team at ECP depends on a set of shared components that none of them own. The authentication and identity layer every user passes through, the shared data services at the core of the product, and the messaging infrastructure connecting the platform are three of them, and they are not the only ones. When any of these has undocumented behavior, a reliability gap, or needs a coordinated change, the work falls to whichever team happens to be closest to it that sprint. We're standing up a platform organization to close that gap, and you'd be one of its first engineers. ECP Intelligence sits here too. It's a set of role-based agents meant to get our users out of the software and back to their communities. Today it's a strategy. Nothing has been designed or written yet. Our data warehouse, which this team also owns, will give an agent what it can see. You own what it can do. An agent that only reads is a demo. One that acts has to act as a specific user, inside that user's permissions, through the same identity and domain services every other client of the platform goes through. That is your first mandate. This is a builder role on a team of four senior engineers, reporting to the VP of Platform Engineering. You'll write the code these capabilities are made of, with a loud voice in how they get designed. The stack. New code is Node and TypeScript. We're migrating off a ColdFusion legacy platform, and the two will coexist for a while. SQL Server and PostgreSQL, a mix of monolith and services, adopting domain-driven design and an event-driven architecture, all on AWS. This is a multi-tenant HIPAA product. You won't write ColdFusion, but you will design against it, because what you write has to serve both platforms at once. What You'll Build ECP Intelligence. You'll build the tool surface an agent acts through, the retrieval and context layer that grounds it in the right clinical and operational data, the serving path product teams call to reach a model, and the evaluation that catches a regression before a customer does. You'll also build the first agent workflows that run on it. This is clinical software, so you have to be able to prove what an agent cannot do. The shared components. Which ones we take on first is an open question, and you'd help answer it. The shape of the work is the same either way. These are systems already in production that every team depends on, with behavior nobody wrote down and boundaries nobody drew on purpose. You'll take them over, give them interfaces worth depending on, and make the seams between the legacy platform and the newer services explicit.