The internal applications covered cybersecurity, communications and HR, from scoping to post-release follow-up.
3 appsJava · Angular · REST
Objects to explore · 3Click an object in the scene or in the list.
Vulnerability alerts Professional contribution · Crédit Coopératif
Java/Angular application, NIST/NVD integration, matching rules, tests and documentation. A focused report to prioritise checks.
QR service Professional contribution · Crédit Coopératif
Business workshops, full-stack flow, validation, tests and release preparation. Personalised generation by identity and entity.
HRIS modernisation Professional contribution · Crédit Coopératif
Legacy analysis, functional migration, Java/Angular development, tests and RUN. A more maintainable and traceable web application.
02Global interaction
Follow my request.
Send a request through the ING3 architecture. Each node reveals the component’s role and my contribution.
6 hopsinterface → data
Objects to explore · 6Click an object in the scene or in the list.
React / Angular Banking + team project
Angular development in banking, then React/TypeScript on SIRIUS ING3. Web journeys structured around user needs.
BFF Engineering project · team of 3
Express/TypeScript BFF and sequence-flow definition. A clear boundary to aggregate and secure calls.
Spring Boot Engineering project · team of 3
User, group, chat, media and notification services. A distributed architecture with explicit responsibilities.
Kafka / WebSocket Engineering project · team of 3
Kafka for events, WebSocket for real-time and Redis Pub/Sub across instances. Decoupled flows and instant interactions.
Persistence Engineering project · team of 3
PostgreSQL for relations, MongoDB for messages, MinIO for media and Redis for fast access. Intentional, documented polyglot persistence.
Quality & RUN Banking + team project
Tests, CI/CD, documentation, health checks and defect follow-up. Connect development, delivery and operations.
03SIRIUS · three generations
Evolve without erasing.
The capstone shows a progression: desktop client, Kubernetes web app, then real-time microservices and GitOps.
ING1 → ING3evolving architecture
Objects to explore · 4Click an object in the scene or in the list.
ING1 · Monolith Engineering project · team of 3
Activity CRUD, simple messaging, UML, persistence and first Jenkins chain. A simple, documented end-to-end product.
ING2 · Web Engineering project · team of 3
UI migration, recommendation algorithm and Kubernetes environments. A web application deployed across several environments.
ING3 · Distributed Engineering project · team of 3
React, BFF, Spring Boot, Kafka, WebSocket, Redis and polyglot persistence. A more modular, observable architecture delivered through GitOps.
Design Engineering project · team of 3
Class, object and sequence UML diagrams over three years. Shared flows and architecture understandable by the team.
04Incident S1
The chat stops responding.
An incident becomes an architecture reading: service, pods, dependencies, logs and health checks are cross-checked before concluding.
S1reproducible diagnosis
Objects to explore · 4Click an object in the scene or in the list.
Chat service Individual work
Checked service, endpoints and routing. Distinguish broken exposure from a stopped application.
Pods Individual work
Inspected pods, events, probes and restarts. Technical evidence before the hypothesis.
Logs Individual work
Correlated Loki and service logs. A documented cause rather than a guess.
Recovery Individual work
Removed the injection and checked nominal recovery. A complete diagnosis–correction–validation cycle.
05Beyond code
Design, then make it understandable.
Tutoring and community leadership complement my technical work with teaching and coordination.
Objects to explore · 3Click an object in the scene or in the list.
Teach Individual work
Adapt explanations to each student’s level, blockers and pace. Eight students supported and sustained teaching practice.
Anticipate Individual work
Organise, facilitate and hand over responsibilities after graduation. Chess strengthens my ability to read several branches before choosing an implementation.
Connect Professional contribution · Crédit Coopératif
Document decisions, make progress understandable and share risks. A dual BUILD/RUN culture and a common language across stakeholders.
06Next mission
Let’s build software that remains maintainable in RUN.
This route prioritises banking applications, distributed architecture, testing and delivery; its résumé is Software-focused.