Site Reliability Engineer - Night Shift

b.well Connected Health is transforming how healthcare consumers find and receive care through a personalized healthcare data platform and mobile applications. The Site Reliability Engineer will build and operate a reliable, secure, and efficient AWS-based platform orchestrated on EKS, while managing reliability practices, observability, infrastructure automation, and external technical advocacy.

Responsibilities:

• Build and operate a reliable, secure, and efficient platform for the b.well network, running entirely on AWS and orchestrated on EKS
• Treat reliability as an engineering discipline — define and manage SLIs, SLOs, and error budgets rather than firefighting
• Champion automation as a core value, from infrastructure reliability to scaling
• Represent b.well's engineering work externally through blogging, speaking, and industry events, and help set the bar for automation across the team

Requirements:

• Deep in the penguin. Whatever your flavor of Linux, you know it cold—from kernel knobs to networking internals
• Terraforming isn't just sci-fi—it's how you build infrastructure (Terraform, OpenTofu, or Pulumi). Infrastructure-as-code is the only way you'd have it
• Git is the source of truth. GitOps is core to how we operate—infrastructure, deployments, and config all flow through code and version control (Terraform, Argo, Helm). If something can only be done through ClickOps, you see it as a gap to remediate, not a shortcut to take
• RFC isn't just three letters to you. Networking, DNS, firewalls, TLS—the fundamentals are, well, fundamental
• Watson, is that you? You're a relentless troubleshooter who can chase a problem across services and layers until it confesses
• Be Awesome. People come to you with problems while they're frustrated. You meet them with patience, clarity, and a fix—and you explain the WHY, not just the what
• Kubernetes is home turf. You've run real production workloads on it (EKS ideally), packaged with Helm, and understand what's happening below kubectl apply
• Cloud native, literally. Strong AWS experience—or equivalent depth in GCP/Azure that you can bring across
• Observability is second nature. You've run distributed monitoring in a microservices world (Grafana, Datadog, or similar) and can turn a wall of metrics into an actual answer. Our ingest is OpenTelemetry-based with some Prometheus in the mix, so love for either is a real plus
• Security-minded by default. You think about compliance and least privilege before anyone makes you—bonus if you've worked in a HIPAA, HITRUST, or SOC 2 environment, since we live in healthcare
• An open source citizen. We love the community and would love for you to contribute back to it
• Hands-on OpenTelemetry instrumentation experience
• HIPAA / HITRUST / SOC 2 or other regulated/compliance experience
• Meaningful open source contributions to infrastructure tooling