Ahmed Elhadi.
Builds backends that
scale to millions.
Backend-focused engineer with 5+ years shipping fintech platforms, enterprise event systems, and real-time applications on AWS, Kubernetes, and event-driven architectures.
Five years writing the kind of systems people only notice when they break.
I gravitate to backend work where the constraints are real: latency budgets, ordered events, partial failure, and the long tail of edge cases that decide whether a product feels reliable.
I'm Ahmed Elhadi, a full stack engineer based in the UAE. My day-to-day is Node.js, TypeScript, NestJS on the server with Vue, Angular, and React when the work reaches the front-end — but the through-line is systems thinking.
Across fintech, events, and enterprise tooling, I've designed message pipelines on Kafka and RabbitMQ, caching layers with Redis, and microservice topologies that survive the kind of load real customers put on them.
The work I'm most proud of is the boring kind: handler timeouts you never have to think about, retries that don't deadlock, deploys that don't wake anyone up.
Enterprise Event Platforms
Built ticketing, scheduling and operations systems serving thousands of concurrent attendees.
Fintech Trading Systems
High-frequency data ingestion, latency-sensitive APIs, idempotent transaction pipelines.
Real-Time Communication
WebSocket gateways, presence systems, fan-out messaging on Redis pub/sub and Kafka.
Distributed Architectures
Service decomposition, event-driven boundaries, saga orchestration and observability.
Cloud Infrastructure
AWS, Kubernetes, infrastructure-as-code, CI/CD pipelines and zero-downtime deploys.
An architecture map, not a progress bar.
Tools are evidence, not identity. Here's the rough topology of what I reach for, organised the way I actually think about a system.
Elhadi
The shape of the systems I build.
A canonical layout of a production system I've shipped variations of — click any node to see the specifics. Data flows top to bottom; events fan out sideways.
Trading Service
Order ingestion, position keeping, idempotent settlement.
Roles where the systems thinking actually shipped.
Four roles, four very different problem spaces — fintech, events, ERP, sports — same underlying habit of building for failure first.
- Designed and shipped scalable backend services in NestJS + TypeScript for an enterprise event platform.
- Built real-time communication channels for live attendee experiences using WebSockets and Redis pub/sub.
- Introduced caching strategies that reduced p99 latency on hot endpoints by ~60%.
- Tuned PostgreSQL and MongoDB queries and indexes to handle a 4× growth in concurrent events.
- Built fintech trading platform components with strict idempotency and audit guarantees.
- Ingested high-frequency market data through partitioned event streams with exactly-once handlers.
- Designed scalable REST + WebSocket APIs serving trading dashboards.
- Owned testing pyramid + monitoring, including synthetic probes and SLO-based alerting.
- Built ERP backend services on Express.js for inventory, orders and accounting flows.
- Refactored a monolith database schema, cutting reporting queries from minutes to seconds.
- Introduced CI pipelines, code review standards and deployment automation.
- Shipped React features across internal tooling, focusing on accessibility and clean component APIs.
- Wrote integration tests and helped resolve a backlog of edge-case bugs.
Selected systems work.
A few projects that capture the kind of work I enjoy: high-throughput, multi-tenant, and production-real. NDAs apply; what I can share lives below.
AlphaForge — Real-time market platform
A trading platform with millisecond-sensitive ingestion, idempotent settlement, and audit-grade traceability. Designed the event-log topology and partitioning strategy that survived burst loads from market open.
7 Pulse — Event ops hub
Backend for live event ticketing, scanning, attendee comms and operator dashboards. Designed the hub-and-spoke event topology around a domain bus.
Live comms gateway
WebSocket fan-out with Redis pub/sub, presence tracking, and worker pools for back-pressure aware delivery to mobile and web clients.
Internal services platform
Reusable platform for spinning up NestJS microservices on Kubernetes with auth, observability and CI/CD baked in. Cut new-service setup from days to hours.
A living ecosystem, not a tag soup.
What I reach for, grouped by responsibility. Inner rings are the dependable defaults; the outer ring is the infrastructure that keeps them honest.
Let's build scalable systems
together.
I'm taking on selected contract and full-time work in 2026. Backend-heavy, distributed systems, and cloud platform projects are where I do my best work.