Four Principles

Riyadh needed its city operations digitized into a single automated system, with the security and scale a government platform cannot compromise.

As senior software consultant, drove the digitization: an automated system for the city, following the most secure practices and architected to scale from day one.

Good architecture does not spread by memo. With projects multiplying, the mid-level teams needed one shared way to think about component design and structure, or each project would reinvent it from scratch.

Ran regular mentoring with the mid-level engineers on component design and architecture: the patterns, the boundaries, and the tradeoffs behind each call, reviewed against real project code instead of slides. The habits carried from one project to the next.

A government-scale system has to be secure and operable before it can be clever, and that is never a solo effort.

Built the core system in close collaboration with heavy DevOps and security teams: threat models, hardened delivery pipelines, and security review baked into every release rather than bolted on at the end.

A city portal has to stay fast and steady whether a hundred or a hundred thousand people arrive on the same morning.

Engineered the portal for scalability: stateless services, caching where it earns its keep, and an architecture that grows sideways under load instead of buckling.