About me
Full Stack Developer building enterprise platforms, government systems, and environmental intelligence. Currently at 4D · Saudi Arabia. Previously led IT operations for the Egyptian Armed Forces and taught programming to 50+ students.
I care deeply about clean architecture, real-time systems, and building software that lasts.
Selected Work
Selected platforms and automation tools I've built for organisations and teams. Each one shipped to real users — not a demo.
Saudi government health platform, rebuilt
A public health platform serving citizens and clinicians — a modernised content platform, healthcare atlas, and certificate verification system. I audited the legacy monolith, made the case to leadership for a full rebuild, then delivered it solo as an API and a single-page app.
AI-powered recruitment platform
Connects applicants, AI screening, and interviews in one place. Applicants upload a CV and the form fills itself. HR gets AI-ranked candidates, weighted scoring, and interview scheduling with calendar invites.
White-label multi-tenant SaaS
One platform for multiple client companies. Each tenant gets its own dashboards, maps, and an integrated AI assistant. Onboarding a new tenant is one record in an admin panel, not a code change — each tenant brokers its own upstream API through encrypted credentials.
Telegram task management for organisations
Manages team tasks inside Telegram. Three-tier roles, a reviewed task lifecycle with revision loops, cloud file attachments, and scheduled reminder and unreachable-user detection jobs.
Journey
Ain Shams Academy
Egyptian Armed Forces
Oraby Academy
Education
Faculty of Computers and Information, Suez University
Case Study
A production bug on ncmh.org.sa that no amount of application debugging could explain — because the application was never the problem.
A single page of the healthcare-facilities Atlas returned HTTP 500 in production. Every other page worked. There was nothing in any log — not Laravel, not PHP, not Apache.
A HEAD request to the failing URL returned 200. A GET to the same URL returned 500. Running the identical query under artisan tinker produced a clean result. The application was not the thing failing.
If the response body was the trigger, the body would tell me. I bisected the JSON over HTTP — removing fields, re-requesting, narrowing — until a single field flipped the response from 200 to 500.
A network-level WAF appliance sitting in front of the server inspects response bodies. One facility record held a sixteen-digit licence number that happened to satisfy the Luhn checksum, so the appliance's credit-card DLP signature concluded the API was leaking a payment card and swapped in its own block page. Only that one Atlas page broke, because it was the only page containing that record.
I removed the licence number from public API responses. Nothing in the frontend consumed it, and it should never have been exposed publicly in the first place — so the correct fix and the minimal fix were the same change.
I documented the failure mode and the proper long-term remedy — a targeted WAF signature exemption rather than shaping payloads around it — in the repository's engineering notes, so the next person to hit it does not lose a day to it.
Most bugs live in your code. Some live in the infrastructure nobody told you about. Knowing which one you're looking at — before you start rewriting things — is the difference between an afternoon and a week.
A Saudi government mental-health platform I rebuilt from a legacy monolith into a versioned Laravel REST API powering a Vue 3 + TypeScript single-page app. I audited the old codebase, made the case to leadership for a full rebuild, and delivered it solo.
Contact
Available for full-time roles, freelance projects, and teaching opportunities. I respond within 24 hours.
