Murex Connectivity 2.0 Developer
Project description
We've been engaged by a large European bank to provide resources to their Markets Program development team working on a wide range of projects like CTB changes, risk and regulatory projects, version upgrades, etc. We require an experienced Java Developer to work within the existing Team.
Responsibilities
- - Lead the design, development, and implementation of Murex Connectivity 2.0 solutions. - Act as the primary point of contact for all Murex Connectivity 2.0-related queries, providing guidance and support to the team. - Collaborate with cross-functional teams to ensure the successful delivery of Murex Connectivity 2.0 solutions, including integration with other systems. - Provide technical leadership and mentorship to the team, ensuring adherence to best practices and standards in Murex Connectivity 2.0 development. - Stay updated with the latest advancements in Murex Connectivity 2.0 and related technologies, integrating innovative approaches for sustained competitive advantage.
SKILLS
Must have
- 6 to 10 years of overall experience in Java-based integration development.
- Strong hands-on experience with Murex Connectivity 2.0 (C2) integrations.
- Proven experience working on Murex Open Connect or C2 interfaces.
- Extensive hands-on development experience using Java 8, 11, or 17 and Java EE.
- Strong practical experience with Apache Camel, including routing, endpoints, and enterprise integration patterns.
- Good understanding of Spring Framework, Spring Boot, Hibernate, and ORM concepts.
- Strong knowledge of XML-based messaging, including XML, XPath, XQuery, XSLT, SOAP, and REST services.
- Solid understanding of Java internals, including memory management and transaction handling.
- Strong SQL skills with Oracle database and JDBC.
- Working experience on Linux or Unix environments.
- Experience working in Agile delivery models.
- Good problem-solving ability with clear communication and effective stakeholder coordination.
Nice to have
- Docker, CI/CD, Jenkins and TeamCity - JSON / XML schema understanding
