Senior Software Engineer, Platform

Job not on LinkedIn

🔥 0 minutes ago

⛰️ Colorado, Illinois, +1 more states – Remote

⛰️ Colorado – Remote 🌽 Illinois – Remote 🗽 New York – Remote

⏰ Full Time

🟠 Senior

🏗️ Platform Engineer

Apply Now

Find Similar Remote Jobs

Set Up Email Alert For New Jobs

📊 Check your resume score for this job

Improve your chances of getting an interview by checking your resume score before you apply.

Upload Resume

ECP

WebsiteLinkedInAll Job Openings

51 - 200 employees

⚕️ Healthcare Insurance

☁️ SaaS

🤝 B2B

Healthcare Insurance • SaaS • B2B

ECP is a company that provides comprehensive software solutions for assisted living and long-term care communities. Their offerings include community management systems, electronic medication administration records (eMAR), electronic health records (EHR), care plans, customer relationship management (CRM), and billing software. ECP's services are designed to improve the workflows for assisted living, independent living, memory care, intellectual and developmental disability support, pharmacies, and group homes, ensuring better care and operational efficiency. The company is recognized for integrating seamlessly with pharmacy partners and offering a user-friendly platform that supports care providers, owners, and operators, caregivers, nurses, and other personnel in these communities. ECP is trusted by thousands of senior living communities across the United States and beyond.

📋 Description

• 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. • Take over shared components that every team depends on, providing interfaces worth depending on, and clarify the seams between the legacy platform and the newer services. • Enhance the messaging backbone; take the event bus the rest of the way, adding contract testing for service verification.

🎯 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