Senior Software Engineer, Clinical

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. 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 The clinical product is ECP's flagship, and caregivers are in it every shift. When a nurse documents a medication administration or a care aide records an overnight observation,that'sour software. The teamyou'djoin builds the next generation of it. The new platform is live and customers are using it, but most clinical functionality still sits in ColdFusion and AngularJS. We movecustomersa function at a time, so a caregiver can be in the new platform for one task and in ColdFusion for the next. Finishing that migration isthe near-term work, andwe'redoing it with AI. The hard part isprovinga migrated workflow still does what it did before. You'dreport to the Senior Engineering Manager for Clinical, on a team of four engineers with a tech lead and a dedicated product manager.You'down clinical domains end to end, moving them onto the new platform for most of your first year and building new capability on them after that. The stack:The newcode is Node, React, and TypeScript on AWS, withdomain-driven design and an event bus between the products. Data is SQL Server on a single-tenant database model, one per community. Youwon'twrite much ColdFusion, butyou'llread plenty of it. What You'll Build The migration.You'lltake a workflow that lives in ColdFusion today, work out what it does including the parts nobody wrote down, and rebuild it. You own that domainthrough toproduction, and you write the tests that prove it works. Not all of it carries over unchanged. The medication administration workflow is already redesigned and waiting, andyou'llsettle with product up front which differences are deliberate, so nobody reads one as a regression later. New clinical capability.Once a domain lands on the new platform, the teambuilds onit.You'llwork with the product manager on scope and sequencing, and we expect you to push back whenthere'sa cheaper way to get acaregiverthe same outcome. The quality bar.The team is moving toward engineer-owned automated coverage in Playwright, and we want it to go further. You carry the pager for the domains you build. What Success Looks Like At six months the migration is well underway, and several of the domains that moved are yours. Caregivers are using them. The team has taken its cues from you on what AI-generated work is fit to merge, and reviewisn'twhere the migration slows down. Past the migration, this job is new clinical capability, and the measure is how quickly a caregiver gets something they asked for. Requirements Required Depth in TypeScript on both sides of the stack, Node on the serverand React in the browser. Tell us about a feature you took from the data model to the interface, and whatyou'dmodel differently now. AI-assisted development is how you work, daily, on production code, and you know where you stopped trusting it. You'vepointed AI at a large codebase youdidn'twrite and gotten useful work out of it. The part we want to hear about is what you did when the first answer was confidently wrong because the modelcouldn'tsee enough of the system. You'vemoved other engineers alonginhow they use AI. Domain-driven design in a complex domain. The version that matters here is drawing a boundary against a system youcan'tchange, so tell us about one you drew and what it cost you when it landed in the wrong place. You'vebuilt software where a defect has consequences past a bad user experience, and it changed how you test and how you ship. You were on call for it. Data modeling and query performance where the tenant model is the data model.You'vefound and fixed a query that was fine in development and fell over on your largest customer. You work withproductinsteadof waiting on it.You'vechanged what got built by understanding the business problem behind a story. Preferred A legacy-to-next-generation migration you saw through, particularly one where both systems ran in production at the same time ColdFusion, or another language you inherited rather than chose HIPAA, PHI, or another regulated data environment SQL Server, AWS, event-driven architecture in production Offline-first or progressive web applications Playwright or comparable browser automation you owned yourself Healthcare, or time spent watching clinical staff work #J-18808-Ljbffr ECP