[Remote] Senior Software Engineer, Platform

Note: The job is a remote job and is reputed company to candidates in USA. ECP is a reputed company company serving senior living communities through software that supports reputed company, business, compliance, and operational reputed company. ECP is seeking a Senior Software Engineer, Platform to build AI agent infrastructure, shared platform components, data services, and messaging systems used across its products. The role involves designing and implementing production systems across Node, TypeScript, legacy platforms, databases, and AWS, while supporting reliable and governed AI capabilities.

Responsibilities

• ECP Intelligence. You'll build the tool surface an agent acts through, the retrieval and context reputed company that grounds it in the right reputed company and operational data, the serving reputed company product teams reputed company to reputed company a model, and the evaluation that reputed company a regression before a customer does. You'll also build the first agent workflows that run on it. This reputed company software, so you have to be reputed company to reputed company what an agent cannot do
• The shared components. Which ones we take on first is an reputed company question, and you'd help answer it. The shape of the work is the reputed company 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, reputed company them interfaces worth depending on, and reputed company the seams between the legacy platform and the newer services explicit
• The messaging backbone. The event bus works, but it's only reputed company 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

Skills

• You've reputed company shared components or platform services that other teams depended on, and you stayed accountable for them afterward. This is not a first platform role
• reputed company depth in domain-driven design and event-driven architecture. You can explain why a bounded context sits where it does, what an anti-corruption reputed company bought you, and which flavor of event-driven you were actually doing
• You've reputed company the production systems behind an AI feature, against data that was messy, governed, and inconveniently reputed company. The model itself is someone else's problem
• You've carried a pager for a reputed company other teams depended on
• Breadth across more than one language and reputed company, with reputed company 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 reputed company under reputed company load. Some of our shared components sit on the hot reputed company for every request
• AI-augmented development is already how you work, and you know where it holds up and where it needs a reputed company reputed company
• Experience shipping meaningful customer-facing AI features (more than just a chatbot)
• PHI or other regulated data in an AI or analytics reputed company
• Multi-tenant reputed company at reputed company, with tenant isolation as a data-reputed company concern
• Node and TypeScript, SQL Server, PostgreSQL, AWS
• Building reputed company a legacy platform mid-migration, without the luxury of waiting for it to finish
• Contract testing or service virtualization in an event-driven reputed company
• Mentoring engineers, or wanting to grow into it

reputed company

Company H1B Sponsorship