Senior Software Engineer, Platform

ECP; United States; Remote; USD 140,000 - 190,000; Full time

Job summary

ECP is expanding its platform engineering team to deliver core shared components, the authentication layer, and the data services that power ECP Intelligence. You will build the agent workflows, ensure you can operate as a specific user within identity and domain services, and drive reliability across multi-tenant deployments.

You’ll work on a stack of Node and TypeScript with SQL Server, PostgreSQL, and AWS, migrating from a legacy ColdFusion environment while maintaining production services

Qualifications

• Experience designing and implementing platform services and shared components.
• Strong understanding of domain-driven design and event-driven architecture.

Responsibilities

• Build shared platform components and the agent/workflow surface for ECP Intelligence.
• Collaborate with product and data teams to enable multi-tenant AI features.
• Maintain reliability, scalability, and governance across services.

Job description

About ECP

ECP is a market-leading SaaS solution that enables senior living communities to better care for their residents. ECP is used in over 8,000 communities.We’relooking to further expand by increasing the number of customers that use our software and increasing the scope of how we serve our customers by developing and releasing new products.

Senior living is deeply under-penetrated withsoftwareand ECP is one of the largest and fastest-growing software companies in the industry. We recently raised a growth round of equity to reinvest in our product, technology, and go-to-market. Our mission is to build world-class software that improves the quality of life for seniors and improves clinical, business, compliance, and operational performance for our customers.

The Role

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 infrastructureconnectingthe 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’restanding up a platform organization to close that gap, andyou’dbe one of its first engineers.

ECP Intelligence sits here too.It’sa set of role-based agents meant to get our users out of the software and back to their communities. Todayit’sa strategy. Nothing has been designed or written yet. Our data warehouse, which this team also owns, will give an agent what it can see. Youownwhat it can do. An agent that only reads is a demo. One that actshas toact 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’llwrite the code these capabilities are made of, with a loud voice in how they get designed.

The stack.Newcode is Node and TypeScript.We’remigrating 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 andan event-driven architecture, all on AWS.This is a multi-tenant HIPAA product. Youwon’twrite ColdFusion, but you will design against it, because what you writehas toserve 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’llalso build the first agent workflows that run on it.This is clinical software, so youhave tobe able to prove what an agent cannot do.

The shared components.Which ones wetake onfirst is an open question, andyou’dhelp 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’lltake them over, give them interfaces worth depending on, and make the seams between the legacy platform and the newer services explicit.

The messaging backbone.The event bus works, butit’sonly partlyadoptedand nobody owns it.You’dtake it the rest of the way, add contract testing so a service can be verified on its own, and support it as something the other teams can build on.

Requirements

What We’re Looking For

Required

• You’vebuilt shared components or platform services that other teams depended on, and you stayed accountable for them afterward. This is not a first platform role.
• Real depth in domain-driven design and event-driven architecture. You can explain why a bounded context sits where it does, what an anti-corruption layer bought you, and which flavor of event-driven you wereactually doing.
• You’vebuilt the production systems behind an AI feature, against data that was messy, governed, and inconveniently shaped. The model itself is someone else’s problem.
• You’vecarried a pager for a system other teams depended on.
• Breadth across more than one language and paradigm, with real depth in at least one. Tell us about a time you had to get productive in an unfamiliar stack fast, and what that took.
• Data modeling and query performance under real load. Some of our shared components sit on the hot path for every request.
• AI-augmented development is already how you work, and you know where it holds up and where it needs a human check.

Preferred

• Experience shipping meaningful customer-facing AI features (more than just a chatbot)
• PHI or other regulated data in an AI or analytics path
• Multi-tenant SaaS at scale, with tenant isolation as a data-layer concern
• Node and TypeScript, SQL Server, PostgreSQL, AWS
• Building alongside a legacy platform mid-migration, without the luxury of waiting for it to finish
• Contract testing or service virtualization in an event-driven system
• Mentoring engineers, or wanting to grow into it

What Success Looks Like

At six months, the AI foundation isrealand at least one ECP Intelligence agent workflow is running in front of customers, taking work off a caregiver’s plate that they used to do by hand.

The shared components and the messaging backbone are a longer job, and that work starts once theagentfoundation is in place. The measure there is that teams build on these components without having to think aboutthem, andspend their time on their own roadmaps instead.