Marseille, France - Remote collaboration · Product engineering & technical architecture

Complete digital products, architected to hold beyond the prototype.

I design and build complete digital products by connecting software architecture, multi-stack backend engineering, public web, mobile applications, admin platforms, realtime communication, data and production-grade quality.

Depending on the product context, I can architect a backend with Node.js and NestJS, Python, Java and Spring Boot, Go or PHP, then connect it to React, Next.js, Angular, Flutter or React Native interfaces. My role is to turn an idea, an ambitious product or a fragile technical base into a platform that is readable, maintainable, secure and genuinely operable.

Multi-stack backend architectureNode.js · NestJS · TypeScriptPython · Java · Spring Boot · GoPHP · Symfony · LaravelReact · Next.js · AngularFlutter · React Native · MobileAdmin · Realtime · DataTesting · Security · Performance

Discuss a project Explore selected work

Open to selected discussions around product architecture and demanding technical systemsAvailable for software architecture missions, multi-stack backend engineering, full-stack platforms, mobile products, business admin systems, realtime projects and technical recovery work that needs stronger structure before scaling.Response expectation: Usually within 24 to 48 hours.

Essential stack

The full map stays available below without making the mobile page endless.

ReactFrontend Next.jsFrontend Node.jsBackend Unit TestsQuality Engineering

Frontend and mobile8 items

Interfaces, applications and cross-platform clients.

ReactFrontend Next.jsFrontend AngularFrontend React NativeMobile FlutterMobile SwiftMobile KotlinMobile ViteFrontend

Backend and languages12 items

API systems, runtimes and server-side architecture.

Node.jsBackend NestJSBackend TypeScriptLanguage PythonLanguage GoBackend .NETBackend PHPBackend LaravelFramework SymfonyFramework JavaLanguage Spring BootFramework HibernateORM

Data and tooling12 items

Persistence, realtime, package managers and build tooling.

PostgreSQLDatabase MySQLDatabase MongoDBDatabase RedisDatabase PrismaORM Socket.IORealtime npmPackage Manager pnpmPackage Manager YarnPackage Manager ComposerPackage Manager Apache MavenBuild Tool GradleBuild Tool

Quality gates8 items

Tests, mutation, performance, contracts and security checks.

Unit TestsQuality Engineering Integration TestsQuality Engineering End-to-End TestsQuality Engineering Smoke TestsQuality Engineering SchemathesisQuality Engineering Stryker Mutation TestingQuality Engineering Performance TestingPerformance OWASP ZAP Security ScansSecurity

Platforms and environments16 items

Operating systems, IDEs, mobile platforms and workstations.

macOSOperating System Windows 11Operating System Windows 8Operating System Windows 7Operating System AndroidMobile iOSMobile XcodeIDE Android StudioIDE Docker DesktopDevelopment Environment WSL 2Development Environment Ubuntu 26Operating System Ubuntu 24Operating System Kali LinuxSecurity DebianOperating System FedoraOperating System Linux MintOperating System

Complete systems

Multi-stack backend, public web, mobile, admin platforms, data, realtime flows and production delivery treated as one product surface rather than disconnected blocks.

Multi-stack backend engineering

Node.js and NestJS, Python, Java and Spring Boot, Go or PHP chosen according to context, with secure APIs, business rules, persistence, transactions and operational integration.

Delivery discipline

Architecture, validation, testing strategy, performance, security, documentation and maintainability are integrated before debt starts steering the product.

Product judgment

Every technical decision serves a visible objective: faster understanding, lower risk, more reliable operations and software that is genuinely useful.

Complete systems

Multi-stack backend, public web, mobile, admin platforms, data, realtime flows and production delivery treated as one product surface rather than disconnected blocks.

Multi-stack backend engineering

Node.js and NestJS, Python, Java and Spring Boot, Go or PHP chosen according to context, with secure APIs, business rules, persistence, transactions and operational integration.

Delivery discipline

Architecture, validation, testing strategy, performance, security, documentation and maintainability are integrated before debt starts steering the product.

