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 current 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.

Position Summary (Purpose of Job) The Lead Infrastructure Architect defines and governs enterprise infrastructure architecture across hybrid and public cloud, compute, virtualization, storage, data protection, data center and colocation services, identity foundations, resilience, supporting platform services, and the connectivity dependencies required to support compute and platform workloads. The role establishes target-state architectures, reference patterns, standards, and multiyear roadmaps that improve reliability, security, scalability, cost efficiency, operational performance, and business agility.

Operating with the highest level of autonomy, the Lead Infrastructure Architect partners with enterprise architecture, cybersecurity, engineering, operations, application teams, service owners, and business stakeholders to evaluate technology options, guide workload-placement decisions, validate infrastructure designs, and lead migration planning from current-state platforms to strategic target architectures. The role provides final infrastructure architecture recommendations and governs exceptions through established architecture decision forums.





The role provides technical leadership for enterprise transformation initiatives, including hybrid-cloud adoption, platform modernization, legacy retirement, data center and colocation evolution, resilience improvement, technical debt reduction, and M&A; integration or separation. The architect translates complex technical options into clear business decisions by articulating value, cost, risk, dependencies, operational impact, and implementation tradeoffs for technical and nontechnical leaders.

Key Responsibilities

Set infrastructure strategy and roadmaps.

Define target-state architectures and multiyear roadmaps across cloud, compute, virtualization, storage, backup and recovery, connectivity dependencies for compute and platform workloads, colocation, and shared infrastructure platform services. Align roadmaps across infrastructure, security, application, and enterprise architecture domains.

Establish workload-placement direction.

Define decision principles for placing workloads across public cloud, private cloud, on-premises, colocation, and distributed infrastructure based on business criticality, security, performance, resilience, regulatory requirements, cost, latency, and operational supportability.

Design end-to-end infrastructure solutions.

Translate business and technical requirements into logical and physical infrastructure architectures.



Validate capacity, performance, availability, recovery, security, observability, automation, and supportability for high-impact initiatives.

Lead infrastructure modernization.

Provide architecture leadership for hybrid-cloud adoption, virtualization modernization, platform consolidation, data center and colocation transitions, technology currency, and legacy-platform retirement. Define transition states, migration waves, dependencies, and risk controls.

Govern standards and exceptions.

Own infrastructure reference architectures, approved patterns, technology standards, architecture decision records, and design-assurance criteria. Lead enterprise quality reviews and manage exceptions through the appropriate governance forums.

Drive resilience and recovery architecture.

Define patterns for high availability, backup, disaster recovery, cyber recovery, geographic redundancy, and service continuity. Ensure designs align to service-level objectives, recovery-time and recovery-point objectives, failure-domain requirements, and recovery-testing expectations.

Direct implementation and operational transition.

Guide engineering teams through implementation and modification activities, resolve complex cross-platform design issues, and ensure solutions are deployable, observable, supportable, testable, and sustainable in steady-state operations.

Institutionalize well-architected practices.

Embed security, reliability, performance efficiency, cost optimization, sustainability, and operational excellence into infrastructure designs. Establish architecture KPIs and OKRs and recommend adjustments that accelerate measurable value.

Optimize c

📌 Lead, Infrastructure Architect (Ahuntsic)
🏢 McKesson
📍 Ahuntsic