Nathan Mercier

I'm part of the Fraud Acquisition team, developing and maintaining a case management platform that allows bank staff to handle fraud dispute cases with customers and decide whether fraudulent transactions should be reimbursed.

Being in a banking environment means navigating a dense set of regulatory and business rules — which keeps every feature both challenging and meaningful.

Among the features I delivered:

Trackdéchet is a waste management platform used by large companies like Intermarché to track their waste from creation to destruction — whether wooden pallets or radioactive materials. I joined as a fullstack developer, contributing to both the Java/Spring Boot backend and the Vue.js frontend of an existing monolith.

The highlight of this mission was implementing multi-packaging support within a single transport, a significant feature that required a deep refactoring of the existing data model and had a wide impact across the application.

What I appreciated most here was the engineering culture. After dealing with legacy codebases in previous missions, this was a refreshing change — the team genuinely cared about code quality. The process reflected that: every feature went through development, peer testing, a merge request reviewed and tested by at least two other developers, a team demo, and a production release only once everything was validated.

My first real professional experience in an enterprise environment. I worked on OMEGA, an early childhood grant management software with highly complex business rules — over 250 database tables, a large user base, and years of legacy code to navigate.

It was a tough but formative environment. Most of the codebase didn't follow modern development practices, which forced me to quickly develop a sense for managing complexity, reading unfamiliar code, and delivering features despite technical debt.

The highlight of this mission was the opportunity to build a new monolithic application from scratch in Spring Boot — my first hands-on experience with the framework. Going from legacy code to a greenfield project in the same mission gave me a unique perspective on what good software architecture actually means in practice.