I started by drawing screens and ended up responsible for what happens when a stranger in an emergency room needs a drug allergy from a discharge summary issued four years ago. Nobody plans that route. I can at least explain it.
Every step was the same move: I refused to stay on my side of the handoff, and the scope of problem I was willing to own got wider. Screens, then the data behind them, then the product, then the systems underneath it, then the whole thing. Building my own was not a leap — it was the next size of the same habit.
In short
- Now
- Founder of Vaulth AI since April 2026, and its only engineer — backend, web, mobile, infrastructure, AI, security and compliance, alongside product and UX.
- Route
- Six roles since 2020: UI/UX developer, intern, developer, designer, product manager, founder. Design first, then data, then product, then systems. Not a ladder — a direction, and the record below has the sideways steps in it.
- Good at
- Deciding what not to build, and saying what a decision cost. Two features killed in a prior multi-product role against criteria agreed before the test.
- Evidence
- Ten case studies, each with its trade-offs and its limits stated. The build page is the argument; this page is the record behind it.
IWhy I build
Because I came to engineering through design, which shows. I still think a product is mostly a claim about how someone will feel at 11pm when something has gone wrong. Everything else is implementation detail, including the implementation — which is now the part I write.
Because I'd rather kill a feature than defend one. Two features died at String Metaverse against criteria we'd agreed before the test. That is the part of product work I'm actually good at, and it took me a long time to admit it's more useful than the drawing.
Because I'm hard to categorise and I stopped minding. Engineers assume I came from a technical background. Designers think I'm too technical. Developers occasionally think I spend too much time on users. For a while I tried to pick one. Then I noticed that products don't care about organisational boundaries and users care even less.
Because systems inherit the boundaries of the teams that make them. Siloed teams ship siloed features, and the seams turn into friction the user can feel. That is why I look at the operating model as well as the interface when a product does not cohere.
Because I've stopped trying to architect the cathedral on day one. Complex systems that work turn out to have grown from simple systems that worked; complex systems designed whole from scratch mostly don't. So I look for the smallest version that genuinely works and the path along which it can grow. It is a less impressive first diagram and a considerably better second year.
Outside the work, I typeset fiction and make videos about design, product, and whatever I have just changed my mind about. Both are deliberately kept as curiosities, not credentials.
IIWhat I'm not yet good at
I have never managed anyone. What I know about teams is knowledge of working with one, not of running one, and a first hire will discover that before I do.
The backend and infrastructure depth is recent and deliberate. There are four years of design and product judgment behind me and about eighteen months of building production systems alone; the gap between those two numbers is the honest shape of the risk.
The independent products are build evidence, not yet adoption evidence. Distribution is the part of this I understand least well, which is why it is the work in front of me rather than a capability I claim.
IIIThe record
Roles, in order, most recent first
Founder & CTO, Vaulth AI
Health records custody and consent, built India-first. Sole engineer across backend, web, mobile, AI, infrastructure, security and compliance, alongside product and UX.
Product Manager, multi-product platform
Eleven products across fintech, Web3, gaming, payments and AI, in an ecosystem that grew from roughly one million users to more than four and a half million. Promoted into a role that did not exist before I was given it.
UI/UX Designer, multi-product platform
Behavioural research across all eleven products, building the opportunity backlog that became the first six months of roadmap.
UI/UX Developer, iAuto Analytics
Remote, Atlanta. Funnel analysis, A/B testing and the design system for an automotive sales platform. Where I learned to read data instead of assuming.
UX Developer Intern, Pluxbox B.V
Hilversum, Netherlands. A no-code SaaS platform, and thirty interviews that removed a third of its setup flow.
UI/UX Developer, iAuto Analytics
The first one. A web application, analytics instrumentation, and the beginning of the habit of checking.
IVEducation
M.Sc, Human Computer Interaction & Design
EIT Digital Master School — Polytechnic University of Madrid & University of Twente
B.Tech, Computer Science and Engineering
Shiv Nadar University
Six roles, one direction. The only thing I've done consistently is refuse to stay on my side of the handoff.