Senior IT Architect (Enterprise Applications / Clinical Platforms)

About this role

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.

Role Summary

Ontadais an oncology data science and technology business dedicated to transforming the fight against cancer. We specialize in real-world data and evidence generation that accelerates life science research, clinical technologies that support community providers with precise care, and provider engagement channels that enable education and insights.

We are hiring anIT Architect to define and drive cloud-native integration architecture acrossOntadaproducts and partner ecosystems. This role owns solution and platform architecture for API-led connectivity, event-driven integration, and secure data exchange—ensuring our systems are scalable, reliable, observable, and straightforward to evolve. Familiarity with healthcare interoperability standards (HL7/FHIR, including SMART on FHIR) is a plus for certain partner pathways, but the primary focus is strong enterprise-architecture fundamentals applied to modern cloud-native integration models.

Success in this role is measured by the clarity and adoption of your reference architectures and standards, the reliability and scalability of the integration ecosystem you enable, and your ability to influence decisions across multiple initiatives while mentoring and elevating engineering teams. Familiarity with AI/ML and NLP capabilities used in products (e.g., LLM-enabled workflows, retrieval patterns, evaluation, and governance) is a plus asOntadaexpands intelligentexperiences, butis not the core requirement.

Technical Environment

Cloud-Native Integration:API-led connectivity, event-driven architecture, pub/sub, schema management, idempotency, retries, backpressure
APIs:RESTful services,OpenAPI/Swagger, API gateways, versioning and contract-first design
Messaging:Kafka (or equivalent), queues/streams, event schema design
Platform Patterns:Microservices, containerization (Docker), service discovery, configuration management; service mesh (where applicable)
Data & Performance:Oracle and relational databases; Redis (caching); Elasticsearch; analytics/pipelines (e.g., Databricks)
Interoperability (nice to have):HL7v2, FHIR (R4+), SMART on FHIR, OAuth2/OIDC, C-CDA
Observability:Logging, metrics, distributed tracing (e.g., Dynatrace)
Cloud & Platforms:Azure, AWS, GCP, Cloud Foundry
Engineering Practices:CI/CD, automated testing, code reviews, architecture documentation

Key Responsibilities

Architecture Leadership & Strategy

• Drive architecture for interoperability and integration capabilities across systems, services, and product offerings.

• Partner with Product Owners, Sales, Business Analysts, Quality Assurance, and Project Management to translate functional and non-functional requirements into target architectures and delivery plans.

• Define architecture standards, reference implementations, and guardrails for APIs, integration patterns, security, and operational readiness.

• Evaluate solution options and drive alignment across stakeholders; communicate tradeoffs, risks, and recommendations to technical and non-technical audiences.

• Providetechnical guidance to coach, motivate, and develop engineers and architects.

Cloud-Native Integration Architecture

• Define and governintegrationreference architectures across APIs, events, and asynchronous workflows (request/response, pub/sub, choreography vs. orchestration).

• Establish platform patterns and guardrails for API gateways, service-to-service communication, schema/version management, and contract testing.

• Design for resiliency and performance using proven patterns (timeouts, retries, circuit breakers, bulkheads, idempotency, caching) andalignto SLOs/SLAs.

• Guideevent-driven integration (e.g., Kafka or equivalent) with well-defined event schemas, lifecycle management, and operational controls.

• Collaborate with security and platform teams to ensure secure-by-default integration approaches (OAuth2/OIDC, least privilege,secretsmanagement, threat modeling).

Healthcare Interoperability (Optional) & Partner Integrations

• When applicable, drive design for healthcare data exchange leveraging HL7v2 and/or FHIR (R4+), including SMART on FHIR, to enable integrations with EMRs and partner systems.

• Partner with domain SMEs and external stakeholders to define interoperability expectations (security, conformance, and onboarding) and ensure integrations are scalable and supportable.

• Define API contracts, versioning strategy, and error taxonomy to enable predictable integrations for internal and external consumers.

• Partner with engineering teams to implement and evolve reusable integration components, adapters, and accelerators that reduce time-to-integrate.

Operational Excellence & Production Ownership

• Collaborate with engineering in release, sprint, and project planning to ensure delivery commitments are tracked and met across the SDLC.

• Demonstrate strong architectural ownership in production operations to address customer needs for support, issue analysis, enhancements, and corrective actions.

• Evolve software systems, infrastructure, and architecture to support growth, SLAs, availability, and continued operation.

• Drive operational readiness practices including observability, runbooks, incident response, and post-incident improvements.

• Resolve technical problems, issues, and escalations across delivery teams and project activities.

AI Enablement…