Yorick Mvou

Context & Missions

Participation then technical leadership of the Customer Service & Person Repository project, aiming to modernize services related to credit, renewals, and insurance, with progressive migration of applications and batch jobs to IBM Cloud. Since 2024, creation and technical supervision of the RCLU (Unique Customer Reference) project, centralizing customer contract management in a unified, scalable, and resilient architecture.

Development & Architecture (02/2022 – 12/2023)

Implementation of business services: credit transfers, quantiles, DMA, banking and civil status changes.

Design and development of REST services (Offer Push, Identify Person, Apple Overview with ThreadPool parallelization).

SOAP → REST Migration (Actito emails/SMS), evolution of Struts 1 applications.

Maintenance of applications interconnected via Kafka (DB2 ↔ SAV), update of multi-brand email templates.

Migration of batch jobs to Java 8, Autosys supervision, secure CFT + PGP/GPG transfers.

Unit and integration tests (JUnit, Mockito), code reviews, Jenkins / XL Release / GCLWeb deployments.

Lead Developer & Technical Supervision (since 01/2024)

Supervision of developers, validation of designs and technical choices.

Leading code reviews, promoting best practices (SOLID, Clean Code, Git Workflow, Sonar).

Supervision of deployments, monitoring of production environments and incidents.

Participation in scoping, technical committees, and application reviews.

Writing and validation of specifications, estimations, POCs, mentoring, and technical interviews.

RCLU Project (Unique Customer Reference)

Hexagonal architecture design, implementation of Kafka Stream / Connect flows.

Creation of REST service for LDAP account creation (apigee, oaut2 jwt), management of CI/CD, ACLs, domain per application...

Application of SOLID, Clean Architecture, DRY, KISS, YAGNI principles to ensure performance and maintainability.

Project Context

Development and deployment of a web application for real-time monitoring of documentary credit operations. The team: three developers supervised by a Product Owner responsible for the business vision.

Analysis and Design

User workshops gathered requirements, formalized into user stories, then translated into Jira tickets detailing functional requirements, banking rules, and security constraints. The project followed Scrum with two-week sprints. Retrospectives facilitated continuous improvement.

Technical Architecture

API contracts were defined in contract-first mode using OpenAPI 2/3 with Stoplight. An FBTI web service was designed for data reading, secured by JWT. The NTT service, an FBTI consumer, transited through an Axway gateway ensuring routing, security, and monitoring. Swagger facilitated understanding and testing.

Frontend Development

The Angular 8 interface was developed from UX/UI mockups, with a modular architecture. A migration to Angular 11 improved performance, Ivy, and bundle reduction.

Quality Assurance

Unit tests (80% coverage) and systematic code reviews ensured quality and sharing. Performance optimizations, including caching, were implemented.

Maintenance and CI/CD

A Jenkins pipeline automated build, tests, and SonarQube analysis. Multi-environment deployment (DEV, QUAL, RECETTE) with XLDeploy/XLRelease ensured consistency and traceability. Production deployment was progressive with pilots and training sessions.

Context

Participation in the development of a mobile application for the health and wellness sector, offering essential client-side services.

The project team included a Product Owner, two developers (front-end and back-end), and a testing team.

Client-Server Architecture.

Mobile Development – Client Side

1. Design and implementation of reservation management, allowing users to request a service directly from the application.

2. Integration of push notification management via Firebase to inform clients in real-time.

3. Execution of unit and integration tests ensuring functional reliability of the application.

4. Systematic code review to ensure compliance with quality and performance standards.

5. Contribution to deployment on the Play Store and Apple Store, including packaging, quality checks, and version tracking.