Senior Software Engineer, Platform

ECP is a market-leading SaaS solution that enables senior living communities to better care for their residents. The Senior Software Engineer, Platform will build AI foundations, agent workflows, shared platform components, data services, and messaging infrastructure while shaping platform architecture and supporting production systems.

Responsibilities:

• 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
• The messaging backbone. The event bus works, but it's only partly adopted and nobody owns it. You'd take 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:

• You've built 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 were actually doing
• You've built 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've carried 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
• 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