Architecture decisions that commit you
An architecture is a set of decisions that are hard to reverse. I define those decisions with you: application boundaries, service frontiers, data management, resilience strategy — each one documented, reasoned and aligned with your business, budget and regulatory constraints.
Technical leadership of teams
I lead teams of 2 to 15 people, from an emerging product squad to an established banking organisation. My role: set the technical direction, clear blockers, arbitrate, and grow everyone’s autonomy.
- Architecture and code review.
- Facilitation of technical rituals.
- Arbitration of structural choices.
- Mentoring and individual support.
Development standards
A high-performing team shares clear rules: coding conventions, testing strategy, branching model, review criteria, definition of done. I put these standards in place — and, above all, I make them workable day to day.
Skills growth
Standards are only worth it if they outlast my involvement. I support teams’ skills growth so they take ownership of the practices and keep them alive. Autonomy is the goal, not dependency.
Demanding contexts
I have led teams and defined architectures for players in banking and consulting — Crédit Foncier, BNP Paribas, Publicis Sapient, Wynd — environments where rigour and compliance are not negotiable.