Software Engineering Focused on Business Operations
I build software for situations where a company’s growth has created more complexity than its existing tools can handle.
Systems engineered for dependability
My work combines software engineering, workflow analysis, data architecture, automation, payment integration, and production infrastructure. The objective is not simply to deliver an application—it is to create a dependable operational system that employees can use every day and that management can trust.
I am based in Fès and work with companies in Morocco as well as remote clients. I am particularly interested in businesses where better systems can produce measurable improvements in time, accuracy, visibility, and financial control.
I start from the workflow that's failing, not from a stack I want to use.
Requirements, data model, backend, frontend, deployment, documentation — one person owns the whole path.
Every claim in this portfolio connects to a screenshot, a test, a dataset or a report.
I build for adoption and a real operational outcome, not for a portfolio screenshot.
Selected professional context
Fractal Tech · Full-Stack Developer Intern
Designed and delivered a refrigeration-business management application in four weeks: customers, quotations, invoices, intervention documents, authentication, deployment and documentation, alone, on a real client's timeline. This is the project behind the Integrated Field Service & Operations case study.
Cnexia · Customer Support & Account Management
Worked a high-volume operational environment with reporting, escalation and client-account responsibility. This is where a lot of the instinct for "what actually breaks a workflow" comes from — I've been the person stuck reconciling a broken process, not just the person who built one.
Faculté Chariaa · Final Project Internship
Built an institutional stock-management portal directly from requirements gathered with administrative stakeholders: movement history, configurable threshold alerts, Excel/PDF exports, and Merise data modelling done before implementation — the discipline of designing for an environment where continuity matters more than speed.
The workflow comes first. The stack is a decision, not a default.
I default to Laravel and React because they let me move from a data model to a working product fast without fighting the framework, and because most operational software doesn't need anything more exotic than that — it needs someone who models the domain correctly and doesn't cut corners on authorization, validation and error handling. Where the project needs different tools — a Python acquisition pipeline, a PostgreSQL-backed data platform — I use them, and the six case studies in this portfolio show both sides of that: relational business systems and data-intensive backend engineering.
What stays constant across both is the same discipline: understand the workflow before touching the schema, treat documents and records as connected states instead of isolated files, build the boring reliability primitives — idempotency, audit trails, role-based access — before the deadline forces a shortcut, and hand over something the client's own team can run without me.
Evaluate the work directly.
Open the six case studies, look at the actual evidence, and judge the engineering on that — not on how confidently I describe it.