SOOK
An owned fashion-commerce business where merchandising, promotions, discovery, and the mobile customer journey are continuously operated and improved.
View case study →Mahmudur Rahman / Dhaka → remote worldwide
I own the path from idea to production.
I turn ambiguous product ideas into production-ready digital products through product judgment, full-stack engineering, and AI-native execution.
- Next.js
- Laravel
- Supabase
- Cloudflare
- MySQL
- AI Agents
OwnerProductfrom idea to production
01Frameproblem
02Shapeexperience
03Buildsystem
04Verifyunhappy paths
05Shipproduction
Product judgmentAI leverageEngineering ownership
01Think beyond the screenflows, rules, operations, edge cases
02Build across the stackfrontend, backend, data, deployment
03Use AI as leveragespeed without surrendering judgment
04Own the outcomefrom vague brief to production
The difference
Most portfolios show what someone can design or code.
Mine shows how I turn ambiguity into a system that ships.
01 / Selected products
Built around real product behavior.
I care about the logic underneath: discovery, operations, data, admin, mobile behavior, deployment, and what happens when users do something unexpected.
Visit SOOK
SUQO
My pre-launch marketplace venture for Bangladesh, spanning customer discovery and the operational systems behind shops, catalogue, stock, orders, and returns.
View case study →
Amar Basha
A pre-launch property marketplace for curated apartment discovery in Dhaka, designed around trust and a direct path from search to enquiry or viewing.
View case study →Athar House
A mobile-first Islamic knowledge and content-discovery product organized around lectures, Qur’an recitations, scholars, series, and topics.
View case study →
MacroPlate
A guided subscription journey that brings plans, menus, macros, filters, and trust information into one clear decision system.
View case study →02 / Build Lab 2.0
Give me a problem. Watch the system take shape.
A deterministic, interactive demonstration of how I move from a brief to product architecture, risks, tests, and deployment—without pretending there is an AI API behind it.
Choose a product brief
My default question“What has to be true for this product to keep working after launch?”
The brief
Start with owned brands, then onboard external shops without rebuilding the product.
Problem
Ownership, inventory, checkout, and operations become tangled as more sellers enter the system.
Assumption
A shared catalogue model can support both owned and partner inventory if ownership rules are explicit from day one.
Decision
Model shops, variants, stock, and order states before investing in storefront polish.
- 01Problem
Multi-shop growth without operational drift
- 02User experience
Shop discovery, filters, variants, checkout
- 03Frontend
Next.js storefront and account flows
- 04Backend
Laravel APIs and Filament operations
- 05Data
MySQL: shops, SKUs, stock, orders
- 06AI / automation
Spec agents, fixtures, regression scenarios
- 07QA
Stock conflicts, roles, failed checkout
- 08Deployment
Cloudflare edge, observe, iterate
Risks I’d surface
- Seller ownership leaks
- Variant stock conflicts
- Order-state ambiguity
Unhappy paths
- Payment succeeds but stock update fails
- A seller edits another shop’s product
- A split order is partially returned
What I’d test first
Run one order with two shops, two variants, and a partial failure through the full operations path.
Build Lab updated to Multi-vendor marketplace
03 / How I work
AI is leverage. Ownership is the skill.
I use AI across research, architecture, implementation, visual production, debugging, and QA. I remain responsible for the problem, the edge cases, and what reaches production.
- 01
Frame
Users, constraints, priorities, and the decision the product must make easier.
- 02
Shape
Flows, information architecture, responsive behavior, and system boundaries.
- 03
Build
Frontend, backend, data, and integrations—with agents used deliberately.
- 04
Break
Unhappy paths, accessibility, state transitions, performance, and regression QA.
- 05
Ship
Deployment, production checks, observation, and the next useful iteration.
04 / Working stack
Full-stack enough to own the journey.
I choose tools in context. The goal is not to force every product into one stack; it is to make sound decisions and carry them through.
01
Frontend
I shape responsive product surfaces, interaction states, and component systems.
- HTML
- CSS
- JavaScript
- React
- Next.js
- Responsive UI
02
Backend & data
I model the rules, identities, records, and workflows beneath the interface.
- Laravel
- Filament
- Supabase
- MySQL
- Cloudflare D1
- APIs
- Authentication
03
Infrastructure
I take responsibility for the route from local build to a production environment.
- Cloudflare Workers
- Cloudflare Pages
- Vercel
- DNS & domains
- Deployment
- Production QA
04
AI-native workflow
Agents accelerate research, implementation, debugging, and verification. Judgment stays human.
- Codex
- ChatGPT
- Claude
- Agent orchestration
- Image generation
- AI-assisted QA
05 / Visual range
Make it work. Then make it feel finished.
Brand and visual judgment support the product work. They do not replace it.
Based inDhaka, BangladeshAvailable remote worldwide
06 / The journey2016—2021 Dec 2021—Jul 2024 Aug 2024—Present Now
I learned products from the physical world before I engineered them in the digital one.
I started around physical products: Textile Engineering, manufacturing, and international B2B commercial operations. Entrepreneurship then exposed me to customers, inventory, conversion, and the business systems behind every useful digital product.
Textile Engineering→B2B operations→Entrepreneurship→Digital products→AI Product Engineering
Textile Engineering
Systems thinking, constraints, manufacturing, and production discipline.
Experience Group
Junior Executive (Dec 2021–May 2022) → Executive (Jun 2022–Oct 2023) → Senior Executive (Nov 2023–Jul 2024). Promoted twice while coordinating LC Waikiki and New Look accounts, commercial execution, manufacturing timelines, and delivery.
Entrepreneurship & owned products
Solving my own commerce problems led from storefronts into backend systems, databases, marketplaces, and increasingly complete digital products.
AI Product Engineering
Product judgment, full-stack execution, and AI leverage. As Founder & Product Engineer, I started WARPIX Studio in November 2025 as an independent umbrella for owned products, prototypes, and experiments.
What I’m targeting
Small teams. Hard problems. Real ownership.
Remote-first product teams where business context, AI fluency, and the ability to cross traditional job boundaries are useful.
- AI Product Engineer
- Product Engineer
- AI Solutions Engineer
- AI Implementation Engineer
- Product Builder
07 / Contact
Got a product problem that needs an owner?
If you’re hiring for a remote product or AI role—or building something where a cross-functional builder would be useful—I’d like to hear about it.