Staff-level engineer for when the backend becomes the bottleneck.
Something in production is slow, fragile, or too risky to touch, and the team has stopped
being able to say why. That's the point where the problem has outgrown the backlog and become
an architecture decision.
Production APIs, data pipelines, cloud architecture, reliability.
Defined the primitives and contracts behind an integrations platform
Designed the shared stream, queue, and workflow primitives, plus the source and target contract conventions, behind an integrations platform whose public catalog covers about 125 vendor actions through one dispatcher.
Validated across 16+ source and target integrations, including GitHub and Shopify.
Established service boundaries across a multi-service Python platform
Defined service ownership and API contract conventions across backend APIs, ETL and ML pipelines, monitoring, and CLI surfaces, reducing integration friction and making cross-team changes safer to coordinate.
Broke a marketplace's Elixir monolith into event-driven services
Decomposed the Elixir monolith behind a marketplace app into event-driven services with Event-sourcing, designed and built its entire GCP architecture as code, Terraform then Pulumi, and moved contact sync, presence and SMS notifications off the synchronous request path.
“ Houssem is a great developer and a great person to work with. He showed himself like a real professional. He helped us to understand those nuances [in our system] and find a way to handle them. ”
Tom Goedhart
Co-Founder at Barbaard Management
“ He is a professional engineer with a great deal of experience and a will to jump into fixing any problem. ”
Lucas Gozalvez
CTO at FelixSmart Inc.
“ His technical skills and attention to detail were impressive. What stood out even more was his exceptional communication throughout the project. ”
Nina Rezec
Founder at Global Consultancy UAE
Before you book
What happens on the first call?
You describe what's happening: the system, the symptom, what it's costing you, and what
the team has already tried. I ask questions. Thirty minutes, and we both find out whether
I'm useful here.
What does an engagement look like?
I join one team for the long haul and own a defined part of the backend or platform, at a
weekly capacity we agree up front. The first weeks go on whatever is hurting most.
Do you only work with healthcare and biotech?
No. That's where a lot of the recent work has been, and it's why I'm comfortable with
auditability, access control, and tenant isolation. The same problems show up in any
data-heavy platform.
Do you take full-time roles?
Yes. I'm open to senior backend and platform roles, and to long-term contracts through
Deel or a direct B2B agreement.
Tell me what's breaking.
You don't need a solution, a spec, or a role description. Describe what's going wrong and
we'll work out whether I can help.
