Technical Director, Global Cloud Operations

Technical Director, Global Cloud Operations Department: Global Cloud Operations Reports To: VP, Global Cloud Operations Location: Remote (U.S.) / Hybrid (Preferred) Travel: Up to 20% (Domestic and International) Why Join Omnicell? Global Cloud Operations is being built as four distinct but deeply interdependent pillars — Site Reliability Engineering, Site Reliability Operations, Platform Engineering, and Cloud Security. Each pillar has its own Director driving execution, but someone needs to hold the technical thread across all four: making sure architecture decisions in Platform Engineering don’t create blind spots for Cloud Security, that SRE’s reliability standards and SRO’s operational model reinforce each other, and that the organization makes coherent technical trade-offs rather than four good decisions that don’t add up to one good system. That’s this role. About This Opportunity Reporting to the VP of Global Cloud Operations, the Technical Director is the organization’s senior-most cross-pillar technical leader — a peer partner to the Directors of SRE, SRO, Platform Engineering, and Cloud Security, and the VP’s primary technical deputy. This is not a role that replaces any Director’s ownership of their pillar; it is the role that makes sure the four pillars operate as one coherent technical organization rather than four independent ones. Purpose The Technical Director owns technical coherence across Global Cloud Operations — setting unified architecture standards, resolving cross-pillar technical trade-offs, and ensuring that reliability, operations, platform, and security decisions are made with full visibility into their effects on each other. Primary Impact As Technical Director, your judgment will directly shape: Whether Omnicell’s four Cloud Operations pillars scale as one coherent technical organization or drift into four disconnected ones. The speed and safety with which cross-pillar technical decisions get made — instead of being escalated to the VP or stalling between Directors. The consistency of architecture, tooling, and technical standards across reliability, operations, platform, and security. The VP’s ability to focus on strategy and executive partnership, trusting that cross-pillar technical execution is in capable hands. What You’ll Do Cross-Pillar Technical Leadership Serve as the unifying technical authority across Site Reliability Engineering, Site Reliability Operations, Platform Engineering, and Cloud Security. Partner closely with all four Directors on architecture decisions, technical roadmaps, and major trade-offs that cross pillar boundaries. Identify and resolve technical inconsistencies before they become production risk — for example, platform provisioning patterns that don’t meet security baselines, or reliability targets that assume operational capabilities SRO hasn’t yet built. Architecture & Standards Governance Own the enterprise-wide technical standards that span all four pillars: observability conventions, incident severity definitions, infrastructure-as-code patterns, and security control baselines. Chair a recurring cross-pillar architecture review, ensuring major technical decisions in any one pillar are visible to the other three before they ship. Maintain a unified view of technical debt and risk across the organization, and prioritize it alongside each Director. Executive Technical Partnership Act as the VP’s primary technical deputy — translating cross-pillar technical detail into clear input for executive decisions, and translating VP strategy into technical direction the four Directors can execute against. Represent Cloud Operations in technical discussions with other engineering and product leaders across Omnicell. Support the VP in Sev1/Sev2 incident review when an incident’s root cause or resolution spans multiple pillars. Talent & Technical Mentorship Mentor senior technical leaders across all four pillars — Reliability Architect, Security Architect, Senior Platform Engineer, and equivalent senior ICs — independent of their reporting line. Help the four Directors develop their own technical judgment and cross-pillar awareness over time, so the need for centralized coordination naturally decreases as the organization matures. What Success Looks Like First 90 Days Build trusted working relationships with the VP and all four Directors. Map the current state of technical consistency (or inconsistency) across the four pillars — standards, tooling, architecture patterns. Identify the two or three highest-risk cross-pillar gaps and begin addressing them. First Six Months Cross-pillar architecture review established and running on a predictable cadence. At least one significant cross-pillar technical inconsistency resolved (e.g., unified observability standard, aligned incident severity model). Recognized by all four Directors as a trusted technical partner, not an added layer of approval. First Year Technical standards and architecture patterns are consistent and well-understood across all four pillars. Cross-pillar technical trade-offs are resolved at the Director/Technical Director level, rarely requiring VP escalation. Demonstrated measurable improvement in an organization-wide metric that depends on cross-pillar coordination — for example, reduced incident cross-talk, faster root-cause resolution for multi-pillar incidents, or improved audit readiness. Minimum Qualifications 10+ years in infrastructure, platform, reliability, or security engineering, with 5+ years in a senior technical leadership role spanning multiple technical disciplines. Demonstrated depth across at least two of the four pillars (SRE, operations, platform engineering, security) and working fluency in all four. Strong track record of resolving cross-team technical trade-offs and influencing without direct authority. Deep experience with multi-cloud architecture (AWS, Azure, GCP), modern observability practices, infrastructure-as-code, and cloud security fundamentals. Experience operating in a regulated industry (healthcare, financial services, or similar) with compliance obligations such as HIPAA, SOC 2, or FedRAMP. Preferred Qualifications Prior experience as a Principal Engineer, Distinguished Engineer, or cross-functional Technical Director in a scaling infrastructure organization. Experience building or formalizing an architecture review or technical governance process from scratch. Experience mentoring senior technical leaders across disciplines outside your own direct reporting line. Leadership Expectations As Technical Director, you will: Lead through technical credibility and relationship, not positional authority over the four Directors. Make and stand behind difficult cross-pillar technical trade-offs, clearly communicating the reasoning to all affected teams. Protect the organization from well-intentioned but locally-optimized decisions that create risk elsewhere in the system. Serve as a calm, technically rigorous voice in cross-pillar incident review and architecture discussions. How You’ll Elevate Cloud Operations Four strong pillars don’t automatically add up to one strong organization — that only happens with someone actively holding the technical thread between them. Your leadership is what turns Site Reliability Engineering, Site Reliability Operations, Platform Engineering, and Cloud Security from four well-run teams into a single, coherent, trustworthy cloud operations function.