About Abdelrahman Mahmoud Youssef — software engineer in Giza, Egypt

About

Software Engineer, backend-heavy background.

I'm Abdelrahman — a backend-focused full-stack engineer based in Giza, Egypt, working mainly in Node.js, NestJS, and TypeScript, with PHP/Laravel on the stack too. I build production systems end-to-end — data model, API, integrations, and the UI on top — and I care about the parts that keep them correct under load: payments, queues, multi-tenancy, and idempotent integrations.

Recent work: a multi-tenant, multi-vertical marketplace on a TypeScript monorepo with Stripe Connect payments and an SSE notification engine; a multi-tenant loyalty SaaS issuing live Apple Wallet and Google Wallet cards; and a salon/coaching booking platform with an availability engine, payouts, and a transactional outbox.

Before that I built 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 booking SaaS, live), KeepComing (loyalty SaaS with wallet integration), and a multi-vertical marketplace monorepo — plus contract integration work in legal-tech and live broadcast.

TypeScriptNode.jsNestJSPHP / LaravelPostgreSQLMySQLRedisBullMQPrismaDrizzleStripeDockerNext.jsReact
Open to full-time Software Engineering roles
Giza, Egypt · Available to relocate to UAE or Saudi Arabia

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
  • Payments, queues, and integrations that stay correct under failure
  • PRs that read like changelogs — reviewable, revertable, traceable

Recently shipped

LinkedIn GitHub
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.

Node.js
NestJS
TypeScript
PostgreSQL
Redis
BQ
BullMQ
Next.js
React
Laravel
PHP
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
  • A thin serverless function would do the job
  • 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
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.