Full-stack Developer in Paris, France

Migrated the product from ASP.NET MVC to .NET Core, revising the architecture from basic CRUD to a domain-driven design with command query responsibility segregation and event sourcing.

The migration consisted of moving the compliance activities functionality from the CRM to a .NET REST API. Some of the UI was moved from ASP.NET Razor and web form components to React web components to be merged with the existing UI.

I wrote the data denormalization code, which maintained consistency between the read SQL Server database and the write Event Store database. Also, I developed React components and wrote unit and integration tests using xUnit.net and user interface tests using Cypress.

Built a React-based dashboard supported by a .NET Core REST API. The dashboard shows the availability status of all applications related to the CRM platform and their dependencies, in addition to reporting the latest error logs to Kibana.

The dependencies are SignalR links to other applications, database connections, or Event Store connections. The availability percentage is calculated based on specific rules, and alerts are sent when predefined thresholds are reached. For the dashboard to retrieve the necessary data, each application must expose a dedicated endpoint wrapped with a shared library, leaving the application team only to implement the health check logic.

Created REST Spring Boot API that allows transfers from bank accounts to digital wallets by performing internal account settlements.

The API receives the settlement data in JSON with a specific accounting schema and checks invariants. Once the accounts are opened, the right balance is available, and the settlements are processed using the core banking system's SOAP API or by integrating an ISO 20022 XML file.

Contributed to the project by working on the back end, front end, and software architecture and built the application based on Spring Boot and Jira Core.

The application allowed companies' purchasing departments to notify suppliers and manage a supplier database, including referencing and contract management. The software follows order processing, from initialization to product delivery. The platform includes automatic supplier pricing, invoice management, payment modules, and an integrated calendar that is synced with the company's email system.

I designed the plugin-oriented software using a microservices architecture with a front-end gateway that handles rendering and authentication. The gateway was built using Angular, and the back-end microservices were implemented with Spring Boot and interacted with the Jira Core engine using REST API. Additionally, I implemented the internal workflows, such as the approval request flow, interest call management, and order fulfillment management.

Developed a suite of applications to manage clearing, interbank payment reconciliation, and credit card application processing, and worked on visualization and reporting for service-level agreement application processing.

The suite included tools for extracting compressed JPEG bank checks, managing rejected transfers and checks, and allowing semi-automatic fund transfers. The applications handled money-clearing files integration, allowed the ATM and POS transaction accounting, and used an XML model for data mapping. To manage and process bank card requests, the applications generated and integrated card creation files in compliance with PCI DSS standards.

This application is written entirely in PHP from scratch with an MVC design. It was developed for an NGO that wanted to automate its process of collecting and analyzing local agricultural data to identify the impact of their actions in the context of global agricultural development aid in third-world countries.

Its objective was to provide users with a user interface to enter agricultural production data remotely. Once data is submitted through HTML forms, a validation flow is triggered where users with higher permissions confirm (or reject) the entries. Once everything is validated, statistics are generated and displayed in the user interface as HTML tables or Chart.js charts, with a filter to select the required geographical area or period. Statistics can also be exported in CSV/Excel. The second objective of the application was to provide an election document management system where supporting documentation is made available to local agricultural actors.

I was the only developer on this project, and I built both the front-end and the back-end and deployed the application on a CentOS base VPS with Apache (httpd) as a web server and MySQL as a database system.