I'm a Senior Backend Engineer & Software Architect based in Cairo, Egypt, with 7+ years in PHP/Laravel. I've spent that time on both sides of the fence — building enterprise-scale systems at places like Spryker, Actindo, IHF, and the Islamic Development Bank, and architecting my own products solo from scratch.
I like taking systems that are genuinely hard to reason about — pricing engines, workflow orchestration, multi-party settlements, API integration layers — and rebuilding them so the next engineer (or future me) can read the diagram and just get it. That's the "bedtime story" part: complexity should be explainable, not just functional.
🚕 The one about the mobility platform I built alone
SinaiTaxi is a mobility platform I solo-architected as a 35-module modular monolith, using Domain-Driven Design and hexagonal architecture.
Inside it:
- A geo-polygon pricing engine — pricing that actually understands geography, not just distance
- A multi-party financial settlement engine — splitting money correctly between drivers, partners, and the platform, every time
- A pluggable OTA connector framework — so integrating a new booking partner doesn't mean rewriting core logic
- A Pest PHP test suite wired into CI/CD, because architecture without tests is just a nice diagram
It's the project I point to when someone asks "okay, but have you actually owned something end to end?"
🧩 The one about teaching APIs to describe their own workflows
php-arazzo is a PHP package implementing the Arazzo Specification — the OpenAPI Initiative's format for describing multi-step API workflows.
It's not just a parser/validator — it includes a workflow executor/runner, so an Arazzo document doesn't just describe a workflow, it can actually run one. I built this after working on a process orchestration engine (places/actions/tokens) at Actindo, and I'm now coordinating with maintainers in the wider Arazzo ecosystem on test suites and tooling.
🏢 The one about a decade split between enterprise systems and 3am side projects
By day (and several years), I've worked inside systems built for scale: e-commerce at Spryker, ETL and queued API integrations at Actindo, and enterprise CMS platforms (Drupal-based) at the International Handball Federation and the Islamic Development Bank.
By night, I architect my own things — because the best way to know if a pattern actually holds up is to build something real with it, alone, with no one to blame but yourself.
🛠️ The one about what's cooking right now
- Extending php-arazzo toward emerging Arazzo proposals (SOAP, gRPC, GraphQL, actor-in-the-loop workflows)
Practices: DDD · Hexagonal Architecture · Clean Architecture · SOLID · TDD (Pest/PHPUnit) · REST/JSON:API · OpenAPI
I'm currently open to remote senior backend / architecture roles. The fastest way to see how I think is to read one of the stories above, then ping me.
