Murex Consultant

We are looking for a Senior Java & Murex Developer who has worked hands-on inside the Murex platform (MX.3), not only on systems that feed trades into it. You will build and support Murex configuration, interfaces and Java services across the full trade lifecycle, from front office trade capture through middle office and back office processing.

The right candidate understands how a trade moves front-to-back across a capital markets business. They also write clean, well-tested Java, and can show TDD, BDD and mocking in a live technical discussion.

• Location: Toronto - Hybrid
• Contract: 12 months + possible extension
• Experience: 8+ years in software development, including 4+ years hands-on with Murex

Key responsibilities

Murex platform development

• Configure, customize and extend Murex MX.3 directly within the platform, including workflows, static data, trade templates and event processing.
• Build and maintain Murex integrations using MxML Exchange, Murex web services and messaging layers (MQ, Kafka, JMS).
• Develop and support Murex Datamart extractions, EOD/batch processing and downstream reporting.
• Support Murex upgrades, environment refreshes, regression testing and release migrations.

Front-to-back trade lifecycle

• Deliver changes across the full trade flow: front office trade capture and pricing, middle office (trade validation, P&L, risk, limits, market data), and back office (confirmations, settlements, accounting, payments and SWIFT messaging).
• Work with traders, middle office, operations, finance and risk teams to turn business needs into technical solutions.
• Analyze and resolve production issues end-to-end, tracing a trade from booking through settlement and accounting.

Java engineering

• Design and build Java 11+/17 services and Spring Boot microservices around the Murex platform.
• Write production code using TDD, with unit tests (JUnit 5, Mockito) and behaviour-driven acceptance tests (Cucumber or similar).
• Apply sound design: SOLID principles, design patterns, concurrency and performance tuning.
• Take part in code reviews, CI/CD pipelines and Agile delivery.

Required qualifications

Murex (must be hands-on in the platform)

• 4+ years working directly in Murex MX.3. This means configuration, development or support inside Murex, not only building systems that send trades to it.
• Practical experience with at least two of: MxML Exchange, Datamart, pre-trade or post-trade workflows, Murex event and contract lifecycle, Murex batch/EOD.
• Able to explain Murex's role in the bank's architecture and how it connects to upstream and downstream systems.

Capital markets business knowledge

• Clear understanding of the front-to-back trade lifecycle, not only front office trade capture.
• Working knowledge of middle office functions: trade validation, P&L attribution, risk and limits, market data, EOD controls.
• Working knowledge of back office functions: confirmations, settlements, payments, accounting entries and reconciliations.
• Experience with at least one asset class in depth (e.g. Fixed Income, FX, Interest Rate Derivatives, Equities or Securities Lending).

Core Java

• 8+ years of professional Java development (Java 11+ / 17), with strong command of collections, generics, streams, exception handling, memory model and multithreading.
• Spring Boot, REST APIs, SQL (Oracle / Sybase / SQL Server) and messaging (IBM MQ, Kafka or JMS).
• Able to discuss design trade-offs, design patterns and performance tuning with concrete examples from their own work.

Testing practices (assessed in interview)

• Proven, day-to-day use of TDD, not only familiarity with the term.
• Hands-on with JUnit 5 and Mockito: mocks, stubs, spies, argument captors and verifying interactions.
• Experience writing BDD scenarios (Gherkin / Cucumber) and wiring them to step definitions.
• Candidates who list TDD, BDD or mocking on their resume should expect live questions and a short coding exercise on these.

Nice to have

• Murex certification or formal Murex training.
• Experience with a Murex upgrade (e.g. 3.1.x version migrations) or a greenfield Murex implementation.
• Exposure to regulatory reporting (e.g. EMIR, Dodd-Frank, CSA trade reporting).
• Angular or TypeScript for internal tools and dashboards.
• Unix/Linux shell scripting, AutoSys or Control-M scheduling.
• Level 3 production support for 24x7 trading systems.