Hi, I'm
I studied dentistry for five years, but halfway through I started learning to code as a hobby and couldn't stop. Five years of backend later: ad-tech, fintech, healthcare. The problems I enjoy most are the ones other people avoid.
Here's what that looks like in production:

Senior Backend Engineer
Cairo, Egypt
A few systems I've built and shipped — newest first. Each one links to a short write-up of what the problem was and how I solved it.

01 / Featured Project
Multi-tenant appointment booking backend serving barbershops, gyms, and consultants — built from scratch on NestJS + PostgreSQL. I owned the architecture end-to-end.

02 / Featured Project
Payment infrastructure work — WooCommerce plugins used by thousands of merchants, a URL shortener that cut SMS costs by 25%, and the documentation that made the whole thing easier to integrate.

03 / Featured Project
Backend performance work on an edtech platform — cut a 3-minute cronjob to 45 seconds, dropped average query time by 40%, and built the student account merge tool nobody wanted to touch.

04 / Featured Project
Built a patient management platform from scratch — schema design, API, AWS infrastructure, ICD-10 medical code engine, real-time chat, and payment integration. Three years of real healthcare system engineering.
Dentistry didn't take. Backend did.
I picked up programming as a hobby in dental school and it quietly took over. Five years later I've shipped backends in ad-tech, fintech, and healthcare — the kind of systems where a bad night means real money or real patients, not a missed sprint.
Most of my work is in Node.js and NestJS. I keep clear boundaries between modules and design the database carefully up front, because the real cost of a system isn't writing it — it's the next engineer trying to change it six months later. Monitoring, CI/CD, and boring, predictable deploys are part of the job, not an afterthought.
I keep one eye on the bill and one on the user. Cutting infra cost, shaving a few hundred milliseconds off a hot path, or deleting a workflow nobody needed — that's the work I actually enjoy.

Oct 2025 — Present·Remote

Jan 2025 — Sep 2025·Remote

Jul 2024 — Jan 2025·Hybrid·Cairo, Egypt

Sep 2023 — Jun 2024·Remote

Mar 2020 — Aug 2023·Remote















Validates expertise in designing distributed systems, cost-optimized architectures, and resilient applications on AWS infrastructure.
Verify CredentialI take on a handful of backend and cloud projects at a time. If any of these sound like your situation, we'll probably work well together.
“My API is slow and I don't know why.”
“I need payments working before launch.”
“My AWS bill makes no sense.”
“We need an API built from scratch.”
“Our deploys are scary and manual.”
“The codebase is a mess to change.”
I work best on longer engagements where I can actually learn the domain — not one-off tickets.
Get in TouchHiring, building something, or just want a second opinion on an architecture decision? Drop me a line — I read every message and reply to the real ones.
Open to new projects and senior backend roles.