Architect
Map systems, data, constraints and outcomes before selecting API-led, event-driven or synchronous patterns.
Clear ownership forcomplex integration delivery.
Prince leads API development and cross-functional delivery with a focus on secure architecture, reusable assets, clear communication and maintainable handover.
Build & validate
Develop, test, document and deploy integration assets with security and operational behaviour visible to the team.
Lead delivery
Coordinate technical decisions and cross-functional delivery across enterprise integration stakeholders.
As Technical Lead at HCLTech, Prince owns end-to-end delivery of MuleSoft API programmes: shaping requirements with stakeholders, setting API-led architecture and coding standards, reviewing designs and DataWeave, and guiding developers through build, test and CloudHub deployment.
Leadership for integration work is mostly about making the invisible visible: agreeing contracts early, documenting error and retry behaviour, and keeping environments, secrets and pipelines predictable. Prince favours reusable assets in Anypoint Exchange so teams stop rebuilding the same connectivity.
His previous years at NTT DATA (Apisero), recognised with two consecutive MVP awards and client Raving Reviews awards, built the hands-on depth that keeps technical decisions practical rather than theoretical.
Frequently asked
What does a MuleSoft technical lead do?
A MuleSoft technical lead sets integration architecture and standards, reviews designs and code, unblocks developers, coordinates with stakeholders and is accountable for delivering reliable APIs to production.
How does Prince run integration delivery?
Contracts first, reusable API-led layers, explicit error handling, MUnit coverage, CI/CD and clear handover documentation so the client team can own the integrations after go-live.