Job Description

About the Role

n

n

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.

n

n

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

n

n

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.

n

n

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.

n

n

Role purpose

n

n

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

n

n

Key accountabilities

n

n

The Technology Architect – Integration is accountable for:

n

n

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

n

n

Key responsibilities

n

n

1. Build a Modern, Simplified Integration Foundation

n

n

n




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

n

n

2. API‑First and Event‑Driven Integration Patterns

n

n

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

n

n

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

n

n

n
- Ensure integration patterns enable AI and analytics solutions by supporting:
n
- trusted, governed enterprise data flows
n
- consistent event and API patterns
n
- minimised data duplication and reconciliation effort
n
- 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).
n

n

n

4. Security, Resilience and Operability by Design

n

n

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

n

n

5. Cross‑Domain Enablement & Enterprise Coherence

n

n

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




- Ensure integration choices support clean‑core discipline and enterprise interoperability to avoid rework and disruption.
n

n

n

6. Integration Governance & Architecture Assurance

n

n

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

n

n

7. Standards, Playbooks and Community Contribution

n

n

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

n

n

What good looks like

n

n

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

n

n

Qualifications & experience

n

n

Essential

n

n

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

n

n

Preferred

n

n

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

n

n

Skills & capabilities

n

n

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

n

📌 Technology Architect (Punjab)
🏢 SISL Global
📍 Punjab