I take ambiguous, data-heavy problems from nothing to shipped.

Engineering and product builder, 15+ years. About a decade at Algolia, building the data and product systems underneath a search company through hypergrowth. Now independent and hands-on, helping founders and teams turn hard, ambiguous problems into things that ship and work.

Currently taking on 1 to 2 engagements

LinkedIn Email

Based in France

15+ years building data-intensive products Algolia: there from 40 to 800 people, past $200M ARR Shipped my own SaaS to ~4,000 users From scratch: billing, analytics, ranking & ML, data pipelines

How I work

Problem first. Stack second.

Start from the problem

I understand a job deeply before I build it or hire for it. The tech serves the problem, never the other way around.

Build it end to end

Backend, frontend, ML pipelines, data, infra. One operator who takes it the whole way, not a slice to manage.

Decide under ambiguity

Data-guided when there is signal, decisive when there is not. Cost and margin aware: I spend to move faster when it is worth it.

I have built things, scaled them, and shut some down on purpose. I know which tradeoff buys speed now, and which one you pay for later.

Proof

A few things I've built.

Algolia

~A DECADE · ENGINEERING & PRODUCT

I joined early and stayed through the climb from 40 to 800 people. I built hands-on, led teams, and came back to hands-on. The systems underneath: the usage and billing that metered the business, the analytics and experimentation tools product teams used to decide what to build, ranking and relevance for its largest customers, and the data pipelines behind customer insight. The domain was search. The instinct travels.

Pimwi

MY SAAS · ~4,000 USERS

My own product, built from nothing and grown to around 4,000 users. I designed it, shipped it, ran it, and supported it, then chose to wind it down when it stopped being worth continuing. The full lifecycle, owned end to end, including knowing when to stop.

If it's not a win for you, it's not a win for me.

Outcome first, always.

Work with me

Tell me the problem.

I work with founders and teams on 0 to 1 builds and on hard data, search, and product problems. Hands-on, as a partner, not a vendor. Whether it is something that does not exist yet or something stuck that needs to start working, send me a few lines. It usually starts with one scoped piece of work over a few weeks, and we see from there.

I work under my own name. The person who builds it is the person you talk to. No agency, no handoff, no account manager.

Send the problem in a few lines. If I can help, I'll tell you how I'd approach it. If I'm not the right person, I'll say so.

Email me the problem

Off the clock I produce music as Raylixir, I run, and I keep threatening to ship an indie game. Same loop, different medium.