About

I build and lead full-stack products from interface to operations.

I build customer-facing products and the systems behind them, from interfaces and APIs to payments, integrations, operational tools, deployment, and observability.

Open to remote roles and select projects

Experience

Product work from interface to infrastructure

My work spans mobile and web interfaces, APIs, data, payments, queues, integrations, administration, deployment, and observability. I take on product decisions alongside implementation, so the user journey and the systems behind it stay connected.

At Terros, I built restaurant, workspace, booking, and operational-management products. I also worked across every layer of HelloLeo, an AI-native platform for business applications. Since April 2026, I have led technical work on a travel-commerce platform and built product verticals end to end, from data models and provider integrations through payments, fulfilment, and admin tools. I lead roadmap discussions, write design specifications, and review delivery work with the client.

I co-founded Clinavi, a medical-practice platform for Moroccan doctors now in pilot. I work across its architecture, frontend and backend, product decisions, infrastructure, and security.

Progression

Experience

Roles and product work, with dates.

May 2026 to present
Clinavi · Cofounder and Full-Stack Engineer
Building Clinavi, a medical-practice platform in pilot, across product decisions, architecture, frontend and backend engineering, infrastructure, and security.
Apr 2026 to present
Freelance · Full-Stack Engineer and Technical Lead
Leading technical work and building travel-commerce product verticals end to end, including provider integrations, payments, fulfilment, administration, observability, planning, and delivery.
Dec 2023 to Mar 2026
Terros · Full-Stack Web Developer
Built restaurant, workspace, booking, and operational-management products, and worked across every layer of HelloLeo, an AI-enabled business application platform.
2023
OHM Energies and Apside Maroc
My work covered React and Next.js interfaces, PHP services in Symfony and Laravel, documented APIs, Docker workflows, testing, and delivery.

How I work

Make the difficult parts clear early.

I work closely with product and client teams to clarify provider, identity, payment, queue, data, and operational constraints before they shape the interface. For AI features, I focus on how they connect to business data, user workflows, testing, and delivery.

Fig. A.1 · How I workOne loop from ticket to decision record, and back to the next ticket.

A closed loop of twelve steps from ticket to decision records, then back to the ticket. Three steps carry numbered notes, listed after the steps.

Ticket
Brainstorm
Dated design spec
Plan
Provider docs and probes
Isolated branch + test-first
Local gates
PR + CI
Certification or readiness audit
Deploy
Observe
Decision records

Back to ticket

Note 1, on step 3, Dated design spec: A dated design spec comes before implementation, so product paths, system boundaries and delivery work can be reviewed before code makes them expensive to change.
Note 2, on step 5, Provider docs and probes: External providers, identity, payments and queues are the difficult boundaries: their docs are read and their behaviour probed before code relies on them.
Note 3, on step 11, Observe: Observability across web, API, scheduled work and queues, with personally identifiable information kept out of logs, feeds the decision records and the next ticket.