Loading…
I bridge product, business, engineering and quality. I turn complex requirements into production-ready digital products and build the AI systems inside them.
Most delivery problems are not engineering problems: they live in the gaps between roles. This is the chain, and I work the length of it.
The disciplines that decide whether software ships, each described by how it is actually practised rather than by a definition.
Owning what gets built and when: shaping the backlog against business goals, planning sprints and releases, and keeping stakeholders, engineers and deadlines pointed at the same outcome.
Turning ambiguous asks into buildable requirements by mapping the process, writing user stories with acceptance criteria, and carrying them through to UAT so what ships is what was asked for.
Treating quality as a plan rather than a phase: test planning weighted by risk, manual and API testing, regression coverage, and the review standards that stop defects earlier than any test run.
Managing cross-functional teams, running delivery execution and technical operations, mentoring engineers and holding code quality across the team.
The technical stack underneath the delivery: architecture, AI systems, backend, frontend, data and cloud, ordered by how much of the work each carries.
Defining system architecture across backend and frontend teams and driving design decisions with senior stakeholders: service boundaries, data flow, and the trade-off between a monolith and a distributed system.
Integrating LLMs into production systems and designing the agent workflows and orchestration around them, treated as engineering with the same delivery, reliability and review standards as the rest of the stack.
Production services in PHP/Laravel, Node.js and Python: REST, GraphQL and distributed API design, service decomposition, authentication, and queue-backed asynchronous work.
Server rendering, state management and component architecture in React and Next.js, backed by typed JavaScript, with Angular across earlier enterprise work.
Leading cross-platform mobile development in React Native and Flutter as part of the same delivery: held to the same review, release and production standards as the web and backend work beside it.
High-performance schema design across four production engines (relational and document, in the same role), with caching, indexing and query optimisation.
AWS infrastructure, containerised services and CI/CD pipelines built for fast, reliable, automated releases, with monitoring and observability on the systems that carry production traffic.
These sit in a section of their own, on purpose. The résumé qualifies them as familiarity rather than production depth, and presenting them alongside the core areas would misrepresent it.
Working familiarity, without production depth. Listed for completeness rather than as core competence.
Have a product, platform or delivery challenge? Let’s talk about turning it into a structured, scalable solution.
Open to technical leadership, product delivery and senior engineering roles, and available for architecture consulting, technical reviews and mentorship. Engagements run as project-based work, contracts, consulting, freelance engagements, remote collaboration and long-term partnerships.
Based in Cairo, Egypt, working remotely with clients across the MENA region and internationally.