Technology Architect

About the Role

The Technology Architect – Integration is a hands‑on architecture role within Digital & Technology (D&T), accountable for designing and governing Haleon’s integration architecture foundation —the connective tissue that enables systems and data to flow reliably end‑to‑end across the enterprise.

Reporting into Technology Domain Architect, the role translates enterprise technology direction and standards into implementable integration patterns, reference architectures and delivery guidance .

The role’s central mission is to create a modern, simplified integration foundation that reduces point‑to‑point complexity and enables fast, safe change at scale.

The role also ensures integration is future‑proofed for data to flow seamlessly across the organisation , for system to connect and for AI : AI value depends on reliable, governed, timely data and interoperable systems. This role helps ensure integration choices enable AI and analytics solutions to scale without fragmentation, rework or hidden operational risk.

Role purpose

To design and govern a modern, simplified, secure and resilient integration foundation that enables scalable enterprise connectivity and future‑proofs Haleon’s data and systems for AI‑enabled solutions .

Key accountabilities

The Technology Architect – Integration is accountable for:

• Establishing and evolving Haleon’s enterprise integration foundation , reducing fragmentation and point‑to‑point complexity through standard patterns and common platform approaches.
• Defining and enforcing modern integration principles and patterns (e.g. API‑first, composability, reusability, resilience and governance by design ).
• Ensuring integration designs are secure by design and resilient by default , including operability, observability and recoverability.
• Future‑proofing integration choices to support AI effectiveness by enabling governed, timely, interoperable data flows and preventing fragmented AI pipelines.
• Providing integration architecture governance and implementation guidance to delivery teams throughout the lifecycle (design → build → deploy).

Key responsibilities

1. Build a Modern, Simplified Integration Foundation

• Design and maintain the enterprise integration reference architecture and guiding principles, ensuring teams have clear “how we integrate” standards.
• Drive simplification by reducing bespoke and point‑to‑point integrations through reusable patterns and shared integration services.
• Support convergence onto a coherent integration approach aligned to enterprise strategy and platform direction, avoiding duplicated tooling and inconsistent patterns.

2. API‑First and Event‑Driven Integration Patterns

• Define and govern API integration and event integration patterns that enable consistent, real‑time and composable enterprise processes.
• Provide practical design guidance to delivery teams on interface contracts, versioning, event schemas, error handling and operational considerations.

3. AI‑Ready Integration (Future‑Proofing for AI Effectiveness)

• Ensure integration patterns enable AI and analytics solutions by supporting:
• trusted, governed enterprise data flows
• consistent event and API patterns
• minimised data duplication and reconciliation effort
• Partner with data and AI teams to ensure integration design supports scalable AI enablement (so AI use cases can be industrialised rather than rebuilt repeatedly).

4. Security, Resilience and Operability by Design

• Embed authentication/authorization, encryption, audit-ability and control expectations into integration designs.
• Ensure resilience patterns exist: retries, idempotency, dead‑letter handling, graceful degradation, and clear monitoring/alerting expectations.
• Ensure integrations are production‑ready, supportable and observable.

5. Cross‑Domain Enablement & Enterprise Coherence

• Work closely with Domain Architects (Commercial, Corporate Functions, QSC/R&D, ERP) to ensure integration choices enable end‑to‑end value streams and do not create cross‑domain friction.
• Ensure integration choices support clean‑core discipline and enterprise interoperability to avoid rework and disruption.

6. Integration Governance & Architecture Assurance

• Provide integration assurance through design reviews, governance forums and delivery checkpoints.
• Maintain documentation of approved patterns, exceptions, risks and integration technical debt.
• Escalate systemic issues and recommendations through the Technology Domain Architect.

7. Standards, Playbooks and Community Contribution

• Create and continuously improve integration playbooks, templates and reference patterns for delivery teams.
• Contribute to architecture communities of practice, improving consistency and capability across D&T.

What good looks like

• Integration becomes simpler, standardized and reusable , with less point‑to‑point complexity.
• Delivery teams can integrate faster using clear patterns and guardrails.
• Data flows support enterprise reporting and AI initiatives without fragmentation or repeated rebuild.
• Integrations are secure, resilient, observable and operationally supportable.

Qualifications & experience

Essential

• Demonstrated experience as an Integration / Technology Architect in complex enterprise environments
• Strong expertise in API‑first integration, event‑driven architecture and enterprise integration patterns
• Experience designing for secure, resilient and operable production systems
• Proven ability to guide delivery teams through architecture governance and implementation decisions

Preferred

• Experience contributing to AI‑ready data and integration foundations (enabling scalable AI rather than isolated pilots)
• Experience operating within enterprise architecture standards and governance models at scale

Skills & capabilities

• Integration design mastery (APIs, events, messaging, data flows, error handling)
• Strong non‑functional design capability (resilience, observability, recoverability)
• Pragmatic “minimum viable architecture” mindset that accelerates delivery safely
• Clear communication and ability to influence engineering and delivery teams