Full-stack web apps and SaaS, from the database to the last pixel

A marketplace, a customer portal, an internal dashboard, the first version of your SaaS. I build the whole stack — data model, API, interface, payments and messaging integrations, deployment — and I've shipped my own products, so I build for the day after launch, not just the demo.

5-star rated mentor on Udacity

1,000+ students trained

10+ large projects

100+ projects delivered

100% success rate

Who this is for#

Founders launching a product, companies replacing a spreadsheet-and-email process with real software, and teams that need a senior engineer to own a feature area end to end. Typical builds: marketplaces, booking platforms, CRMs and admin dashboards, customer portals, and the first version of a SaaS.

What you get#

A data model that will still make sense in a year. PostgreSQL, designed for the questions you'll ask later, not just the screens you need now.
A clean API (REST or GraphQL) with authentication, permissions, rate limiting and documentation.
A responsive React frontend that works on phones — most of your users are on one.
Integrations: payments (Stripe or regional gateways), WhatsApp and email messaging, maps, file storage, third-party APIs.
Deployment and monitoring: containerised, deployed to your cloud, with backups, logs, error tracking and uptime alerts.
Tests and documentation, so the next engineer (or you) can change it safely.

How I build it#

Scope and data model. We map the workflows, the entities and the screens; you get a written scope with milestones.
Walking skeleton in week one. Login, the main screen and deployment, so every later week adds something real.
Build in weekly slices. Each week ends with a demo of working software on a staging URL.
Launch. Domain, TLS, monitoring, backups, a runbook — and I'm around for the first weeks after.

Proof#

Manzel Masr — Egypt's Arabic-first property marketplace with a CRM for brokers: map search with live prices, video tours, verified broker directories, WhatsApp-to-broker messaging and an AI listing assistant. I founded it and built it (Django, PostgreSQL, React, WhatsApp Business API).
Seera — an interactive, sourced timeline with 84+ events, search and filters (React).
Excalidraw+ — an extended whiteboard with no ceiling on diagram size and a built-in presentation mode (TypeScript, React).
Hamour — a 3D browser game with 100 levels (Three.js), which says something about how far a web app can go.
In previous roles: microservices in NestJS with end-to-end tests, a Spotify-style backend built with a small team inside a 36-developer project, and a monolith refactored into microservices with a full CI/CD pipeline on AWS.

Stack I typically use#

Python (Django, FastAPI, Flask) · TypeScript (Node.js, NestJS) · React · PostgreSQL, Redis, Kafka · WebSockets and gRPC where real-time matters · Docker, Kubernetes, GitHub Actions · Azure, AWS, GCP.

Where and how I work#

Remote from Cairo (UTC+2) with clients in the United States, Europe and the Middle East. Fluent English, native Arabic. Weekly written updates and working demos — no twenty-page proposals.

Questions people ask

What size of project do you take on?

From a focused MVP in a few weeks to a platform built over several months. I've built more than ten large projects and over a hundred small and medium ones, so I can also scope honestly which of the two you actually need.

Which technologies do you use?

Python (Django, FastAPI) or TypeScript (Node.js, NestJS) on the backend, React on the frontend, PostgreSQL and Redis for data, and Docker/Kubernetes or simpler hosting depending on scale. If you already have a stack, I work in it.

Can you take over an existing codebase?

Yes. I start with a short audit — architecture, tests, deployment, the risky parts — and give you a written plan before changing anything.

Do you handle design?

I build clean, responsive interfaces and can work from your designer's files or produce a straightforward design myself. For brand-heavy products I recommend a dedicated designer and I work alongside them.

How do we communicate?

A shared channel (Slack, WhatsApp or email), a weekly written update, and a demo whenever there's something new to click on. You always know what's done, what's next and what's blocked.