Code Breaker Jobs in Illinois (NOW HIRING)

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 

Foundation Engineering is a new platform capability at ECP. It owns the path from code to production: the CI/CD pipeline, the environments code runs in, the test automation framework, and the observability tooling that shows how code behaves once it's live. 

Almost none of it is built yet. CI/CD is split across Bitbucket Pipelines and Jenkins. Environments are shared and fragile. QA writes the automated tests on delivery teams' behalf. We have Sentry and CloudWatch, which is error tracking and infrastructure metrics, not observability. You'll fix all of it without breaking a product that thousands of communities run their operations on. Our newer product surfaces move first; our clinical surfaces sit on the oldest platform and carry the highest cost of failure, so they move last, once the safety net exists. 

The work is hands-on. Most of your time goes to writing infrastructure code and building tooling. You'll have an open req for one engineer to hire alongside you and two SDETs partnered with you on the test framework, reporting to the VP of Platform Engineering. This is a player-coach role: you'll build the team as the function grows, managing 2 to 4 people over time while staying close enough to the code to set the technical bar yourself. 

The stack. New code is Node and TypeScript. We're migrating off a ColdFusion legacy platform, and the two will coexist for a while. SQL Server and PostgreSQL, a mix of monolith and services, adopting domain-driven design and an event-driven architecture, all on AWS. Your pipeline and tooling have to serve the old stack and the new one at the same time. You won't be writing ColdFusion. 

What You'll Own 

The delivery pipeline. Consolidate CI/CD onto a single system every delivery team builds and deploys through. Cut build and deploy times. Own the AWS and CloudFormation infrastructure underneath it. Make dependency scanning, secrets detection, and static analysis default steps on every build. Give teams feature flags so deploy and release come apart. 

The developer platform. This starts on the engineer's machine: environment setup, build speed, the tools they use before code ever reaches the pipeline. Replace shared environments with ephemeral ones, and solve multi-tenant test data seeding so they're usable. Our event bus is partially adopted, which makes contract testing part of this: services have to be testable in isolation without standing up the whole topology. Establish golden paths: opinionated, documented ways to build, test, and deploy a service. Drive toward self-service, and over time an internal developer portal. Run the platform as a product, with a visible roadmap, a feedback channel teams actually use, and reliability standards for the platform itself. 

The test automation framework. Turn a framework QA builds on delivery teams' behalf into one delivery engineers use directly. Two SDETs work with you on it. Building it is the straightforward part. Landing it with delivery leads whose teams are measured on shipping is the job. 

Production ownership. Delivery engineers carry the pager for their own code today, but most incident response still lands on the infrastructure team, because engineers can't see or reach what they shipped. This is a HIPAA environment, so broad production access isn't on the table. Engineers need full visibility into how their systems behave without access to the data inside them. Build the logging, tracing, metrics, and alerting stack that delivers that, and give teams audited break-glass paths for the cases that need more. 

The agentic development loop. Our engineers already use AI-assisted development, and it's made everything downstream of them slower. Code generation is cheap. Verification is not. That gap is what we're hiring you to close. You'll own what makes coding agents effective in our codebase: deterministic local builds, fast test feedback, repo context, sandboxed execution, review gates for agent-authored code, and internal platform capabilities exposed to agents through MCP. 

Requirements

Required 

• You've led a developer experience or platform engineering function before, and can point to what measurably changed because of it. 

• Deep AWS and infrastructure-as-code experience, and enough command of CI/CD to redesign a system rather than run one someone else built. 

• You've moved testing from a QA-owned function to an engineer-owned one, or won an equivalent adoption fight. We care that it stuck. No delivery team reports to you here, and the platform only works if they choose it over what they have. 

• AI-assisted development is already how you work, and you know where it holds up and where it needs a human check. 

• You've managed or led a small team of engineers, and you're comfortable doing so while staying very hands-on in the code. 

Preferred 

• HIPAA-regulated or other compliance-sensitive environment 

• Contract testing or service virtualization in an event-driven system 

• Bitbucket Pipelines, Jenkins, or GitHub Actions 

• SQL Server and PostgreSQL at production scale 

What Success Looks Like 

At six months: 

1. Every non-clinical delivery team builds and deploys through one pipeline, security scanning runs by default, and builds are measurably faster than the day you started. 
2. At least one team runs on ephemeral environments with realistic seeded data, and its engineers write their own tests. 
3. Delivery leads describe Foundation Engineering as the reason shipping got faster. 

The developer portal, full observability coverage, clinical migration, and org-wide progressive delivery are longer term goals that will come later.