I build the data infrastructure businesses run on.
Most data problems aren't data problems. They're architecture problems — unclear ownership, inconsistent definitions, systems that were never designed to talk to each other. I work at that level: not just building pipelines, but designing the stack that makes pipelines worth having.
Start with the business problem
Technology is a means. I spend the first part of every engagement understanding what decisions need to be made, what data those decisions require, and what's currently getting in the way. The architecture follows from that — not the other way around.
Build for the team that inherits it
A platform that only the person who built it can maintain is a liability. I write documentation, design for debuggability, and make deliberate choices about complexity. The goal is a system the next engineer can understand and extend — not one they have to reverse-engineer.
Governance isn't a retrofit
Access controls, data ownership, retention rules, compliance mapping — these aren't things to add later. I treat them as design constraints from the first schema conversation. It's always cheaper to build governance in than to bolt it on after an audit.
AI readiness is a data quality problem
Most AI projects stall before the model is ever trained — because the data underneath isn't clean, consistent, or governed. Building AI-ready infrastructure means getting the semantic layer right, documenting lineage, and designing for the retrieval patterns AI systems actually need.
How I engage
I work best in early-stage environments where the data function is being built from scratch, or in established teams where technical debt has accumulated faster than trust. I've been the first data hire multiple times — which means I know how to move fast without building things that have to be torn down later.
Compliance & governance
Governance isn't a separate workstream in my engagements — it's part of the schema design conversation. I've run full data mapping exercises across multi-tenant SaaS platforms, covering PII classification, data flows, retention rules, and ownership. The compliance architecture goes in before the first client onboards, not after the first audit request.
Based in
Cairo, Egypt
Available for
Remote (US / EU timezones)
Background
Operations Research & Decision Support
Languages
Arabic (Native) · English (Professional)