Senior Software Engineer, Platform (DevOps)

ECP is a market-leading SaaS solution that helps senior living communities care for residents and improve clinical, business, compliance, and operational performance. The Senior Software Engineer, Platform (DevOps) will own production infrastructure on AWS, automate provisioning and operations, improve security and observability, support on-call operations, and enable delivery teams through self-service tooling and documentation.

Responsibilities:

• You'd own a defined set of production systems: designing them, writing the infrastructure code, operating them, and carrying the pager for them. That includes the routine work. Patching, runtime upgrades, certificate rotation, and adding capacity before a customer hits a limit are all part of the job, and we want as much of it automated as you can manage
• Security on those systems is yours as well. IAM and least privilege, rotating credentials and keys, keeping images patched, and building controls so they produce their own audit evidence
• The biggest thing we want from you in the first year is observability the delivery teams can use on their own
• They need traces, metrics, and logs they can read without asking us, and because resident data can't be in what they see, this is more of a design problem than a purchasing one
• The rest of the job is working with the delivery teams directly
• When a team needs a queue, a new service, a database, or an environment that behaves like production, we want you in that conversation early, before it turns into a ticket
• Common requests should end up in the provisioning framework so they stop being requests
• And write things down. Too much of how this estate runs lives in one or two people's heads, and runbooks and documentation count as real work here

Requirements:

• Production infrastructure on AWS that you built as code and kept running. CloudFormation, Terraform, CDK, or Pulumi, we don't mind which
• Networking and IAM you designed yourself: VPCs, cross-account access, and keeping one workload's data isolated from another's
• Containers in production on ECS or Kubernetes, including the deployment strategy and the capacity decisions
• Hands-on security work on infrastructure you ran: least privilege, credential rotation, patching on a cadence
• Producing evidence for an audit, whether SOC 2, HIPAA, ISO, or PCI, ideally by automating it rather than assembling it by hand at the end
• You've been on call for something other teams depended on, and you can walk us through an incident you handled from start to finish
• You've used AI in an operational workflow, for triage, correlating alerts, running runbooks, or drafting incident writeups, and you can say what it changed
• You've built observability that other engineers used to debug their own systems, in an environment where log contents were sensitive
• You've cut the requests coming to your team by making things self-service, and you write runbooks that people other than you use
• You write real code, in Python, Bash, Go, or whatever your infrastructure is in. Much of this job is software
• 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
• Running a production database, with restores and failover you've exercised yourself
• A migration between AWS accounts or architectures done without downtime
• Cost work: reserved capacity, savings plans, enterprise agreements
• Healthcare or another regulated industry