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.
Saudi Arabia · Mobile, web, full-stack product engineering
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.
- Focus
- Mobile, web, and the systems underneath
- Recent work
- Commerce platforms, real-time Systems, external integrations
- Availability
- Graduating Jun 2026
Selected work
Case studies built around constraints, decisions, and outcomes.
These are the projects I would want a hiring manager or client to review first. Each one starts with a production constraint and ends with a measurable result.
Experience
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.
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.
Writing
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.
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.
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.
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.
Contact
Available for conversations worth having.
If something here resonated, feel free to reach out.