About Abdelrahman Mahmoud — full-stack engineer in Egypt

About

Egypt-based. Building for MENA — and beyond.

I'm Abdelrahman — a full-stack engineer in Egypt working in TypeScript, Next.js, and NestJS. Across 25+ production projects I've shipped SaaS, AI features, and automation end-to-end — data model, API, UI, deploy — with a real feel for Arabic-first, multi-tenant products built for this region: RTL UIs, WhatsApp over email, local payments, and the operational quirks generic SaaS gets wrong.

Recent work: a multi-tenant SaaS handling 1,000+ daily bookings with real-time scheduling, Stripe subscriptions, and AI photo analysis for instant quotes; a job-referral platform with queue-driven event processing on BullMQ; and an automated content pipeline integrating Claude, HeyGen, and n8n.

Before that I shipped a Digital Asset Management system processing 10,000+ media files and a custom PHP framework that lifted team velocity 40%. I write code other engineers can read, review, and extend.

Production work includes getbookra.com (multi-tenant salon booking SaaS, live), a multi-tenant loyalty platform with Apple Wallet integration for MENA businesses, and a 22-app Next.js 15 marketplace monorepo.

TypeScriptNestJSNext.js (App Router)Node.jsReactPostgreSQLRedisBullMQPrismaTailwindDockerStripeClaude / OpenAILaravelXano
Open to full-time roles & select freelance
Remote · Hybrid · On-site · GMT+2 (GMT+2)

How I think about engineering

  • Types that catch bugs at compile time, not in production
  • Queries that stay fast as data grows — not just on day one
  • UIs that hold up on the third edge case, not just the happy path
  • PRs that read like changelogs — reviewable, revertable, traceable

Recently shipped

LinkedIn GitHub Upwork
Tech Stack

Skills, ranked by honest proficiency

Not a logo wall — what I actually reach for, grouped by how deep I go.

Deep production experience — what I reach for first.

NestJS
Next.js
TypeScript
Node.js
React
PostgreSQL
Redis
n8n
Laravel
PHP
Xn
Xano
How I Pick Tools

The right stack — for your problem

I'm not loyal to any one tool. Here's how I decide which to reach for, with the trade-offs I tell every client.

Next.js

Sweet spot

Full-stack apps with great DX and SEO

Pick when
  • React frontend + API routes in one deploy
  • SEO matters — SSR, SSG, or ISR
  • TypeScript end-to-end, RSC, App Router
Skip when
  • Pure API with no UI — use NestJS instead
  • Complex real-time — pair with a dedicated WS layer
  • Team is not on React

NestJS

Sweet spot

Long-lived multi-tenant SaaS

Pick when
  • Multiple services / queues / workers
  • Domain logic complex enough to model properly
  • TypeScript end-to-end, OpenAPI, DI matter
Skip when
  • Tiny CRUD app — overkill
  • You'd ship faster on Xano or Supabase
  • Team is more comfortable with PHP / Python

Laravel

Sweet spot

Classic CRUD apps with great tooling

Pick when
  • PHP team / hosting constraints
  • Server-rendered admin panels (Filament, Nova)
  • Battle-tested ecosystem, fast scaffolding
Skip when
  • Primarily an API serving a SPA — TS pays off more
  • Real-time / streaming is core
  • Heavy queue + microservice topology

Xano

Sweet spot

Ship a real backend in days

Pick when
  • MVP under tight deadline
  • Non-technical stakeholders need to peek
  • Standard SaaS shape — auth, CRUD, Stripe, webhooks
Skip when
  • Heavy realtime (sockets, streaming)
  • CPU-bound jobs or fine-grained perf tuning
  • You'll outgrow no-code limits in 6 months
How I work

Engineering, end-to-end

The shape of how I move from a vague problem to production code that holds up.

01

Understand

Read the code, talk to users, name the constraints — before writing anything

02

Architect

Map data models, define contracts, surface trade-offs in writing

03

Build

Type-safe code, tests where they pay off, PRs that read like changelogs

04

Ship

Deploy with monitoring, alerts, and a rollback plan — never on Friday

05

Iterate

Measure, learn, refactor. The second version is always better than the first.