Product judgment

Every technical decision serves a visible objective: faster understanding, lower risk, more reliable operations and software that is genuinely useful.

Delivery map

The value comes from the relationship between architecture, delivery and proof.

This map summarizes the portfolio’s operating thread: frame architecture, build the API, connect interfaces, apply quality gates and make proof usable.

Architecture

Technical frame, domains and boundaries.

Backend API

Contracts, validation and business logic.

Frontend / Admin

Public journeys and internal operations.

Quality gates

Typecheck, build, tests and audits.

Production proof

Readable signals for maintenance and decisions.

The value comes from the relationship between architecture, delivery and proof.

Delivery map

The value comes from the relationship between architecture, delivery and proof.

This map summarizes the portfolio’s operating thread: frame architecture, build the API, connect interfaces, apply quality gates and make proof usable.

Architecture

Technical frame, domains and boundaries.

Backend API

Contracts, validation and business logic.

Frontend / Admin

Public journeys and internal operations.

Quality gates

Typecheck, build, tests and audits.

Production proof

Readable signals for maintenance and decisions.

Architecture

System-first

Stack choices, business boundaries, critical flows and structural dependencies are clarified before implementation expands.

Delivery

Whole product

Backend, web, mobile, admin systems, data and realtime flows stay connected to one product logic instead of becoming isolated surfaces.

Quality

Verified

Contracts, testing, security, performance, documentation and maintainability focus on actual risk instead of decorative process.

Product framing

Clarify the real need, the users, the business constraints, the critical journeys and what the solution must simplify, secure or unlock.

Architecture & backend

Choose the right technical foundations, then structure data, APIs, authentication, business rules, integrations and orchestration without locking the product into a fragile shape.

Interfaces & operations

Connect public web, mobile applications, admin tooling, support, analytics and realtime flows to one coherent and genuinely operable product core.

Hardening & delivery

Verify critical paths, document decisions, monitor risk, prepare performance and ship a base that can evolve without chaotic rewrites.

Six layers connected as one operating system.

Architecture

System-first

Stack choices, business boundaries, critical flows and structural dependencies are clarified before implementation expands.

Delivery

Whole product

Backend, web, mobile, admin systems, data and realtime flows stay connected to one product logic instead of becoming isolated surfaces.

Quality

Verified

Contracts, testing, security, performance, documentation and maintainability focus on actual risk instead of decorative process.

Product framing

Clarify the real need, the users, the business constraints, the critical journeys and what the solution must simplify, secure or unlock.

Architecture & backend

Choose the right technical foundations, then structure data, APIs, authentication, business rules, integrations and orchestration without locking the product into a fragile shape.

Interfaces & operations

Connect public web, mobile applications, admin tooling, support, analytics and realtime flows to one coherent and genuinely operable product core.

Hardening & delivery

Verify critical paths, document decisions, monitor risk, prepare performance and ship a base that can evolve without chaotic rewrites.

Complete systems

I build products where every technical layer serves the same objective.

A serious product is neither a polished interface alone nor an isolated API. It connects multi-stack backend architecture, data, public web, mobile, internal operations, realtime flows, security, quality and production delivery inside one coherent system that can keep evolving.

Product surface map

Six layers connected as one operating system.

Each layer matters independently, but the product becomes serious only when architecture, interfaces, operations and delivery remain connected.

Multi-stack backend architecture

Admin platforms & operations

Public web & product interfaces

Mobile applications & field experiences

Realtime flows, notifications & automation

Quality, security & production delivery

Multi-stack backend architecture

Node.js and NestJS, Python, Java and Spring Boot, Go or PHP depending on the product context: APIs, authentication, business rules, persistence, transactions, queues, integrations and domain boundaries built to last.

Admin platforms & operations

Business back-offices, user management, leads, support, dashboards, permissions, functional monitoring and internal tooling that make the product operable every day.

Public web & product interfaces

