Backend
Services built for regulated domains, real traffic, and on-call support.
open to opportunities
Senior Software Engineer / Software Architect
Cairo, Egypt · UTC+2 · remote
I turn messy enterprise systems into reliable products fast. From national infrastructure and regulated fintech platforms to AI-native builds, I design systems that survive real production pressure.
Capabilities
Services built for regulated domains, real traffic, and on-call support.
Interfaces that stay maintainable after the third team touches them.
Agentic systems, orchestration, and LLM architecture that survives a budget review.
Infrastructure and delivery flows that keep teams shipping under pressure.
Case studies
5 of 11. Each one links to the full write-up with the decisions, trade-offs, and a working demo.
A wallet service where two bets placed at the same instant could both spend the same balance.
Row lockcheck and debit in one transaction
Under load, concurrent bets on one account raced each other.
Moved the check and the debit inside a single transaction that takes a lock on the wallet row before reading it.
Writes to a single wallet now serialize, so a hot account is a throughput ceiling no number of instances can raise.
Betting Wallet Redesign — request path
Agents that read the screen as pixels and drive legacy desktop software that offers no API to call.
< 2sscreenshot → action
Businesses need to automate complex desktop workflows — filling forms, navigating legacy software, extracting data from screens — but traditional RPA is brittle and breaks when UIs change.
Built a production platform on Claude Computer Use API with a Python/FastAPI backend.
Vision-driven control is slower and costlier per step than scripted RPA, and it is non-deterministic — every action needs a verification read-back before the next one is safe.
Computer-Use Agent — request path
Payment services split along the boundaries that matter — gateway, payments, ledger, notifications — carrying millions of records a day.
MillionsRecords / Day
High-volume payment traffic needed dependable services and fast production fixes — millions of records a day flowing through gateway, payments, ledger, and notification paths, where downtime or backlog has direct financial impact.
Delivered .NET Core microservices with clear service boundaries, Redis-backed hot paths, and Docker-based deployment, plus the hotfixes and operational support that keep a high-throughput payments platform healthy under real load.
Clear service boundaries cost cross-service consistency — transactions stay inside a single service and the ledger reconciles afterwards.
Enterprise Payment Microservices — request path
A multithreaded calibration pipeline that took smart-meter manufacturing from one meter per cycle to forty.
40×1 → 40 meters per cycle
Manufacturing throughput was capped by a slow, sequential calibration workflow — each meter processed one after another, leaving expensive production lines waiting.
Re-architected calibration around a multithreaded, batch-oriented pipeline tuned to the production hardware.
Parallelising the line meant giving up a simple failure model: one meter faulting mid-grid must not take the other thirty-nine with it, so per-slot error isolation and recovery became the real work.
Smart Meter Calibration System — request path
Dynamic 835/837 EDI and HL7 parsers that turn messy, multi-vendor healthcare interchange into reliable structured data.
835/837EDI Formats Parsed
Clinical and billing systems exchange data as dense X12 EDI (835 remittance, 837 claims) and HL7 messages that vary by vendor and break rigid parsers.
Built schema-driven parsers that tokenize the X12 stream, resolve segment definitions dynamically, validate loops and control numbers, and normalize everything into internal claim and remittance models — then route the results through Iguana, a fax gateway, or internal services.
A schema-driven parser is slower and harder to debug than a hand-written one per vendor, and it adds a schema registry to maintain.
Healthcare EDI & HL7 Integrations — request path
System design
Whiteboard defaults I reach for before reaching for anything clever.
Most business software is this shape. The work is in the boundaries, not the boxes.
An agent is only as good as the context it is handed. Retrieval is the product; the model is a dependency.
Sockets are easy until you run two instances. Shared state is what makes it survive a deploy.
Experience
Government infrastructure, Saudi fintech regulation, healthcare interoperability, payments, manufacturing, and AI — in that order.