Job Title

Job Title: Mulesoft Technical Lead Skills: MuleSoft, insurance, API, ESB, RESTful, Amazon S3, Amazon MQ, RESTful APIs, OIDC/OAuth (Okta), relational databases, Jenkins, Azure DevOps, Maven, GitHub, Logging tools Experience: 10 to 15 Years Location: Mississauga, Ontario, Canada Job Type: Full-time We at Coforge are hiring Mulesoft Technical Lead with the following skillset: Degree in the field of computer science, information science, management information systems preferred. Minimum of 10 years of hands-on experience as a MuleSoft Developer. In-depth knowledge of life insurance industry processes and data structures. Proficiency in MuleSoft Any point Platform, including API development and ESB configuration. Strong understanding of API design principles, RESTful services, and microservices architecture. Problem solving skills sufficient to perform research and recommend a proposed solution to problems. Effective verbal and written communications skills and the ability to communicate with business partners and other IT staff. Designed, developed, and implemented robust MuleSoft integrations tailored to the unique needs of the life insurance sector. Collaborated closely with stakeholders to gather requirements and ensure accurate data mapping and transformation. Built scalable APIs and microservices to facilitate data exchange between systems, both internal and external. Ability to define MuleSoft best practices and testing guidelines. Performed troubleshooting and resolution of integration issues promptly, ensuring minimal disruptions to critical business processes. Strong experience with event-based integrations, connectors and other tools for Amazon S3, Amazon MQ, RESTful APIs, OIDC/OAuth (Okta), relational databases, file shares Experienced with continuous integration and automation practices to support improved delivery to production using tools like Jenkins, Azure DevOps, Maven, GitHub, Logging tools preferred. Ability to work collaboratively in cross-functional teams and communicate effectively with both technical and non-technical stakeholders.