About the Role
Join a 13-person delivery team as the MuleSoft Solution Architect on a 15-week modernisation programme for a global insurance client. You will define the upgrade architecture for 81 MuleSoft APIs moving from Mule 4.6 to Mule 4.9.2 on Java 17, design wave-level cluster cut-overs, and govern technical decisions across the delivery team.
Key Responsibilities
- Upgrade Strategy: Define the Mule 4.6 to 4.9.2 and Java 17 upgrade approach and approve the pilot runbook.
- Dependency Mapping: Build the dependency matrix for connectors, modules, and custom Java across all 81 repositories.
- Remediation & Escalations: Establish common remediation patterns and escalate connector replacement decisions to the client.
- Cut-over Architecture: Design the cluster cut-over strategy (in-place or parallel 4.9 clusters) and backout plan for each wave.
- Mobilization & Sizing: Validate the complexity of XL and 2XL APIs during mobilization and rebaseline the plan as needed.
- Quality Governance: Review samples of upgraded APIs and approve technical exceptions, such as JVM workarounds.
Requirements
- 9+ years of enterprise integration experience, including proven leadership as a MuleSoft Solution Architect.
- Deep expertise in Mule 4.x runtime upgrades (Mule 4.9.x / Java 17), cluster architectures, and JVM troubleshooting.
- Track record of managing large-scale API dependency mapping, remediation patterns, and zero-downtime cut-over/backout designs.
- Strong client-facing communication skills for architectural escalations and stakeholder alignment.
Suggested Stack: MuleSoft, Mule 4.9, Java 17, Solution Architecture, JVM, Cluster Cut-over, API Governance
