I prefer technology work that has consequences.

Systems people rely on. Platforms that need to remain operable. Decisions that affect budgets, teams, risk and customers.

Background

My experience spans IT leadership, infrastructure and cloud modernization, cybersecurity, data architecture, software engineering and production delivery across Qatar, the UAE and Syria.

I have worked both at the organizational layer—budgets, governance, teams, vendors and service continuity—and close to implementation through software delivery, system integration, data services, release management and operations. That combination shapes how I assess technology decisions: by whether they can be understood, delivered, secured and operated.

02Working Principles

Business before tooling

Start with the outcome, constraints and operating reality before selecting platforms or technology.

Architecture with consequences in mind

Design for ownership, security, integration, change and production—not just for the initial build.

Reliability is part of the product

Continuity, observability, release discipline and security belong in delivery from the beginning.

Strategy must reach production

Plans matter when teams can execute them, stakeholders can understand them, and systems remain operable afterward.

07CONTACT / DOHA

Start with the situation

A useful technology conversation starts before the tool choice.

Senior roles, modernization programs, partnerships, product/platform work and technology leadership discussions.

Discuss a technology challenge Download executive CV