Multi-disciplinary engineer running enterprise infrastructure and delivering projects end-to-end — for clients across Saudi Arabia and India.
I build systems that listen — infrastructure, teams, code, whatever the problem actually is.
Somewhere between running enterprise networks for Aramco and KBR, co-founding a startup at 20, and getting a chamber of commerce ready to do business in China, I stopped thinking of myself as one kind of engineer. I automate what should be automated, secure what needs securing, and manage the parts that don't fit in a script.
I don't just handle pressure — I thrive in it. Off the clock, that shows up in Formula 1 — the obsession with margins, with getting one more tenth out of a system that's already been optimized twelve times — and in ranked Valorant, reading a situation half a second before it happens. On the clock, it shows up in 100% schedule adherence on projects most people would call chaotic.
I prioritize efficiency — if something takes ten steps and can take three, I'll find the three. But efficiency without purpose is just speed. I'd rather build the right thing slower than the wrong thing fast.
Margins, precision, the last tenth of a second.
Tactical reads, half a second ahead.
If a process takes ten steps and can take three, I'll find the three.
I don't build things just to ship them — I want to know they're solving something real.
KPI-driven delivery across multi-disciplinary engineering projects — on schedule, on budget, every time.
Terraform, Docker, Kubernetes, GitHub Actions — infrastructure as code, shipped and monitored.
Enterprise firewalls, VLANs, wireless design, Linux administration — the systems underneath everything.
n8n workflows and Python scripts that quietly remove ten steps and leave three.
Voice assistants, RAG pipelines, and conversational agents built on OpenAI and open models.
CEH-trained penetration testing across web, wireless, and mobile — OWASP Top 10 and beyond.