Backend Software Engineer · Laravel · NestJS · AI Engineering · Port Said
I build the systems behind SaaS products and money: trades, wallets, permissions, subscriptions and the background jobs that carry the heavy work. When two things happen at once, the data still comes out right.
All circuits normal
Trip a breaker to see how each system handles its worst everyday failure.
Illustration running in your browser. It shows each system’s approach in simplified form; nothing here touches the real systems.
Selected work
What each one does, in plain words. Open a case study for the technical detail and a model you can try.
Circuit 1 · Money
No two buyers can take the same piece of gold
The trading core of Estore, an asset-trading platform. Gold prices move fast and many people can buy at once, so every trade is locked for the instant it runs and every piece is tracked by serial number.
My part I architected and built it.
Circuit 2 · Access
Fast, correct permissions across 38+ modules
A SaaS ERP with 38+ modules and 7 mobile apps. I rebuilt who-can-do-what across every module, made it fast with event-driven caching, built the dynamic subscription engine, Leaflet geofenced attendance, open-source payment packages, and mobile APIs.
My part I re-architected access control and built the subscription engine, payment packages and mobile API.
Circuit 3 · Tenants
One codebase, a subdomain per customer
A multi-tenant SaaS CRM in NestJS. Every customer gets their own subdomain: the app works out which tenant a request belongs to, checks permissions with guards, and takes payments through Paddle.
My part I engineered the backend architecture.
Circuit 4 · Jobs
Heavy money reports that never slow the app
A private enterprise system for running rentals. A Laravel core with a separate Node.js service for WhatsApp. Heavy financial reports run in the background, and tenants hear from the system by app, email or WhatsApp.
My part I architected and built it.
Capabilities
The server side of your product: REST APIs, microservices, modular monoliths, and data integrity, built clean, secure and reliable.
Laravel 11 · NestJS · Node.js · PostgreSQL · MySQL
Trades, wallets, deterministic financial reconciliation, and subscription billing: locks, HMAC signing, idempotency keys, and exception-driven audit trails.
Redis locks · HMAC · Paddle · Payment Gateways · Idempotency
One codebase for many customers with isolated tenant data, wildcard subdomains, fine-grained RBAC permissions, and dynamic subscriptions.
RBAC · NestJS guards · Nginx wildcards · Laravel
Integrating LLMs, RAG, Agentic AI, and Vector Databases into backend production systems, using AI-assisted workflows to accelerate delivery.
LLMs · RAG · Agentic AI · Vector DBs · MCP · Claude Code
I run and observe what I build: Ubuntu servers, Docker, Supervisor, Horizon queues, CI/CD pipelines, and observability with Grafana and Telescope.
Ubuntu VPS · Docker · Supervisor · Horizon · Grafana · Telescope
How I work
Two orders for the same item are handled one at a time, so nothing is sold twice.
Wallet requests are signed, so a tampered payload can’t change a number.
Permission checks are cached, and an event clears them the moment a rule changes.
Slow jobs run in the background, so the app stays fast for the people using it.
About
I’m a backend software engineer with an engineering background from Port Said, Egypt. I work extensively across Laravel and Node.js/NestJS, and I own the full lifecycle of what I build: Linux VPS, Nginx, Docker, Supervisor, queues, and Redis.
I specialize in systems where mistakes cost money: gold trading, digital wallets, multi-tenant ERPs with 38+ modules, and deterministic financial reconciliation. I plan for the bad day first: data integrity, idempotency, clean architecture, and observability with Grafana and Telescope.
I also expand backend capabilities with AI Engineering (LLMs, RAG, Agentic AI) and modern AI workflows. I work remotely and I’m open to new production challenges.
Contact
I work remotely and I’m open to new projects. Email is the best way to reach me.