Sr. Site Reliability Engineer

Optura.AI is healthcare’s AI orchestration platform, aiming to transform disconnected AI pilots into a unified program that delivers measurable value. The Senior Site Reliability Engineer will be responsible for designing, building, and operating the core services of Optura’s AI Platform, ensuring reliability, performance, and security in healthcare environments.

Responsibilities:

• Architect and own Optura's multi-cloud infrastructure across AWS, GCP, and Azure — provisioning, networking, identity, observability, and cost governance
• Design and operate Kubernetes platforms that run consistently across our cloud environments and inside customer environments, including BYOC and on-prem (potentially air-gapped) deployments
• Build a unified deployment framework so Optura ships the same product to SaaS, BYOC, and on-prem customers without bespoke per-customer engineering — Helm charts, operators, install/upgrade tooling, and release pipelines
• Own SLOs, capacity planning, incident response, and postmortems across the entire infrastructure stack; set the bar for operational readiness
• Drive reliability and performance through error budgets, chaos testing, latency optimization, and disciplined runbook quality
• Harden the platform for regulated deployments — HIPAA controls, tenant isolation, audit logging, RBAC, KMS, and secrets rotation
• Lead the build-out of IaC, GitOps, and progressive delivery (Terraform, Argo CD, Crossplane) as the team's standard
• Partner with engineering and security to set opinionated guardrails: golden paths, base images, policy-as-code, and CI/CD that the rest of the org adopts by default

Requirements:

• 8+ years operating production infrastructure, including 3+ years in a senior SRE, platform, or staff infrastructure role
• Deep Kubernetes expertise across managed (EKS, GKE, AKS) and self-managed/on-prem distributions — not just running it, but operating it at scale across heterogeneous environments
• Multi-cloud fluency across AWS, GCP, and Azure, with informed opinions on when to abstract vs. embrace cloud-native primitives
• Expert with Terraform (or Pulumi/Crossplane) and GitOps tooling
• Experience shipping infrastructure that runs in customer environments — packaging, install/upgrade UX, air-gapped artifacts, support escalation paths
• Strong networking, identity, and security fundamentals: VPC design, service mesh, mTLS, OIDC, KMS, secrets management
• Production observability ownership (Prometheus, Grafana, OpenTelemetry, distributed tracing) and on-call leadership
• A track record of writing real code — Go, Python, or similar — to extend the platform, not just configure it
• Experience shipping HIPAA-regulated workloads, including BYOC or air-gapped customer deployments
• Background with enterprise software delivery tooling (Replicated, Cluster API, Talos, Rancher, OpenShift)
• Built internal developer platforms (Backstage, golden paths) that measurably reduced lead time for an engineering org
• FinOps experience — driving meaningful cloud spend reductions through architecture, not just rightsizing
• AI/ML infrastructure exposure: GPU scheduling, model-serving stacks, inference autoscaling
• OSS contributions to infrastructure projects, or strong opinions formed running them at scale