Senior Site Reliability Engineer

b.well Connected Health is solving healthcare’s fragmentation problem with their FHIR-based health data management platform. As a Senior Site Reliability Engineer, you will ensure the reliability, security, and efficiency of the platform, focusing on automation and performance in a cloud-based environment.

Responsibilities:

• Let the robots do the work! Drive down toil by automating everything—infrastructure provisioning, deployments, monitoring, and disaster recovery. Reliability at scale isn’t something you do by hand
• Run the fleet. We’re all-in on AWS and orchestrate everything on EKS. You’ll keep Kubernetes humming—scaling, upgrades, and all the sharp edges in between
• Python, Go, Bash—pick your poison. The team ships in all three. We care more about clean, reliable automation than which one you reach for
• Define what “reliable” means and hold the line on it. SLIs, SLOs, error budgets, incident response, and blameless postmortems—so there are steadily fewer 3am pages for everyone
• Like the Eye of Sauron, you’ll keep watch. Build the dashboards, alerts, and SLOs that catch problems before our customers ever notice
• CI/CD is your love language. Keep our GitHub Actions pipelines fast, safe, and boring in the best possible way
• New platform, who dis? Design and build new solutions that move the business forward—then pass the knowledge on to your peers
• Must feed, water, and provide high-fidelity, low-friction platform tooling to engineers to keep them happy and shipping
• Write the ancient artifacts of documentation—runbooks, policies, and procedures—so your peers (and future you) know how the environment actually works
• Share the on-call load. This role includes an on-call rotation for a production healthcare platform. A big part of the job is making on-call suck less through better automation and smarter alerting
• Get paid to be curious. You like reading about the latest tech and trying it out? Come do it here—and blog, speak, and share what you learn

Requirements:

• Deep in the penguin. Whatever your flavor of Linux, you know it cold—from kernel knobs to networking internals
• 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
• 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
• 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
• 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
• 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
• 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
• Hands-on OpenTelemetry instrumentation experience
• HIPAA / HITRUST / SOC 2 or other regulated/compliance experience
• Meaningful open source contributions to infrastructure tooling