Staff Engineer (Site Reliability)
Babylist
- Ottawa, Canada
- Posted
This job is closed: the employer no longer lists it.
Skills
Required
- AWS
- EKS
- RDS
- cloud networking
- DNS
- CDNs
- load balancers
- CI/CD systems
- CircleCI
- GitHub Actions
- Kubernetes
- Datadog
- PagerDuty
Preferred
- Terraform
- AWS environment
- drive post-incident reviews
- close the loop
You will own the infrastructure and reliability practices that support over 9 million users and the engineers who build for them. This is not a maintenance role; you will actively evolve how we build and operate our AWS infrastructure, CI systems, and developer tooling. You will work cross-functionally across all of Babylist Engineering, and your decisions will have wide leverage.
About Babylist
- Babylist, a rapidly growing company that started as an e-commerce and registry platform and is now expanding into health, media, mobile, and new product surfaces.
- As a Staff Engineer (Site Reliability), you will be at the center of keeping our platform reliable, fast, and scalable.
- You naturally reach for AI in your work — at Babylist, every team uses AI daily. You're already using it to move faster and improve your output, and you stay curious about what's coming next
Responsibilities
- Infrastructure ownership — manage and evolve our AWS environment using Terraform, keeping EKS clusters, databases, and core services current and performant.
- CI/CD reliability — own the speed and reliability of our CI systems for the full Engineering org — every deploy starts here.
- Incident response — lead or support incident response, drive post-incident reviews, and close the loop so the same thing doesn't happen twice.
- Deep hands-on Terraform expertise — you own IaC, not just contribute to it
- Comfortable supporting developers across local, staging, and production — you're a resource, not a gatekeeper
Requirements
- Proven AWS experience at scale — EKS, RDS, cloud networking, DNS, CDNs, load balancers — you know the gotchas
- Comfortable designing and improving CI/CD systems — CircleCI, GitHub Actions, or similar; you care about developer velocity, not just pipeline uptime
- Experienced operating Kubernetes in production — you've debugged the hard stuff, not just deployed the easy stuff
- Strong observability instincts — Datadog, Sentry, PagerDuty, Cronitor — you build alerting that's actionable, not noisy
- Experienced with on-call and incident management — you've run the post-mortems and actually changed things afterward
