About
Systemsthat admitdoubt.
I am a frontend engineer based in Kolkata, currently building product at Fleapo. Before this I worked at Actalyst and started out at MountBlue Technologies — three years of shipping interfaces for software that people depend on to do their jobs, including apps serving millions of users.
What I add to that is the two halves either side of it. I design the product before I build it, and I build the agentic systems behind it — the retrieval and the reasoning, not just the screen in front of them. Most frontend engineers treat the model as a black box and hand the design off to someone else; doing all three is the difference between an interface that displays an answer and one that can be trusted.
It matters because AI products fail at the seams, not in the model. A model that is right 90% of the time is a research result; a product that is right 90% of the time is a liability, unless somebody decided what the other 10% looks like — whether it refuses, what it shows instead, whether a person is asked, and how the user knows which case they are in. That is a UX decision and an engineering decision at once, and it does not survive a handoff.
So the thing I care about most is how software behaves when it isn't sure. I have built vector retrieval where the questions are genuinely open, and deliberately refused embeddings where every claim had to trace back to a confirmed fact. I placed first in the UI/UX Grand Prix against 200 designers, and I run discovery, competitor analysis, personas and information architecture before opening a code editor, then build the design system the interface is made of. None of this is a claim to take on faith — it is the work.