STAGE 3A - DEV C++ - Unit test the liquidation maintenance engine H/F

Murex is a global fintech leader in trading, risk management, and processing solutions for capital markets. Operating from our 19 offices, 2,500 Murexians from over 60 different nationalities ensure the development, implementation, and support of the MX.3 platform which is used by banks, asset managers, corporations and utilities, across the world.

Join Murex and work on the challenges of an industry at the forefront of innovation and thrive in a people-centric environment.
You’ll be part of one global team where you can learn fast and stay true to yourself.

Context :

The liquidation team is in charge of developping and maintaining the code that:

• computes the back office positions and their P&L results
• handles the corporate actions execution on those positions
• feeds the front office and the accounting with these positions

We are an agile team working in collaboration with others teams on cross-teams subjects using the SAFe framework.
Collaboration, mutual aid and communication is promoted inside and outside the team.

Missions :

The maintenance engine is in charge of computing positions during the EOD.
This engine, though being at the heart of the liquidation process, is not unit tested.
The purpose of the internship will be to define a roadmap and unit test the engine.

Missions:

The purpose of the internship will be to:

• Model the interactions between the liquidation and its external dependencies
• Define the interfaces and class interactions using the Domain Driven Design approach.
• Refactor and unit test the engine.

Hence during his internship, the internee will have to acquire some knowledge about the Domain Driven Design and how to apply it in in an industrial context.
He could present his thoughts about it to the team and collaborate with us to define some coding rules for a testable code.

He will also have to analyze the existing code and discuss with the functional team to understand the functional aspects of the module.

Since the code is still enriched and maintained by the team, he will have to proceed by steps, participate to agile meetings, communicate and synchronize with the team on his work.

The developments will be done in C++ and unit tested with gMock.

Profil :

3rd year student in Computer Science:

• Good knowledge of C++ and unit testing with gMock
• Good knowledge of SQL
• Interest in software engineering ("clean code", resilience, operability, continuous integration)
• Ability to speak in english
• Ability to work in agile mode
• Good analytical skills
• Ability to collaborate and communicate