I solve problems by building reliable systems.
I'm Moaz Essam, a software engineer in Cairo. I've been writing software since 2021, when I studied front-end web development and game development side by side. Real projects started in earnest in 2025: a multi-tenant fitness platform with 288 row-level security policies and the harness that proves them, a CLI that lets agents from different vendors work one codebase as a team, and a single-file network analyzer that a support floor uses every day.
By day I work at Vodafone Intelligent Solutions. I started on the front line for complex home-broadband faults, moved to support manager handling escalations, and now sit in proactive operations. Every one of those roles came with the same question: why is this done this way, and what would it cost to do it properly? The answers became WireTrace, six automated initiatives, a KPI dashboard that didn't exist before, and many more internal Vodafone UK and VOIS projects and automations.
I use coding agents heavily, and I run them the way I'd run a team. I write the spec, split the work, and read every diff before it lands. Nothing ships on a green exit code alone: I re-run the verification myself. When an agent gets something wrong, the fix becomes a CI test, a skill, or a line in the rules file it reads every session, so it doesn't happen twice. The agent types; I decide. That process has its own page.
Game development is the hobby: Unreal Engine with C++, C# in Godot, Three.js on the web. Free time, because I like it.
- Location
- Cairo, Egypt
- Open to
- roles about solving problems: full-stack, backend, automation, tooling, data; remote-friendly
- Languages
- Arabic (native), English (fluent)
- Education
- Information & Systems Management, El Gezira Higher Institute, final year
- Stack
- TypeScript, React, React Native, Node, Postgres, Supabase, Python, C++, C#
- Tools
- Claude Code, Codex, Cursor, OpenCode, Antigravity, Power Automate, Power BI, Unreal Engine, Godot
What I actually do
Agentic coding
Spec first, agent implements, I review and re-run the proof.
Automation
Manual daily jobs turned into scheduled flows that fail loudly.
Data analysis
Before-and-after numbers in the metrics ops already track.
Networking and diagnostics
Games (hobby)
Work numbers are my own account; the code is on GitHub where it can be.
Vodafone Intelligent Solutions · Proactive Operations
Found the team's workload living in spreadsheets and its KPIs untracked. Automated six initiatives in about three months with Power Automate and Office Scripts, two of them fully unattended and self-flagging on anomalies, the rest down to a single manual send at the end. Proposed and built the team's first Power BI KPI dashboard; still adding metrics to it.
Vodafone Intelligent Solutions · Support Manager, complex home broadband
Handled escalations and coached front-line technicians. Noticed that "sync, no PPP" faults waited days on the one team that could read packet captures. Built WireTrace so anyone on the floor could read the router's capture and event log in a browser, cutting the wait to minutes on the cases it catches.
Vodafone Intelligent Solutions · Front-line technician, complex home broadband
Learned which faults repeat and which ones the tooling couldn't see. Started asking why.
Independent work
Raptor (multi-tenant fitness platform), crosstalk (multi-vendor agent teams), rls-harness (open source), Solari tooling, Vault benchmark. See Work.
Education
El Gezira Higher Institute, Information & Systems Management, expected 2026. Self-taught front-end and game development since 2021.