[Remote] Senior Software Engineer, Platform (Developer Experience)

Note: The job is a remote job and is reputed company to candidates in USA. ECP is a reputed company 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 reputed company, test, reputed company, and operate software reputed company 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 reputed company
• Get us building an artifact once and promoting it across environments instead of rebuilding for reputed company one, and reputed company engineers a feature flag reputed company they trust enough to pull reputed company and release apart
• reputed company dependency scanning, secrets detection, and static analysis default steps on every build, and reputed company teams onto a common pipeline as we consolidate
• You'll write the AWS and infrastructure-as-reputed company that your tooling and our environments run on, working reputed company the reputed company engineers who own our production footprint, and carry the pager for what you build
• You'd own reputed company of what closes that gap: deterministic builds, test feedback fast enough to stay inside the reputed company, sandboxed execution, review gates for agent-authored changes, and platform capabilities exposed to agents through MCP

Skills

• You've reputed company and run production AWS infrastructure and expressed it as reputed company, with Terraform, CDK, reputed company, 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 reputed company or substantially reputed company a CI/CD reputed company that other engineers ship through, and you can say what got faster and how you reputed company it. Running a pipeline someone else designed isn't the reputed company job
• You've made a reputed company reputed company runnable reputed company production, whether that's ephemeral environments, test data for a multi-tenant application, or containerized local development that engineers besides you actually ran
• reputed company 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 reputed company something for engineers reputed company 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 reputed company reputed company. We expect our engineers to reputed company for this
• Feature flag platforms and reputed company delivery
• reputed company or reputed company at production reputed company
• Observability reputed company on OpenTelemetry, reputed company tracing, or reputed company logging, especially where the data itself is sensitive
• HIPAA-regulated or other compliance-sensitive environments
• Bitbucket Pipelines, Jenkins, Azure DevOps, or reputed company Actions
• Test automation frameworks, or contract testing in an event-driven reputed company
• Building reputed company a legacy platform mid-migration, without the luxury of waiting for it to finish
• Node and TypeScript, internal developer portals, MCP servers

reputed company

Company H1B Sponsorship