04/About
I’m a senior full-stack engineer with 7+ years building for the web. Front end in Vue, Nuxt and TypeScript; back end in Node and NestJS with Prisma, PostgreSQL and Redis; Docker, Nginx and CI to ship it. I design the architecture, write the code and run it in production — the same person, end to end.
In 2026 I co-founded VibeSEO, an AI SEO platform (NestJS, Prisma, Redis, multi-LLM). As CTO I built the product and led a team of 6 until it wrapped up in July 2026. Before that: axcapital.ae built from scratch, and a B2B product taken 0 → production in two months that later won a grant. 20+ projects shipped.
I work directly and in writing: one engineer from architecture to deployment, scope agreed before code, a staging link that updates as I build, a short demo every week. I’ve also led — a front-end team in Dubai, engineering at VibeSEO as CTO — and can own a codebase, a roadmap, or both.
04.1/Track record
Teaching, then front end, then the whole stack, then the whole product. Four places, some of them overlapping.
Co-founded an AI SEO automation platform and built it as CTO with a team of 6. It ran in production until the project wrapped up in July 2026.
Production front-end for client applications; moved from developer into the front-end lead role.
Built axcapital.ae, a Dubai real-estate platform, end to end: corporate site, admin, and a Three.js 3D apartment viewer.
Taught programming to 1000+ students.
04.2/How I work
Six habits from seven years of shipping. Each one came from a problem I have already paid for once.
A short brief becomes a written scope and a fixed quote before I open the editor. Changes are agreed as changes — before the work, not after it.
When a request lands mid-build, I hold it against the brief. Usually it becomes a small, priced change.
Full source in your repo, a README that gets a new engineer running, CI config included. There is no dependency on me to keep the product alive.
I’ve inherited enough undocumented projects to never hand one over.
Progress is a URL, not a status report. Staging updates as I build, with a short demo each week, so misunderstandings surface while they are still cheap.
The first demo is usually where a line in the spec turns out to mean two different things.
If a one-pager solves it, I won’t build you a SaaS. If WooCommerce fits, I won’t rewrite it in Nuxt. Technology has to pay for itself inside the product.
Sometimes the honest answer is “you don’t need an app for this.”
Vue, Nuxt, TypeScript, Node, PostgreSQL: widely used, well documented, easy to hire for. Novelty goes into the product, not the toolchain.
In three years you won’t be hunting for someone who remembers how it works.
A month of support is included after launch; after that, hourly work. I ran VibeSEO in production, so I know the second month matters more than launch day.
Some projects have stayed with me for years — because the product kept growing.
04.3/Toolbox
Send the idea, the repo or the half-built thing. I answer with questions first, then a written scope. Hiring? Tell me which role.