Software Engineer — Backend · Acting team lead · Cairo
I build the systems behind apps and websites: the parts that take payments, carry traffic and keep servers running. When something goes wrong, it stays small and is easy to fix.
All circuits normal
Trip a breaker to see how each system handles its worst everyday failure.
Illustration running in your browser. It follows the real systems’ rules; nothing here touches them.
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 · Traffic
Moving customers to a new system with no downtime
Every request to the company’s API passes through it. It lets the team move customers to a new system one at a time, and move them back instantly if anything looks wrong.
My part I designed and built it.
Circuit 2 · Money
One checkout for six payment methods
The company’s products take payments and subscriptions through it: cards, PayPal, crypto and more. Even when a payment provider sends the same message twice, the customer is charged and credited exactly once.
My part I started it, led two rebuilds and ran its releases.
Circuit 3 · Tasks
A new platform designed for tens of millions of requests a day
The next version of the company’s main API, designed to handle far more work while keeping server costs inside a set budget. It is built and running on nine servers; customers move to it next.
My part I designed it, wrote most of it and lead the team.
Circuit 4 · Machines
Servers set up from one file, safely
A tool that creates the platform’s servers automatically. It always shows what it will change before doing anything, and it can never buy the same server twice or delete one by accident.
My part I wrote it, every commit.
Capabilities
The server side of your product: APIs, integrations, data and admin tools, built to be reliable. I also rebuild old systems without breaking what already works.
Laravel · Go · NestJS · MySQL · Redis
Checkout, subscriptions, renewals and refunds with Stripe, PayPal, Paddle and other providers, with every payment counted exactly once.
Stripe · PayPal · Paddle · Tap · BTCPay
Servers, deployments and monitoring, set up so your system can serve more users without the costs running away.
Docker · Hetzner · RabbitMQ · Grafana
Turning business needs into a clear plan, reviewing code, making the technical calls and keeping delivery on track.
Planning · Code review · Delivery
How I work
Nothing important changes without a preview and a confirmation first.
Repeated messages from a payment provider can never charge or credit a customer twice.
If one part goes quiet, the rest keeps running on the last information it knew was right.
Updates go out one server at a time and stop at the first sign of trouble.
About
I started in 2023 building full-stack PHP apps and kept following the work downward: payments first, then platforms, then the servers they run on.
I like systems where a mistake is expensive: money, live traffic, production data. So I plan for the bad day first. Dry runs, a single switch back, records that can’t count twice.
Today I’m acting team lead at ABM Egypt. I plan the work, review the code and still write a lot of it. I work in Arabic and English, and I’m open to relocation and remote work.
Contact
I’m open to full-time roles, remote or with relocation, and to freelance projects. Email is the best way to reach me.