For over a decade Fauzul has shipped web experiences people love as both the designer and the engineer who builds them. He designed 's brand, prototyped its dishes with generative AI, and shipped the live ordering site himself. He was design lead on Zass Organic for two years, and some of the client marks in 's portfolio are drawn by his hand, including 's own. On the engineering side it is production React, TypeScript, Tailwind and TanStack, with Storybook component libraries and WCAG 2 delivered alongside GDPR and HIPAA. This page is the working sample: one component set, a per-brand theme engine that re-skins it for Duolingo, Anthropic and Lovable, and a model running on-device in your browser. Staff/Principal range comes from nine years co-founding through Engineering Manager to CIO, and he is eager to relocate to London (Stockholm a strong second) to own the experiences that share Lovable with the world.
is the clearest version: he designed the brand, prototyped the dishes with generative AI, and shipped the live ordering site himself. is the editorial counterpart, a spec-first export catalogue on TanStack Start at the Cloudflare edge, tuned so a procurement lead on a mid-tier connection gets it in single-digit MB. One pair of hands from the mark to production.
Two years as design lead for Zass Organic, hands-on in Photoshop, Illustrator and Figma: brand language, campaigns, and the collateral that carried a delivery business through COVID. Client marks drawn by hand, including 's own, Dairyland Bangladesh and East Bengal Closet. A logo gets one look and no interaction to explain it, and that constraint is where the restraint in his interface work comes from.
He designs the system rather than babysitting every line: reusable patterns, guardrails, and an LLM-readable structure where each role is a data file that one component set renders. That is why this page re-themes per brand in hours instead of weeks. he built solo on Bolt.new during the World's Largest Hackathon and submitted to Y Combinator, which passed on it; he kept shipping it, and enterprise pilots followed. and were built the same way, in public.
A Staff/Principal design engineering seat: owning the landing pages and web experiences that share Lovable with the world. Every ask below is mapped one for one, including the one that is still a ramp. Tap any "Ask Fauzul" chip to go deeper than the summary.
Over a decade as the designer and the engineer on the same work: nine years at , plus a freelance practice that started in brand and print before it became code. is his own restaurant brand and ordering site. is a live editorial export site for a 26-year-old exporter. , acquired by Loopcloud in 2026, is the Zürich music-tech product he built from a blank canvas to 15,000+ EU users.
's ordering flow is local-first: Zustand and localStorage confirm instantly and move the guest onto a predictive timeline while the Go backend settles behind it. pairs a spec-first catalogue with a d3-geo and topojson markets map and an AVIF/WebP pipeline that holds first load in single-digit MB. turns thousands of match timestamps into localized availability heatmaps and one-click Discord invites. This page is the fourth sample.
ran four pop-ups before committing to a flagship location, so the brand and the ordering flow were refined against real guests rather than in a file. got the opposite call: 200+ source photos transcoded into four widths and two modern formats, because first-load weight was the thing a procurement lead would actually feel. The trade-off gets made per surface, not by rule.
React with TypeScript, Tailwind and TanStack (Query and Start), state from Zustand through Redux and RxJS, shared component libraries in Storybook, and NX monorepos holding and Elobooks together so several engineers could ship without fragmenting the codebase. Accessibility is not a retrofit: WCAG 2 was delivered alongside GDPR and HIPAA across five client organisations.
There is no handoff gap because both jobs are his. went from generative AI food prototypes to a live site. Elobooks was designed end to end in Figma, IA through flows, components and brand, then built with him as lead engineer. started as Figma blueprints so Dhaka and Norway engineers shared one picture before anyone wrote code.
's instant-confirmation ordering and 's readable-at-a-glance availability heatmaps are the interaction bar he sets for himself. On this page the per-brand motion is his: defined once as reusable primitives, then re-tuned per brand, written in React and TypeScript.
's front end started from a blank canvas as React plus Storybook, and he stood up the pod that grew it on an NX monorepo with shared libraries. This page's theme engine is the same idea pointed at brand: one component set, per-brand tokens, and pages for Duolingo, Anthropic and Lovable that share almost no visual DNA.
The browser-limits work is real, but it is not WebGL. The chat on this page runs Gemma on-device through WebGPU and MediaPipe, so answers are generated in your browser rather than round-tripped. was four years of collaborative browser audio tooling on the Web Audio API with WebSocket multiplayer. 's markets map is d3-geo over a topojson atlas.
Shader-driven WebGL and 3D scenes are the piece he has not shipped in production. The adjacent muscles are there, GPU work in the browser and realtime audio, and he would rather ramp on a marketing surface that has to ship than on a demo.
Ask him to build the workspace for Staff / Principal Design Engineer, Web. Here is what ships first, generated the way Lovable generates everything else.
Build the day-one workspace for the Staff / Principal Design Engineer, Web seat.
Building your workspace…
Ran this shape for nine years at ELO, across ten client geographies and five time zones.
The JD's own example: Monday's priority reframed by Wednesday. This is the meeting that catches it before it costs a sprint.
Agenda, pre-reads, and the follow-through system that makes decisions survive contact with the week after.
Shaping how the CEO communicates, which is the half of this role nobody sees.
Over a decade as the designer and the engineer on the same work: nine years at ELO, plus a freelance practice that…
Two years as design lead for Zass Organic, hands-on in Photoshop, Illustrator and Figma: brand language, campaigns,…
React with TypeScript, Tailwind and TanStack (Query and Start), state from Zustand through Redux and RxJS, shared…
Set the hiring bar at ELO and held it while scaling from zero to 22 engineers.
Ran the loop end to end, including the hard conversations at the offer and headcount stages.
The part most trackers skip: whether the leader actually lands, and stays.
Claude-led for client delivery. Everything else is deliberate experiment: skills, hooks, harnesses, and loops that cut cost, tokens, and time-to-ship.
When a workflow shows up more than once, I turn it into an agent skill with reusable instructions and triggers, rather than a one-off prompt.
Most builds add hooks, tools, or plugins aimed at lower spend, tighter token use, and faster delivery. It is deterministic control in the places where prompts alone waste budget.
Recently connected Claude to Antigravity CLI (agy) so image generation rides an existing subscription, iterating taste-of-design and sharpening a design skill through that loop.
Claude Code for primary client build work; Antigravity and others when the task or token budget asks for it. This site's chat runs on-device Gemma 4 E2B (WebGPU + MediaPipe, model hosted on R2). NewScriber scripts with Kimi via OpenRouter and voices with Gemini TTS via Azure.
He does not hold US work authorisation, and he is not going to pretend the route is already solved. He is ready to relocate to New York and to start remotely while a visa runs. What he brings to that conversation is a decade of working across borders on someone else's clock: delivery for clients in London, Zurich, Oslo, Dubai, Florida, Montreal and Laval, and a working history of moving between markets and design cultures without needing a local playbook handed to him.
The posting lists WebGL as the ideal edge and he has not shipped it in production. What sits next to it is real: the chat on this page runs Gemma on-device via WebGPU and MediaPipe, was four years of Web Audio and WebSocket multiplayer in the browser, and 's markets map is d3-geo over a topojson atlas. He learns a technology by shipping a page with it rather than reading about it first.
The same instincts Lovable names as its own values show up in how he already works, not just what he'd promise to do.
The direct answers: seniority, real brand and web range, whether he writes production frontend solo (he does), where WebGL still is a ramp, and relocating on-site. Ask the agent anything these do not cover.
In the ownership rather than the years. I co-founded in 2017 and spent nine years there, Engineering Manager from 2022 and CIO from 2024, and I stepped out of the operating role in August 2026 to stay on as a stakeholder and advisor. For a design engineer that matters in one specific way: the taste calls and the deadline calls landed on the same desk, mine, with the numbers attached. I also coached engineers into leadership and handed over mission-critical operations, and two of them now lead teams in Norway. What I never stopped doing was writing the frontend myself.
Yes. I designed 's brand and built its site. I was design lead on Zass Organic for two years, brand language through campaigns and collateral, produced directly rather than art-directed from a distance. Client marks are mine too, including 's own, Dairyland Bangladesh and East Bengal Closet. was a different brief: a 26-year-old export house with more institutional knowledge than most tech-first brands, where my job was to organise it into a surface rather than invent positioning. And this page is a brand artifact in itself, one component set re-themed for Duolingo, Anthropic and Lovable, with the motion a landing page lives or dies on.
Yes, and it is an easy yes. I write, ship and maintain production React, TypeScript and Tailwind on my own. This page is live proof, built and deployed by me. I do not hand designs over a wall: I design in Figma and then build them, which is exactly why Design Engineer fits me better than a pure-design or pure-engineering seat.
Yes, and that is the demonstration. It is not a one-off. Each role is a structured, LLM-readable data file plus references, and one component set re-themes per company. The agent you are talking to runs Gemma on-device in your browser through WebGPU and reads my real project context to answer live. The takeaway is that I can own a web system and steer it with AI to adapt fast, which is the muscle Lovable is built on.
Conviction from a builder who tested the field. I burned $700 on bolt.new the night it launched, and I had pushed Cursor hard before that. When I got to Lovable the read was decisive: it was the one that understood where AI generation actually breaks for a person, that the model handles raw code while a human still drives product orchestration. I have since put non-technical friends onto it and watched them ship. That a category-defining AI product was built outside the Bay Area, on craft and human-led design, is a big part of why I am relocating.
Yes, happily and on purpose. London is the personal first choice: my sister lives there, I have delivered for London clients for a decade, and finally supporting Arsenal in person makes this a long-term move rather than a posting. Stockholm is a strong second and I would relocate there just as readily, a short flight from my closest friend in Oslo and from my sister in London, and the region is not abstract to me after leading Frontgo's engineering pod in Norway through the Vipps integration. After years remote-first I want to be in the room for high-craft, fast-iterating work. I can start remotely while the permit processes, and a 900+-day French streak, kept while building in public, is my evidence that I show up.
Genuinely ready to work from New York full time, on the CEO's clock.
