About me

I build systems and try to understand how they hold up.

My work sits across product, AI, and system design. I care less about how something performs in a demo and more about what happens after it ships. Once real users interact with a product, the gaps in thinking become visible.

Earlier, I used to build every product for finesse. I was working in larger organisations where polish, process, and structure were expected.

That changed when I joined an early-stage startup.

In that environment, speed was survival. Decisions had to be made with incomplete information. Trade-offs were immediate and visible.

Over time, I realised the real question is not speed versus architecture. It is timing.

Every product sits at a different stage. Some moments demand velocity, even if the structure is imperfect. Other moments demand restraint, even if that slows momentum. The discipline is understanding the product, the customer, and the company’s ambition before deciding what to optimise for.

I have worked across enterprise and AI-driven products in environments where edge cases, compliance, and operational reliability matter.

Across roles, the throughline has been consistent. Understand the system. Respect constraints. Design with production in mind.

I am still learning how to do that better.