About the Role
Serve as the Onshore MuleSoft Technical Lead and day-to-day technical contact for a global insurance client on a 15-week modernisation programme upgrading 81 MuleSoft APIs from Mule 4.6 to Mule 4.9 on Java 17. You will build the reference upgrade, set technical standards, review the work of eight offshore developers, and lead all production cut-overs with the client’s platform and release teams.
Key Responsibilities
- Pilot & Standards: Build the pilot upgrade across five representative APIs and author the upgrade runbook for the offshore team.
- Client Alignment: Lead daily technical working sessions with the client technical lead, API owners, and platform team.
- Code Reviews: Review pull requests from 3 senior and 5 MuleSoft developers against the upgrade checklist.
- Release & Cut-over: Plan and execute production cut-overs and backouts within the client’s change windows.
- Quality Sign-off: Verify that every API passes its Mule 4.6 vs. 4.9 regression comparison prior to promotion.
- Defect Triage & Hypercare: Triage defects raised by client QA and lead the final two weeks of hypercare.
Requirements
- 8+ years of hands-on MuleSoft architecture and development experience, including technical leadership on enterprise engagements.
- Proven experience leading Mule 4.x runtime upgrades (Mule 4.9 / Java 17), CI/CD pipelines, and production cut-overs.
- Strong background reviewing code, authoring technical runbooks, and guiding offshore engineering teams.
- Excellent client-facing communication skills for daily technical working sessions and release management.
Suggested Stack: MuleSoft, Mule 4.9, Java 17, REST Assured, CI/CD, API Architecture
