Integration Architect #1

Integration Architect #1

Full-Time 70000 - 90000 £ / year (est.) No working from home possible
Gsk

At a Glance

  • Tasks: Design and govern integration architecture for seamless data flow across the enterprise.
  • Company: Join Haleon, a purpose-driven consumer health company with a trusted brand portfolio.
  • Benefits: Enjoy competitive salary, inclusive culture, and opportunities for professional growth.
  • Other info: Be part of a dynamic team focused on innovation and collaboration.
  • Why this job: Make a real impact by shaping the future of health technology and AI solutions.
  • Qualifications: Experience in integration architecture and strong API knowledge required.

The predicted salary is between 70000 - 90000 £ per year.

Welcome to Haleon. We’re a purpose-driven, world-class consumer company putting everyday health in the hands of millions. In just three years since our launch, we’ve grown, evolved and are now entering an exciting new chapter – one filled with bold ambitions and enormous opportunity. Our trusted portfolio of brands – including Sensodyne®, Panadol®, Advil®, Voltaren®, Theraflu®, Otrivin®, and Centrum® – lead in resilient and growing categories. What sets us apart is our unique blend of deep human understanding and trusted science.

Now it’s time to fully realise the full potential of our business and our people. We do this through our Win as One strategy. It puts our purpose – to deliver better everyday health with humanity – at the heart of everything we do. It unites us, inspires us, and challenges us to be better every day, driven by our agile, performance-focused culture.

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 systems 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

  • 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/authorisation, encryption, auditability 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, standardised 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.

Equal Opportunities

Haleon are committed to mobilising our purpose in a way that represents the diverse consumers and communities who rely on our brands every day. It guides us in creating an inclusive culture, where different backgrounds and views are valued and respected – all in support of understanding and best serving the needs of our consumers and unleashing the full potential of our people. It’s important to us that Haleon is a place where all our employees feel they truly belong.

During the application process, we may ask you to share some personal information, which is entirely voluntary. This information ensures we meet certain regulatory and reporting obligations and supports the development, refinement, and execution of our inclusion and belonging programmes that are open to all Haleon employees. The personal information you provide will be kept confidential, used only for legitimate business purposes, and will never be used in making any employment decisions, including hiring decisions.

Adjustment or Accommodations Request

If you require a reasonable adjustment or accommodation or other assistance to apply for a job at Haleon at any stage of the application process, please let your recruiter know by providing them with a description of specific adjustments you are requesting. We’ll provide all reasonable adjustments to support you throughout the recruitment process and treat all information you provide us in confidence.

Note to candidates

The Haleon recruitment team will contact you using a Haleon email account (@haleon.com). If you are not sure whether the email you received is from Haleon, please get in touch.

Integration Architect #1 employer: Gsk

At Haleon, we pride ourselves on being a purpose-driven employer that champions everyday health through innovation and collaboration. Our agile, performance-focused culture fosters an inclusive environment where employees are empowered to grow and contribute to meaningful projects that impact millions. With a commitment to employee development and a strong focus on work-life balance, Haleon offers a unique opportunity to be part of a dynamic team dedicated to shaping the future of health.

Gsk

Contact Details:

Gsk Recruitment Team

StudySmarter Expert Advice🤫

We think this is how you could land Integration Architect #1

Join Local Tech Meetups

Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Gsk or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!

Contribute to Open Source Projects

Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Gsk.

Tap into Online Developer Communities

Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Gsk.

Explore Job Boards Specifically for Tech Roles

Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Gsk that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!

We think you need these skills to ace Integration Architect #1

Integration Architecture
API-First Integration
Event-Driven Architecture
Enterprise Integration Patterns
Security Design
Resilience and Operability
Data Flow Management

Some tips for your application 🫡

Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.

Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Gsk.

Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Gsk and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!

Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!

How to prepare for a job interview at Gsk

Brush Up on Your Coding Skills

For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.

Know Your Tools and Frameworks

Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Gsk uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.

Showcase Your Projects

Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.

Prepare for Behavioural Questions

While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.