Sr Director, Shared Capabilities & Engagement Experience

McKesson•Columbus, OH

3d•Hybrid

About The Position

McKesson is an impact-driven, Fortune 10 company that touches virtually every aspect of healthcare. We are known for delivering insights, products, and services that make quality care more accessible and affordable. Here, we focus on the health, happiness, and well-being of you and those we serve – we care. What you do at McKesson matters. We foster a culture where you can grow, make an impact, and are empowered to bring new ideas. Together, we thrive as we shape the future of health for patients, our communities, and our people. If you want to be part of tomorrow’s health today, we want to hear from you. CoverMyMeds is building the platform and services that will power the next generation of healthcare automation, real-time prior authorization, and partner connectivity at scale. The Sr Director, Shared Capabilities & Engagement Experience is a new role that owns the full developer engagement surface, both inside and outside the organization, and leads the engineering teams responsible for the foundational shared services that everything else runs on. You will own three interconnected workstreams: The Shared Platform Capabilities (Kafka event streaming, API surface, automation tooling, and configuration services) that CMM product teams build on top of; The Subscription Portal , an external developer portal giving partners self-service onboarding as well as automating and standardizing direct partner integrations; and the Internal Developer Portal , a self-service experience for CMM engineers covering Golden Path onboarding, service catalog, and tooling discoverability. This role is for an engineering leader who thinks in terms of platforms as products, who treats GitOps not as a deployment preference but as the operational backbone, and who sees AI-native automation as the default rather than an enhancement. If you believe the most important thing a platform can do is eliminate toil, you will find this role compelling.

Requirements

Degree or equivalent experience and typically requires 13+ years of relative software engineering with significant experience leading platform engineering, shared services, or developer experience teams at scale, and 6+ years of diversified leadership, planning, communication, organization and people motivation skills
Demonstrated track record of building platforms that are adopted by multiple product teams, not just built and handed off.
Deep fluency in GitOps principles and tooling (Infrastructure as Code, Terraform) and the conviction to make them the operating standard, not just a preference.
Experience building or operating internal developer portals (Backstage, Port, Cortex, or equivalent) and external developer-facing API products.
Strong distributed systems and event streaming background; Kafka or Confluent Platform experience at production scale.
Experience leading and developing engineering managers, not just engineers.
Proven ability to operate in a matrixed enterprise environment with shared infrastructure dependencies (similar to McKesson Technology or equivalent).
Clear, executive-level communication skills; comfortable presenting roadmaps, trade-offs, and investment asks to senior leadership.

Nice To Haves

Experience designing or building production-grade AI-native platforms, including agentic workflows, AI-assisted developer tooling, or LLM-integrated platform services.
Background in healthcare technology, regulated environments, or high-trust systems with compliance requirements (HIPAA, SOC 2, HITRUST).
Hands-on experience with Azure, AKS, and the Azure-native platform ecosystem.
Familiarity with SAFe or other scaled agile frameworks in a large engineering organization.
Experience building external developer portals or API marketplaces for partner ecosystems.
Exposure to prior authorization, pharmacy, or healthcare interoperability (FHIR, NCPDP, HL7) is a meaningful plus.

Responsibilities

Drive the API surface management strategy across CMM product teams, including standards, versioning, lifecycle governance, and NFR enforcement.
Build, support and evolve common service API’s that all teams utilize.
Own and evolve the Confluent Kafka event streaming platform, including schema governance, consumer SLAs, and multi-region reliability.
Provide leadership oversight for the Integrations team with key network customers and stakeholders.
Build the operating model for a unified external engagement surface that eventually connects partner connectivity, Subscription Portal, and shared API services under one coherent strategy.
Build and operate a self-service external subscription portal where partners onboard, provision API credentials, browse documentation, and integrate with CMM systems without requiring custom internal engagement.
Define the partner integration lifecycle from initial discovery through production onboarding, supported by automation and AI-assisted tooling at every step.
Own the roadmap for the Subscription Portal product in partnership with the Platform Technical Product Owner and external partner teams.
Instrument partner adoption, time-to-first-call, and integration health as primary success metrics for this workstream.
Own the Internal Developer Portal as a product, covering service catalog, Golden Path templates, onboarding automation, and tooling discoverability for CMM engineers.
Drive adoption by making the portal the single pane of glass for developer context, from service ownership to deployment state to security posture.
Integrate AI agents into the portal as first-class users: by 2027, agent-driven interactions with internal developer portals are projected to outnumber human ones. Build for both audiences from day one.
Partner with Core Platform and Reliability on Golden Path standards so the portal reflects the actual platform capabilities, not aspirational documentation.
Design every shared service and portal with AI augmentation as the baseline, not an add-on. Automated onboarding, AI-assisted integration support, intelligent routing, and self-healing pipelines are table stakes here.
Build agentic workflows into the Subscription Portal and Internal Developer Portal so that routine actions (credential provisioning, environment setup, runbook execution) require no human in the loop.
Require GitOps as the source of truth for all infrastructure, configuration, application state, and portal content. Every change is a pull request. Every environment is reconciled from Git. Drift is an incident.
Champion AI-assisted engineering tooling (Claude Code, GitHub Copilot, and emerging agentic platforms) within your teams and across CMM technology, and help define the engineering standards for how CMM uses AI to build software.
Define and own the multi-year strategy for shared platform capabilities, developer portals, and partner engagement experience at CMM.
Translate complex infrastructure and product decisions into clear executive communication and roadmap narratives.
Partner with the Shared Products and Capabilities product team to align engineering capacity against the FY27 roadmap and DC exit commitments.
Define build, buy, and partner decisions across the portal and shared services stack with a strong bias toward owned, automated solutions over vendor dependency.
Lead and develop two high-performing engineering teams across multiple disciplines.
Establish engineering excellence standards for your org: test-first development, GitOps-first delivery, AI-native tooling, and production-grade observability from day one.
Drive DORA metrics (deployment frequency, change failure rate, mean time to recovery) as primary health indicators for your teams.
Build a culture where engineers are empowered to own outcomes, automate their own toil, and contribute to platform standards across CMM.
Partner with Core Platform and Reliability on AKS, GitOps pipelines, and multi-region shared service architecture.
Coordinate with Product Security on API security posture, WAF standards, and external partner trust models.
Collaborate with McKesson Technology (MT) on Alkira networking, DNS, firewall provisioning, and Kafka private endpoint dependencies that affect shared platform reliability.
Represent the platform's external engagement surface in SAFe PI Planning, ART sync, and executive program reviews.