Note: The job is a remote job and is open to candidates in USA. ECP is a SaaS company that provides software for senior living communities. The Senior Software Engineer, Platform (Developer Experience) will build developer environments, CI/CD pipelines, AWS infrastructure, and tooling that helps engineering teams develop, test, deploy, and operate software efficiently and securely.
Responsibilities
- Replace shared, slow-to-provision environments with ephemeral ones an engineer can stand up on demand, and solve the multi-tenant test data seeding that makes them realistic enough to trust
- Cut local build and test times
- Establish golden paths: opinionated, documented ways to build, test, and run a service, so the answer to "how do I start" is one page and one command
- Get us building an artifact once and promoting it across environments instead of rebuilding for each one, and give engineers a feature flag system they trust enough to pull deploy and release apart
- Make dependency scanning, secrets detection, and static analysis default steps on every build, and move teams onto a common pipeline as we consolidate
- You'll write the AWS and infrastructure-as-code that your tooling and our environments run on, working alongside the cloud engineers who own our production footprint, and carry the pager for what you build
- You'd own pieces of what closes that gap: deterministic builds, test feedback fast enough to stay inside the loop, sandboxed execution, review gates for agent-authored changes, and platform capabilities exposed to agents through MCP
Skills
- You've built and run production AWS infrastructure and expressed it as code, with Terraform, CDK, Pulumi, or CloudFormation. Networking, IAM, and container workloads are things you've configured yourself, and you've carried a pager for infrastructure other engineers depended on
- You've built or substantially rebuilt a CI/CD system that other engineers ship through, and you can say what got faster and how you measured it. Running a pipeline someone else designed isn't the same job
- You've made a real system runnable outside production, whether that's ephemeral environments, test data for a multi-tenant application, or containerized local development that engineers besides you actually ran
- Name a tool or service you wrote that other engineers used every day, and what it did for them. Much of this job is software
- You've built something for engineers outside your own team, and you can talk about both a time it worked and a time nobody adopted it
- You've moved other engineers along in how they use AI. It's already how you work yourself, and you know where it holds up and where it needs a human check. We expect our engineers to advocate for this
- Feature flag platforms and progressive delivery
- Kubernetes or ECS at production scale
- Observability built on OpenTelemetry, distributed tracing, or structured logging, especially where the data itself is sensitive
- HIPAA-regulated or other compliance-sensitive environments
- Bitbucket Pipelines, Jenkins, Azure DevOps, or GitHub Actions
- Test automation frameworks, or contract testing in an event-driven system
- Building alongside a legacy platform mid-migration, without the luxury of waiting for it to finish
- Node and TypeScript, internal developer portals, MCP servers
Company Overview
Company H1B Sponsorship