Romuald Verjus

Your system has grown faster than expected. Technical debt is accumulating. Deployments are becoming risky. A prototype needs to go into production. Or your team needs a senior to structure what exists and accelerate.

This is the type of situation where I step in.

8 years building and taking over critical production systems - payments, data, large-scale microservices. Last mission: 3 years at ADEO designing, taking over, and evolving a platform of 100+ microservices across 1000+ GCP projects.

Results:

- Re-architected 50% of the codebase - development time divided by 4

- Designed critical data pipelines (BigQuery to Kafka connector, GenAI batch, multi-source ingestion) used daily by all platform teams.

- Implemented testing and monitoring strategy - significantly reduced production incidents

- Standardized patterns across the entire data platform

My approach: whether it's a system to build from scratch or an existing one to take over, I work the same way. I understand the business context, I design a solid architecture, I stabilize what's causing problems, I document what has never been documented, and I upskill your developers in the process. Without over-engineering. Without breaking what works.

Microservices architecture, monolith to be cleaned up, prototype to be industrialized, new service to be designed - same rigor, same standards.

Stack: Python (FastAPI, Flask, asyncio) · Kafka · BigQuery · PostgreSQL · ElasticSearch · GCP · Docker · Microservices · Event-driven · MLOps.