Shipping production software at a pace most teams need a squad for.

I work across mobile, web, and backend — using AI as a multiplier, not a replacement for thinking. The goal is always the same: something that works correctly and holds up over time.

0+
Lines of Code Delivered
Sum volume of core systems designed, implemented, and shipped solo across mobile and web client platforms.
0+
SaaS Feature Modules
Modular feature slices authored, ensuring clean separation of concerns and robust multi-tenant data boundaries.
0+
Database Schema Migrations
Idempotent database schema evolutions managed securely, backed by row-level security and optimized RPC layers.
02 //

Engineering

Early-stage engineer who owns products end to end — from schema design to App Store.

I work best in teams where implementation quality matters as much as the architectural decision behind it.

Apr 2025 - Present

Software Engineer

Etlaq

First engineer to join. Own end-to-end delivery of client products across mobile and web, contributed to PRDs, client discovery, and hiring process alongside building the engineering culture from scratch.

Jun 2024 - Aug 2024

Full Stack Developer

Nisfak

Worked inside an existing Flutter codebase, led a UI overhaul, and cut iOS CPU usage in half by profiling and optimising hot render paths with iOS Instruments and Flutter DevTools.

03 //

Draft Notes

Working notes on architecture and interface decisions.

A few essays and internal memos have turned into reusable thinking. The published set is small; the useful ideas are not.

Draft in progress

Making Flutter Apps Look Premium

The gap between a Flutter app that looks cheap and one that feels considered is rarely about features. It is about typography, motion, color discipline, and a handful of decisions most developers skip.

Draft in progress

Coupling, Boundaries, and Shared Domains

What actually goes wrong when you ignore bounded contexts in a growing codebase, and how to draw lines that hold up under real product pressure.

Draft in progress

Refactoring Slop: Inheriting a Vibe-Coded Codebase

A walkthrough of a real codebase handed off after going wrong — what the patterns looked like, how I diagnosed the damage, and what the refactor actually involved.

04 //

Conversation

Available for conversations worth having.

If something here resonated, feel free to reach out.

Location

Riyadh, UTC+3

Response time

Usually within one to two business days