Conversion-focused websites, editorial platforms, React, Next.js or Angular interfaces, structured SEO, multilingual navigation, clear content and enough finish to represent the product seriously.

Mobile applications & field experiences

Flutter, React Native or native approaches depending on the need: mobile journeys connected to the same business rules, the same data and the same operating constraints as the broader ecosystem.

Realtime flows, notifications & automation

Chat, WebSockets, notifications, events, automated workflows, user engagement and admin response loops designed for realistic operating scenarios.

Quality, security & production delivery

Validation, unit tests, integration, E2E, API contracts, performance, smoke, security, mutation testing, documentation and operational readiness wherever risk justifies it.

I build products where every technical layer serves the same objective.

Complete systems

I build products where every technical layer serves the same objective.

Product surface map

Six layers connected as one operating system.

Each layer matters independently, but the product becomes serious only when architecture, interfaces, operations and delivery remain connected.

Multi-stack backend architecture

Admin platforms & operations

Public web & product interfaces

Mobile applications & field experiences

Realtime flows, notifications & automation

Quality, security & production delivery

Multi-stack backend architecture

Admin platforms & operations

Business back-offices, user management, leads, support, dashboards, permissions, functional monitoring and internal tooling that make the product operable every day.

Public web & product interfaces

Conversion-focused websites, editorial platforms, React, Next.js or Angular interfaces, structured SEO, multilingual navigation, clear content and enough finish to represent the product seriously.

Mobile applications & field experiences

Flutter, React Native or native approaches depending on the need: mobile journeys connected to the same business rules, the same data and the same operating constraints as the broader ecosystem.

Realtime flows, notifications & automation

Chat, WebSockets, notifications, events, automated workflows, user engagement and admin response loops designed for realistic operating scenarios.

Quality, security & production delivery

Validation, unit tests, integration, E2E, API contracts, performance, smoke, security, mutation testing, documentation and operational readiness wherever risk justifies it.

Selected work

Proof through architecture, reconstruction and technical responsibility.

The selected work spans public products, business platforms, backend architecture, mobile surfaces, recovery efforts and IT duties carried out in a confidential environment.

These cases avoid fabricated metrics and expose no sensitive detail. Their value lies in the real technical surface: product, backend, frontend, mobile, infrastructure, documentation, quality and the ability to carry technical responsibility.

01 - Professional multilingual web platform

Luchtreiniger Pro / Afzuigkapreinigenhoreca.nl

A production-oriented B2B web ecosystem designed to present services, structure demand acquisition, handle leads and deliver an operable platform in Dutch and English.

A complete business-facing platform with acquisition, business logic and operations — not a brochure page.

Scope

NL / EN multilingual public website
Next.js frontend and SEO-oriented content architecture
Backend, forms, leads and business workflows
Back-office, VPS infrastructure and deployment documentation
Quality baseline, build verification and progressive hardening

Stack signal

Next.jsNestJSTypeScriptMultilingual SEOLead workflowBack-officeVPS / DockerDocumentation

02 - Advanced modular backend and social mobile product architecture

Glimpse

A dense backend and product foundation for a social mobile application, with complex domains, deep quality strategy and strict responsibility boundaries.

Architecture depth, testing pressure, validation rigor and product design shaped for serious production readiness.

Scope

Multi-domain NestJS backend architecture
Prisma, PostgreSQL, PostGIS and complex business rules
Auth, chat, notifications, wallet, gamification, billing and referrals
Full quality chain: k6, Schemathesis, unit, integration, E2E, smoke, ZAP and Stryker
Testing documentation, global runners and API / test repository separation

Stack signal

NestJSPrismaPostgreSQLPostGISk6SchemathesisJestE2EZAPStryker

03 - Multi-surface product recovery and technical reconstruction

Socializus / P4W

A clarification and reconstruction effort spanning mobile application work, backend design, chat, notifications and maintainability, with one concrete objective: making the system understandable and evolvable for a small team.

A practical recovery mindset for systems that need clarity, lower risk and stronger foundations again.

Scope

