Sr. Manager, Site Reliability

About This Opportunity

Omnicell is building a Global Cloud Operations organization from the ground up as our business shifts from on-premise, hardware-centric products to a cloud-native, SaaS-delivered platform that hospitals depend on 24/7. The Site Reliability Engineering function is the reliability engine of that organization, and this role is the first senior SRE hire — the person who will design the practice, set the standards, and then run the plays themselves until the team is large enough to delegate.

• Define and publish SLOs and SLIs for the top 5–10 Tier-1 customer-facing services, in partnership with Product and Engineering.
• Establish error budget policy and the enforcement mechanism when budgets burn.
• Design the incident command structure: severity rubric, declaration criteria, war-room protocol, stakeholder communication cadence, and the postmortem template.
• Select and stand up the primary observability platform, preferring extension of existing Omnicell contracts (DataDog, IBM/Instana, Prometheus/Grafana, OpenTelemetry, or other tooling already in use) over net-new procurement.
• Define the instrumentation standards all new services must meet.
• Partner with the VP to migrate the interim incident response RACI — currently held by matrixed individuals across IT, Engineering, Support, and Enterprise Security — into a durable SRE-owned model.
• Develop and track operational KPIs — MTTR, SLO attainment, change-failure rate, recurrence, cost per workload — and present reliability metrics and improvement roadmaps to senior leadership in the monthly Cloud Ops executive review.
• Instrument Tier-1 services yourself. Write the dashboards. Write the alerts. Write the runbooks. Do not wait for the team to grow before the work starts.
• Take the pager. Commander Sev-1 and Sev-2 incidents until a broader on-call rotation is staffed. Lead blameless postmortems and drive follow-up work to resolution.
• Contribute code and infrastructure-as-code (Terraform preferred; Chef/Puppet acceptable) to the platform.
• Work with Enterprise Security, Compliance, and Architecture to ensure platform services meet regulatory and security requirements in a healthcare environment.

What you will own

• Reliability practice (the coach half): Define and publish SLOs and SLIs for the top 5–10 Tier-1 customer-facing services, in partnership with Product and Engineering. Establish error budget policy and the enforcement mechanism when budgets burn. Design the incident command structure: severity rubric, declaration criteria, war-room protocol, stakeholder communication cadence, and the postmortem template. Train the first cohort of incident commanders across Engineering and Support. Select and stand up the primary observability platform, preferring extension of existing Omnicell contracts over net-new procurement. Define the instrumentation standards all new services must meet. Partner with the VP to migrate the interim incident response RACI into a durable SRE-owned model. Establish the on-call rotation model, including fair distribution, compensation approach, paging discipline, and the handoff protocol with our existing managed services partners (IBM, HCL) who provide L1/L2 coverage. Develop and track operational KPIs — MTTR, SLO attainment, change-failure rate, recurrence, cost per workload — and present reliability metrics and improvement roadmaps to senior leadership in the monthly Cloud Ops executive review.
• Hands-on engineering (the player half): Instrument Tier-1 services yourself. Write the dashboards. Write the alerts. Write the runbooks. Do not wait for the team to grow before the work starts. Take the pager. Commander Sev-1 and Sev-2 incidents until a broader on-call rotation is staffed. Lead blameless postmortems and drive follow-up work to resolution. Contribute code and infrastructure-as-code (Terraform preferred; Chef/Puppet acceptable) to the platform. Administer and scale our Kubernetes platform, including secure and compliant cluster configurations. Work with Enterprise Security, Compliance, and Architecture to ensure platform services meet regulatory and security requirements in a healthcare environment.

Required Knowledge And Skills

• Proven experience leading SRE, DevOps, or platform engineering teams in a cloud-native production environment — with demonstrated experience building a practice from zero or near-zero: you have set SLOs, defined incident command, and introduced error budget thinking to an organization that did not have it.
• Deep hands-on expertise with at least one major public cloud (AWS, Azure, or GCP), including networking, IAM, and managed services.
• Strong background in CI/CD pipeline design and management (familiarity with CodeFresh, GitHub Actions, Jenkins, TeamCity, or equivalent).
• Experience implementing Infrastructure as Code using Terraform (preferred), Chef, Puppet, or similar tools.
• Proficiency in Python or another object-oriented programming language for automation, tooling, and production services.
• Experience administering and scaling Kubernetes clusters, including secure and compliant platform configurations. Working knowledge of Docker, Helm, and Service Mesh technologies (Istio, Linkerd).
• Hands-on experience designing modern observability platforms using tools such as DataDog, Prometheus, Grafana, OpenTelemetry, Elasticsearch/Kibana, or equivalent — with an opinion about what a good telemetry stack looks like.
• Familiarity with integrating AI/ML-based anomaly detection, alerting, or LLM-assisted triage pipelines — or strong conviction about where AIOps should and should not be applied in a regulated environment.
• Real incident command experience for customer-impacting Sev-1 events, with blameless postmortem practice and documented follow-up discipline.
• Ability to coach and mentor, with direct evidence of growing junior and mid-level engineers.
• Comfort operating in a regulated environment where reliability and compliance (HIPAA, SOC 2) are inseparable.
• Excellent communication and stakeholder management skills; ability to translate complex technical concepts for non-technical audiences.

Basic requirements

• Bachelor's degree in Computer Science, Engineering, or a related technical field OR equivalent experience.
• 8+ years of experience in software or platform engineering, with at least 4 of those in an SRE, DevOps, or platform reliability role.
• Proven Experience advising and influencing senior technical or operations leaders using data driven recommendations.
• At least 2 years of formal technical leadership, tech-lead, or staff-level experience with mentorship responsibilities.

Preferred Knowledge And Skills

• Masters Degree.
• Prior experience in healthcare, clinical workflows, or another regulated vertical.
• Experience transitioning from MSP-heavy operations to internal-first, or integrating managed service providers (IBM, HCL, or similar) into an SRE operating model.
• Exposure to hybrid hardware-plus-cloud products, where device reliability and cloud reliability are jointly owned.
• Experience building or integrating AIOps platforms for automated incident triage and remediation.
• Familiarity with large language model APIs or agentic AI frameworks applied to on-call automation or runbook generation.
• Experience deploying and managing stateful distributed services in Kubernetes.
• Hands-on experience with security scanning and intrusion detection systems in regulated environments (HIPAA, SOC 2, or equivalent).
• Experience with messaging systems such as Kafka or RabbitMQ.
• Familiarity with chaos engineering principles and tooling (Chaos Monkey, LitmusChaos, or similar).
• Working knowledge of Databricks, Team Foundation Server, Octopus Deploy, or similar tools in Omnicell's current stack.
• Experience with FinOps practices and cloud cost optimization strategies.