Responsibilities

• Collaborate with business users, product owners, and architects to gather, document, and refine integration requirements.
• Translate business processes and functional requirements into API specifications, data mappings, and integration use cases.
• Conduct analysis between existing systems and desired integration outcomes.

• Work closely with MuleSoft developers and architects to define API interfaces, message structures, and validation rules.
• Create detailed specifications including RAML or TMForum definitions, payload examples, and data transformation logic.
• Participate in API design reviews and ensure adherence to enterprise integration standards and governance frameworks.

• Support end-to-end integration delivery across planning, testing, and deployment phases.
• Prepare project documentation such as user stories, process flows, sequence diagrams, and integration test cases.
• Validate implemented APIs against business requirements and assist in Sanity Test and user acceptance testing (UAT).

• Act as the liaison between business users, ServiceNow development teams, and vendors (e.g., Mulesoft, ServiceNow, in-house core systems).
• Communicate project status, risks, and issues effectively to both technical and non-technical stakeholders.

• Assist in maintaining API documentation portals and reuse catalogues.
• Identify opportunities to streamline integration processes and promote reuse across applications.
• Contribute to establishing best practices for API lifecycle management, security, and versioning.

Requirements

• Degree in Computer Science / Engineering or related discipline
• Hands-on experience with MuleSoft Anypoint Platform, including API management and integration lifecycle.
• 3–5 years of experience in large-scale IT integration projects.
• Hands-on experience working in Agile Scrum teams delivering integration or platform features in iterative sprints.
• Proficiency in writing user stories, acceptance criteria, and maintaining a well-groomed product backlog using tools like Jira or Azure Boards.
• Proficiency in designing Mule components (Mule ESB, Anypoint Studio, ETLs, flows, MEL, message modelling, Routing, Filtering, Database, Exception Handling, API Management)
• Understanding of MCP (Model Context Protocol) architecture: resources, tools, prompts/skills, and how they provide context to AI models.
• Knowledge of how to integrate MCP with enterprise systems (e.g., via HTTP, webhooks, or event buses) for orchestration