React Native application for iOS and Android
Backend recovery, chat, notifications and product-flow consistency
Architecture decision between isolated chat microservice and modular NestJS monolith
Maintainability designed for a small team, handover and future contributors
Documentation, flow stabilization and progressive hardening

Stack signal

React NativeiOS / AndroidNestJSRealtime chatNotificationsProduct reconstructionDocumentationQuality hardening

04 - Public Android SMS gateway prototype

SmsService

A public Kotlin Android prototype that turns a controlled phone into a local SMS gateway for consent-based transactional messages, with backend integration constraints and explicit security limits.

A small but concrete public repository showing Android, backend integration, local infrastructure thinking and security boundaries.

Scope

Android foreground service running on a controlled phone
Local HTTP-like endpoint for backend-triggered SMS requests
Shared-secret validation and French mobile number restriction in the prototype
GitHub documentation, build instructions and local network usage notes
Security framing: visible secrets must be rotated and the gateway must stay private

Stack signal

KotlinAndroidSmsManagerLocal gatewayBackend integrationConsent-based SMSGitHub publicSecurity hardening

05 - Technical experience under demanding constraints

French Foreign Legion — IT duties in a confidential environment

An IT experience carried out in an environment where rigor, discretion, reliability and service continuity were part of the expected standard.

A formative experience, presented with restraint, that helps explain my current standards for architecture and reliability.

Scope

IT duties performed within a confidential framework
Experience with demanding environments and strong operational constraints
Responsibility, continuity and technical reliability as working habits
Operational discretion: no sensitive or confidential detail is exposed

Stack signal

ConfidentialityReliabilityRigorTechnical responsibilityContinuityDiscretion

Open the projects page

Proof through architecture, reconstruction and technical responsibility.

Selected work

Proof through architecture, reconstruction and technical responsibility.

The selected work spans public products, business platforms, backend architecture, mobile surfaces, recovery efforts and IT duties carried out in a confidential environment.

01 - Professional multilingual web platform

Luchtreiniger Pro / Afzuigkapreinigenhoreca.nl

A production-oriented B2B web ecosystem designed to present services, structure demand acquisition, handle leads and deliver an operable platform in Dutch and English.

A complete business-facing platform with acquisition, business logic and operations — not a brochure page.

Scope

NL / EN multilingual public website
Next.js frontend and SEO-oriented content architecture
Backend, forms, leads and business workflows
Back-office, VPS infrastructure and deployment documentation
Quality baseline, build verification and progressive hardening

Stack signal

Next.jsNestJSTypeScriptMultilingual SEOLead workflowBack-officeVPS / DockerDocumentation

02 - Advanced modular backend and social mobile product architecture

Glimpse

A dense backend and product foundation for a social mobile application, with complex domains, deep quality strategy and strict responsibility boundaries.

Architecture depth, testing pressure, validation rigor and product design shaped for serious production readiness.

Scope

Multi-domain NestJS backend architecture
Prisma, PostgreSQL, PostGIS and complex business rules
Auth, chat, notifications, wallet, gamification, billing and referrals
Full quality chain: k6, Schemathesis, unit, integration, E2E, smoke, ZAP and Stryker
Testing documentation, global runners and API / test repository separation

Stack signal

NestJSPrismaPostgreSQLPostGISk6SchemathesisJestE2EZAPStryker

03 - Multi-surface product recovery and technical reconstruction

Socializus / P4W

A practical recovery mindset for systems that need clarity, lower risk and stronger foundations again.

Scope

React Native application for iOS and Android
Backend recovery, chat, notifications and product-flow consistency
Architecture decision between isolated chat microservice and modular NestJS monolith
Maintainability designed for a small team, handover and future contributors
Documentation, flow stabilization and progressive hardening

Stack signal

React NativeiOS / AndroidNestJSRealtime chatNotificationsProduct reconstructionDocumentationQuality hardening

04 - Public Android SMS gateway prototype

SmsService

