Platform Engineer (ECP Intelligence & Shared Components)

ECP is a market-leading SaaS solution enabling senior living communities to enhance resident care, serving over 8,000 communities. The company is expanding by increasing customer adoption and developing new products to improve clinical, business, compliance, and operational performance.

The Role

This role involves building and maintaining shared platform components—such as authentication, identity layers, data services, and messaging infrastructure—that are critical to all delivery teams. You’ll join a platform organization to ensure these systems are reliable, well-documented, and scalable. Additionally, you’ll lead the development of ECP Intelligence, a set of role-based agents designed to automate tasks for users, reducing their time spent in the software and improving efficiency.

The team consists of four senior engineers reporting to the VP of Platform Engineering. You’ll design and implement code for these capabilities while influencing their architecture. The stack includes Node.js and TypeScript, with a migration from ColdFusion to coexist temporarily. The infrastructure spans SQL Server and PostgreSQL, a mix of monoliths and microservices, adopting domain-driven design and event-driven architecture, all hosted on AWS. This is a multi-tenant, HIPAA-compliant product, requiring careful design to serve both legacy and new platforms.

What You'll Build

You’ll develop the foundational tools for ECP Intelligence, including the agent interface, data retrieval and context layers, model-serving pathways, and evaluation mechanisms to prevent regressions. Additionally, you’ll design and improve shared components—such as authentication, data services, and messaging—that are currently undocumented and unreliable. These systems are already in production and relied upon by multiple teams, so your work will involve refactoring them into well-defined, maintainable interfaces.

The messaging backbone, currently partially adopted, will be fully owned and enhanced with contract testing to ensure service reliability. You’ll also build the first agent workflows that run on the platform, ensuring they operate within user permissions and through the same identity and domain services as other platform clients.

Requirements

What We're Looking For

Required:

• Experience building and maintaining shared components or platform services that other teams depend on, with long-term accountability for their reliability.
• Deep expertise in domain-driven design and event-driven architecture, including the ability to explain bounded contexts, anti-corruption layers, and event-driven patterns.
• Experience developing production systems behind AI features, working with messy, governed, and irregularly shaped data. The AI model itself is not your responsibility.
• Experience with on-call (pager) duty for systems critical to other teams.
• Broad technical skills across multiple languages and paradigms, with deep expertise in at least one. Highlight a time you quickly adapted to an unfamiliar stack.
• Proven ability in data modeling and query optimization under real-world load conditions.
• Experience leveraging AI tools in development, understanding their strengths and limitations.

Preferred:

• Experience shipping significant customer-facing AI features beyond simple chatbots.
• Experience with PHI (Protected Health Information) or other regulated data in AI or analytics workflows.
• Experience with multi-tenant SaaS at scale, including data-layer tenant isolation.
• Proficiency in Node.js, TypeScript, SQL Server, PostgreSQL, and AWS.
• Experience building alongside a legacy platform during migration, without waiting for its completion.
• Experience with contract testing or service virtualization in event-driven systems.
• Experience mentoring engineers or a desire to grow into this role.

What Success Looks Like

Within six months, the AI foundation will be operational, and at least one ECP Intelligence agent workflow will be live with customers, automating tasks previously done manually by caregivers. The shared components and messaging backbone will be refactored to be seamless and reliable, allowing other teams to focus on their own roadmaps without worrying about these foundational systems.