The back office or Operations domain in a bank is responsible for managing the life-cycle of business objects, such as contracts after they are booked by the Front Office domain. The One Stop Processing (OSP) module allows these users to monitor, investigate, and execute manual tasks (that cannot or should not be automated) required for the business activity of their organization. It allows users to search, analyze and validate items from a real-time refreshed screen, in addition to performing financial and non-financial events on the items.

The internship will take place in the team responsible for the OSP, the real-time exception management application of the MX.3 platform.

Missions:

The OSP application provides a modern solution to allowing workflows that require interacting with other client-side and server-side applications.

In the OSP, data can be visualized from multiple services, allowing users to perform generic actions on data without the need to open multiple applications. The interaction between the OSP and other services can have an unforeseen impact on the performance of the OSP. In some cases, slow services can cause a degradation in OSP performance, which is undesirable.

OpenTelemetry, among other modern monitoring techniques, could help us identify the cause of such performance issues, and better understand the chain of interactions across multiple services. Identifying these issues can help us propose solutions and improve performance.

The aim of the internship will be the following:

·       A study on the OSP architecture and how the OSP visualizes data originating from external services.

·       Define the metrics that will be used to evaluate and detect performance issues and give a better understanding of the interactions between services.

·       Determine the max throughput the service can handle (in order to establish recommendations for client installation)

·       Build a monitoring system for the OSP that can track interactions across different services.

·       Build a dashboard to show the results and articulate the metrics in an intuitive way.

·       Student in the last year of an Engineering/Computer Science degree or Master’s degree.

« Mandatory » skills:

·       Good knowledge of object-oriented programming (preferably Java)

·       Interest in software engineering issues (“clean code”, resilience, operability, continuous integration, etc.)

·       Autonomy, curiosity, and capacity for innovation

·       Fluent English

« Nice to have » skills:

·       Ability to work in an agile and highly collaborative environment.

·       Compilation, algorithmic and concurrency knowledge will be appreciated.

Duration: 6 months from February or March 2024