Fauzul is a product engineer who still writes the code behind his own architecture: React and TypeScript on the front, Go behind it, shipped end to end. That is not a recent return to it. He held Principal Staff Software Engineer at before Engineering Manager and CIO, and kept shipping through all three. The receipts are live and checkable: , an ordering platform he designed, built and now runs alone, React and Zustand over a Go and ConnectRPC service; , whose first web product he took from a blank canvas to market and 15,000+ active users in Zürich before Loopcloud acquired the company in 2026; , holding a fragmented national esports scene together at 1,207 players and 47,091 matches. The judgement this seat runs on, when to ship now and when to build the floor first, is a call he has made with his own capital behind it rather than in a design review. Rust and consumer traffic at millions of users are the two things he would be picking up here. He is ready to be on-site in Stockholm, where this team sits.
is one person all the way down: he designed the brand, built the React and Zustand ordering front end, wrote the Go and ConnectRPC service behind it, and put it on Cloud Run scaled to zero. Nothing was handed over a wall, because there was no wall. He reached Principal Staff Software Engineer before Engineering Manager and CIO and never stopped writing production code through either.
's first web product went from a blank canvas to market and 15,000+ active users in Zürich, on a full-stack team he stood up around it, and Loopcloud acquired the company in 2026. consolidated a scattered national esports scene into one canonical platform at 1,207 players and 47,091 matches, and hosted the country's first nationwide league through it. Neither is a prototype that got a demo and a screenshot.
ran four pop-ups to prove demand before he committed money to a flagship location, and he prototyped the menu with generative image models instead of a photographer, which took over $10,000 out of the launch before the kitchen ran a single service. Speed versus foundation is not an abstraction when the wrong answer comes out of your own pocket.
Seven habits, each one attached to a product that is live and checkable rather than to an adjective.
from ledger design to deployment, 's ordering UI and the Go service under it, 's platform surfaces. Nothing waits on a translation layer or someone else's sprint capacity.
runs on Cloudflare Workers and R2 with a Fly.io machine holding the event stream, deployed and operated solo. 's Go service scales to zero on Cloud Run so compute cost mirrors the restaurant's opening hours.
launched with profiles and rosters ahead of match analytics, because a national hub earns the right to rank players only after it is the canonical record of who plays for whom.
's first web product, blank canvas to market and 15,000+ active users, acquired by Loopcloud in 2026. at 1,207 players and 47,091 matches. 's briefings reaching about 12k listeners a week.
Ten client geographies coordinated at once at , headcount conversations taken directly rather than routed. Two alumni now lead teams in Norway.
's brand, menu and interface are all his: dishes prototyped with generative image models as blueprints for the chef, ordering built local-first so a returning guest re-orders instantly without an account or a tracker.
Claude leads the delivery work with Gemini second, chosen per task. went scaffold to working platform in eight days on that practice, and 's entire menu was prototyped as generative imagery before a chef touched a pan.
The posting puts it in one sentence: do all it takes to build a generational product, scaling the core Lovable experience for millions of users. A hands-on Staff or Principal seat on the Product team, full stack, architecture through production, with the speed-versus-foundation call in your hands. Tap any "Ask Fauzul" chip to go deeper than the summary.
Ten years of working history since 2015, nine of them co-founding and shipping inside it the whole way, through every rung the ladder had: UX Engineer, Principal Software Engineer, Principal Staff Software Engineer to the end of 2022, Software Engineering Manager, then Chief Information Officer to July 2026. Products rather than internal tooling, 0→1 for client portfolios across ten geographies, several still running. He stepped out of the operating role in August 2026 and remains a stakeholder and advisor; everything since, , and , he has shipped solo at the same level with nobody scoping the work.
Both halves, not one padded out by the other. React and TypeScript on the front: 's local-first ordering UI on Zustand and localStorage, 's TanStack Start build with SSR or SSG chosen per page, 's React 19 and TanStack Router console. Go behind it: 's ConnectRPC service on Cloud Run, scaled to zero so compute cost tracks the restaurant's opening hours, and 's Go orchestration under an agentic audio pipeline reaching about 12k listeners a week. Node.js, NestJS and Python fill out the rest of the backend, and TypeScript runs all the way through.
The systems-design work is his own rather than something he reviewed. 's first web product reached 15,000+ active users on an architecture he started from a blank canvas and a team he then stood up around it. ingests and serves 47,091 matches for 1,207 players, with an Intl-localized availability model that reads thousands of match timestamps to predict when a player is likely online and a weighted-overlap algorithm that turns two schedules into one playable window. What none of that is: consumer traffic at millions of users. That is the real distance between his largest product and Lovable's core experience.
The design discipline travels even where the traffic profile does not: isolate state early, measure before optimizing, treat a performance budget as a product requirement rather than a cleanup task. What is genuinely new is the operating half, load at millions of concurrent users, cache invalidation at that width, and fleet-scale observability on Grafana and OTEL rather than the dashboards and logs he runs on his own platforms today. He would be learning that here, against real traffic, and he would rather start from that than a claim.
Two decisions on are the cleanest version of this. He shipped the boring surfaces first, profiles and rosters, ahead of the match-analytics views that would have demoed better, because a national hub earns the right to make competitive claims only once it is the canonical answer to who plays for whom. And he made coaching the revenue wedge instead of ads, because ad-funded community sites die the week the community decides it has been monetised against. Both were foundation-first calls with a slower launch as the price. He is a Certified Scrum Product Owner, so the prioritisation discipline is trained rather than improvised.
is the clearest single proof. Agentic due-diligence infrastructure live at wiregent.com: it reads a company's records the way a professional reads a file, cites the evidence behind its verdict and names outright what it could not score, connects agentic payments to a double-entry, hash-chained ledger and a token economy, and issues temporal certifications that prove change and growth over time rather than at one frozen point. He architected it, wrote it, deployed it across Cloudflare Workers and R2, a Fly.io machine holding the event stream and Neon Postgres behind a parity suite, and has kept iterating on it alone since. The first working platform shipped from scaffold in eight days, solo and agent-led. and have the same shape: same person on the architecture, the production code, the deploy, and whatever broke on a Sunday.
Nine years with nobody scoping the week. grew to 22 engineers serving ten client geographies at once, and the calls about which fire actually mattered, which idea waited, and which headcount conversation he had to take himself rather than route elsewhere, were his. The clarity outlived the org chart: two alumni now lead teams in Norway, one took up graduate study in Canada on his recommendation, another moved into UX design in Germany, and an early-career report is now at Amazon in Sweden.
Ask him to build the workspace for Staff / Principal Software Engineer, Product. Here is what ships first, generated the way Lovable generates everything else.
Build the day-one workspace for the Staff / Principal Software Engineer, Product 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.
Ten years of working history since 2015, nine of them co-founding ELO and shipping inside it the whole way, through…
Two decisions on DotaBD are the cleanest version of this. He shipped the boring surfaces first, profiles and rosters,…
Nine years with nobody scoping the week. ELO grew to 22 engineers serving ten client geographies at once, and the…
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.
His largest products are at 15,000+ active users and at 1,207 players and 47,091 matches, real systems with real people on them, and still an order of magnitude short of Lovable's core experience. The architectural habits carry: isolate state early, measure before optimizing, treat a performance budget as a product requirement. What he would be learning here is the operating side, load at millions of concurrent users, cache invalidation at that width, and fleet-scale observability on Grafana and OTEL rather than the dashboards he runs himself.
He has not shipped Rust. The posting asks for React and TypeScript and/or Go and Rust, and he covers three of the four in production today. New backend languages have arrived the same way each time, against a live deadline rather than a tutorial: Go entered his stack that way and now runs and , as did Solidity for an EthGlobal build and Flutter for a client's mobile app.
Stockholm is the move he is planning for, because that is where this team and this product sit. He has not worked in Sweden and will not pretend otherwise. What is real is the region: he hired and led Frontgo's engineering pod in Norway from zero through to Vipps-integrated production, has delivered on CET for years, and his closest friend lives in Oslo. London is the other office on this posting and the place his sister lives, so either address works. He can start remotely while the permit runs.
Every bullet above is a box a competent candidate could tick. These are the reasons to hire this one.
is his restaurant. He wrote the ordering platform, and he also signs for the ingredients, which means every engineering shortcut and every over-build shows up in his own numbers. Lovable exists for people acting on the problems closest to them. He has been that person, with the till receipts to match.
's users are players, 's are diners, 's were music producers. That is why 's matchmaking lives inside Discord where the community already was, and why 's ordering asks for no sign-up and no tracking. Designing for people who will never read your docs is the default setting, not an adjustment he would have to make.
At he built the first web product from a blank canvas, stood up the full-stack team around it on an NX monorepo, and stayed hands-on through the first market release. The team kept shipping after he moved to the relationship side, and Loopcloud acquired the company in 2026. Building something other people can carry is a different skill from building something impressive.
The deploy, the thing that broke on a Sunday, the cost line nobody was watching. , and are all live and all his to operate, so the standard he holds architecture to is the one he has to live with at two in the morning rather than hand to an on-call rota.
The direct answers, including the two things he does not carry into this seat: Rust, and a product that has served millions of users. Ask the agent anything these don't cover.
You cannot know it from my history, so let me be exact about what is there. The largest user base I have built for is at 15,000+ active users; the largest system I run today is at 1,207 players and 47,091 matches. Real products with real people on them, and still an order of magnitude short of yours. What I bring is the discipline underneath those numbers: isolating state early, measuring before optimizing, treating performance as a product requirement rather than a cleanup ticket. Hyperscale load and fleet operations are the part I would be learning here, and I would rather you price that in now than discover it in month three.
Because I have done this ramp under a deadline more than once. Go entered my stack because a client build needed a systems language I did not have, and it now runs 's ordering backend and 's pipeline. Solidity arrived for an EthGlobal build, Flutter for a client's mobile app. None of them slowed delivery, because I learn a language by shipping something in it rather than reading about it. Rust I have not shipped, and adjacent experience does not close that on day one. Point me at a real feature and it closes fast.
I never left the code, so there is nothing to return from. The title I did the best work in was Principal Staff Software Engineer, and while I was CIO I was also shipping 's full stack, building , and putting together solo. What a Staff or Principal seat asks for, architecture judgement plus the clarity to align people around it, is most of what the CIO job actually was, minus the parts that had nothing to do with building. The org chart goes away. The shipping does not.
Both directions, on the same product. On I shipped profiles and rosters before the match-analytics views, which is the slower launch and the less impressive demo, because a national hub has to be the canonical answer to who plays for whom before anyone will trust it to rank them. That is foundation over speed. Then I made coaching the revenue surface rather than ads, quickly, because it aligned the platform's income with what the community actually wanted from it. On the equivalent call is the deterministic model driver: it needs no key, no network and no model, it is the default, and every other driver falls back to it rather than failing a request. That cost me a flashier out-of-the-box demo and bought the guarantee that the product works for anyone who opens it.
By taking the conversations nobody volunteers for and having them directly. Running meant deciding which team's fire mattered this week across ten client geographies, saying no to work we could have taken, and handling headcount myself instead of routing it. The evidence I trust most is what happened to the people afterwards: two alumni now lead teams in Norway, one took up graduate study in Canada on my recommendation, another moved into UX design in Germany, and an early-career report is now at Amazon in Sweden.
Serious, and specific. Stockholm is where this team and this product are, so it is the address I am planning around rather than the one I would negotiate down from. I have not worked in Sweden and I am not going to claim roots there. The Nordics I do know from the inside: I hired and led Frontgo's engineering pod in Norway from nothing through to Vipps-integrated production, and my closest friend is in Oslo, so the region is a place I have worked and visited rather than a map pin. London is the other office on this posting and my sister lives there, so that address works too. I can start remotely while the permit runs, on local hours.
Genuinely ready to work from Stockholm full time, on the CEO's clock.
