Lead Software Engineer, Clinical
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Confirmed still open
Last checked 21h ago — checked against the employer's own applicant tracking system, which is the company answering directly.
We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.
How old is it?
Posted 1d ago
The date the source published, not the day we noticed it (2026-11-16). Last seen at its source 1h ago.
Is it remote?
Marked remote on the employer's board
Their board carries a remote setting on this posting — a field they filled in, not wording we read. The location field names somewhere specific, which is usually where the team or the entity sits.
Who may apply?
United States
The description states no restriction of its own. This is the source's own tag.
Pay not stated
Similar roles pay $151.5k–235k/yr
Middle 50% of 255 listings that do state pay — Engineering · Lead · United States · USD/year. This employer has published no salary; this is what comparable listings we hold disclose, never converted between currencies or periods. How this is calculated.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
Workable employer's own board first seen 21h ago · last seen 1h ago
The listing
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're looking 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 with software and 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's our software.
The team you'd join 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 move customers a 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 is the near-term work, and we're doing it with AI. The hard part is proving a migrated workflow still does what it did before.
You'd report to the Senior Engineering Manager for Clinical, as the tech lead on a team of four engineers with a dedicated product manager. You'd own 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 new code is Node, React, and TypeScript on AWS, with domain-driven design and an event bus between the products. Data is SQL Server on a single-tenant database model, one per community. You won't write much ColdFusion, but you'll read plenty of it.
What You'll Build
The migration. You'll take a workflow that lives in ColdFusion today, work out what it does including the parts nobody wrote down, and rebuild it. You own that domain through to production, 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, and you'll settle 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 team builds on it. You'll work with the product manager on scope and sequencing, and we expect you to push back when there's a cheaper way to get a caregiver the 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. You have rolled out a software factory for your team that has meaningfully improved the pace of delivery.
Past the migration, this job is new clinical capability, and the measure is how quickly a caregiver gets something they asked for.
Requirements
Required
- You have prior success as the technical lead of an AI-enabled software delivery pod.
- You've shipped and stayed accountable for customer-facing features across the whole stack, from the data model through the API to the UI. React/Node/Typescript is our preferred stack, but any polyglot engineer with strong fundamentals would fit in well here.
- Real depth in event-driven and domain-driven design. You can explain a bounded context you drew and why it sits where it does, and you've debugged an event flow in production by tracing a message through the system when something went wrong.
- You've built correctness-critical systems where wrong output had real consequences, whether payments, health, or other regulated data. Data integrity is a first-order concern in how you design.
- Cloud native. You will be productive immediately with managed cloud services, ideally within AWS.
- AI-assisted development is how you work, daily, on production code. You have a multi-agent team, work in loops, and live in worktrees. You have moved other engineers forward in how they use AI.
- Quality first mindset. You write your own unit, integration, and contract tests as a matter of course rather than handing testing off as a later phase.
- Success at scale. You have launched, tuned and ran mission critical systems at high scale with high quality.
- You work with product instead of waiting on it. You've changed what was built by understanding the business problem behind a story.
Preferred
- A successful legacy-to-next-generation application migration
- HIPAA, PHI, PCI or other regulated data environment
- Offline-first or progressive web applications
- Multi-tenant SaaS
- Continuous delivery at scale