Integration Lead / Architect - Mulesoft

Role Purpose The Integration Lead / Architect is accountable for the end-to-end ownership of enterprise integration across a complex transformation programme. This includes both the hands-on architectural design of integration solutions and the governance, prioritisation, and delivery of integration workstreams. The successful candidate will ensure that all integrations are architecturally sound, reusable, secure, and delivered in alignment with programme timelines, business priorities, and enterprise standards. Key Responsibilities 1. Governance & Operating Model ▸     Define and operate the Integration Centre of Excellence(COE) operating model and intake process. ▸     Own the integration roadmap, delivery plan, and capacity plan across all workstreams. ▸     Manage escalations, blockers, risks, and cross-programme dependencies. ▸     Lead stage-gate design reviews from intake through to deployment. 2. Standards & Quality Assurance ▸     Set and enforce API standards, non-functional requirements (NFRs), naming conventions, design patterns, and integration best practices. ▸     Maintain the enterprise integration catalogue as the single source of truth. ▸     Review MuleSoft solution designs, RAML/API specifications, data mappings, security models, and deployment approaches. Architecture & Design ▸     Design scalable, reusable, and governed MuleSoft APIs and integrations aligned to enterprise architecture principles. ▸     Apply API-led connectivity principles, ensuring clear separation between System, Process, and Experience API layers. ▸     Define and maintain canonical data models and reusable integration patterns across the programme. 3.Stakeholder & Programme Engagement ▸     Work collaboratively with business, application, data, security, infrastructure, and delivery teams to align integration outcomes. ▸     Support estimation, planning, delivery governance, and release readiness for integration workstreams. ▸     Serve as the primary point of contact for integration architecture decisions across the programme. Must-Have Requirements 1. MuleSoft Integration Architecture Strong, demonstrable experience designing and delivering enterprise integrations using MuleSoft Anypoint Platform, including: –      API-led connectivity and reusable API design (System, Process, and Experience API layers). –      MuleSoft deployment patterns including CloudHub, Runtime Fabric, and on-premises deployments. –      Design and review of RAML/OAS API specifications, data transformation (DataWeave), and security models. –      Enterprise-grade non-functional requirements including performance, availability, andscalability. 2  |  Enterprise Integration Governance &Standards Ability to define, document, and enforce end-to-endintegration governance, including: –      API design standards, naming conventions, versioning strategies, and integration patterns. –      Integration catalogue management and reusable asset governance. –      Design authority participation and stage-gate review processes. –      Integration COE operating models, intake processes, and delivery governance frameworks. 3  |  Platform, Network & Security ArchitectureAlignment Ability to collaborate effectively with network, security, cloud, and infrastructure architects to ensure: –      The MuleSoft platform is correctly configured, secured, and aligned with enterprise standards. –      Network topology, firewall rules, DNS, TLS, and mTLS configurations are appropriate for integration workloads. –      Identity and access management (IAM), OAuth 2.0, and API security policies are correctly implemented. –      Cloud infrastructure (AWS, Azure, or GCP) is leveraged appropriately to support platform scalability. Good-to-Have Requirements 1. MuleSoft Certifications ▸     MuleSoft Certified Integration Architect (MCIA). ▸     MuleSoft Certified Platform Architect (MCPA). ▸     MuleSoft Certified Developer (MCD) – Level 1 or Level2. 2. Enterprise Architecture Experience ▸     Experience with TOGAF or equivalent enterprise architecture frameworks (Zachman, SABSA, etc.). ▸     Ability to articulate and align integration architecture decisions with broader enterprise architecture principles and roadmaps. ▸     Experience producing architecture artefacts: solution design documents, architecture decision records (ADRs), integration catalogues ,and capability maps. 3. DevOps & Operational Support Knowledge ▸     Experience with CI/CD tooling (Jenkins, GitHub Actions, Azure DevOps) for MuleSoft integration delivery. ▸     Knowledge of monitoring, logging, and alerting patterns for MuleSoft (Anypoint Monitoring, ELK, Splunk, Datadog). ▸     Familiarity with release management, runbooks, and supportability patterns for production integration workloads. ▸     Experience with infrastructure-as-code (Terraform, Ansible) for MuleSoft platform provisioning.