A public Kotlin Android prototype that turns a controlled phone into a local SMS gateway for consent-based transactional messages, with backend integration constraints and explicit security limits.

A small but concrete public repository showing Android, backend integration, local infrastructure thinking and security boundaries.

Scope

Android foreground service running on a controlled phone
Local HTTP-like endpoint for backend-triggered SMS requests
Shared-secret validation and French mobile number restriction in the prototype
GitHub documentation, build instructions and local network usage notes
Security framing: visible secrets must be rotated and the gateway must stay private

Stack signal

KotlinAndroidSmsManagerLocal gatewayBackend integrationConsent-based SMSGitHub publicSecurity hardening

05 - Technical experience under demanding constraints

French Foreign Legion — IT duties in a confidential environment

An IT experience carried out in an environment where rigor, discretion, reliability and service continuity were part of the expected standard.

A formative experience, presented with restraint, that helps explain my current standards for architecture and reliability.

Scope

IT duties performed within a confidential framework
Experience with demanding environments and strong operational constraints
Responsibility, continuity and technical reliability as working habits
Operational discretion: no sensitive or confidential detail is exposed

Stack signal

ConfidentialityReliabilityRigorTechnical responsibilityContinuityDiscretion

Open the projects page

Working method

Clarity first. Architecture second. Hardening where it matters.

The process is designed to reduce technical fog, make the right system decisions early and leave behind software that can keep moving.

Delivery

A product is framed before the build expands.

Architecture

Backend decisions are connected to product operations.

Quality

Risk receives verification instead of ceremony.

Frame the real need

Clarify the product objective, constraints, users, risk and operating model before writing the critical code.

Design the system boundaries

Choose domains, APIs, data flows, interfaces and responsibilities with maintainability in mind.

Build the foundations

Implement the backend, interfaces and workflows with a bias for clarity, typed contracts and changeable structure.

Harden the risky paths

Apply tests, contract checks, performance probes and smoke verification where failures would be expensive.

See the full method ->

Clarity first. Architecture second. Hardening where it matters.

Working method

Clarity first. Architecture second. Hardening where it matters.

The process is designed to reduce technical fog, make the right system decisions early and leave behind software that can keep moving.

Delivery

A product is framed before the build expands.

Architecture

Backend decisions are connected to product operations.

Quality

Risk receives verification instead of ceremony.

Frame the real need

Clarify the product objective, constraints, users, risk and operating model before writing the critical code.

Design the system boundaries

Choose domains, APIs, data flows, interfaces and responsibilities with maintainability in mind.

Build the foundations

Implement the backend, interfaces and workflows with a bias for clarity, typed contracts and changeable structure.

Harden the risky paths

Apply tests, contract checks, performance probes and smoke verification where failures would be expensive.

See the full method ->

Tech lab

An engineering environment built to develop, test, experiment and document without unnecessary compromise.

The lab is part of how I produce: powerful workstations, Linux and macOS ecosystems, Docker environments, mobile tooling, local AI curiosity, performance checks, quality verification, documentation and enough hardware margin to explore seriously before industrializing.

Visit the tech lab

About

Software engineering, operational discipline and IT experience in a confidential environment.

My background combines complex digital product development, seven years of service in the French Foreign Legion and IT duties carried out within a confidential framework. Without exposing any sensitive detail, that experience explains part of my working standard: rigor, discretion, reliability, technical responsibility and the ability to stay precise under pressure.

Read the story

An engineering environment built to develop, test, experiment and document without unnecessary compromise.

Tech lab

An engineering environment built to develop, test, experiment and document without unnecessary compromise.

Visit the tech lab

About

Software engineering, operational discipline and IT experience in a confidential environment.

Read the story

Start the conversation

Bring the idea, the existing product or the system that became unclear. I will help turn it into an operable architecture.

Use the contact page for software engineering missions, full-stack platforms, multi-stack backend architecture, mobile applications, technical recovery work, quality hardening, recruitment opportunities and serious collaborations where system clarity truly matters.

Discuss a project View resume