I started by drawing screens and ended up thinking about what happens when a stranger in an emergency room needs to piece together a medical history scattered across documents from four years ago. Nobody plans that route. I can at least explain it.
I kept getting curious about whatever happened after my part was supposed to end. Screens led to analytics, analytics led to product decisions, and product decisions led to the systems underneath. Starting my own company felt less like a leap than the next version of that 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. The path was not tidy, but each role gave me a wider part of the product to own.
- 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.
- Work
- Ten case studies with the trade-offs, results, and limits included. The build page is the quickest way to see them.
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 stop a weak feature than keep defending it. In a previous role, two features missed criteria we had agreed before testing, so we stopped them. It took me a while to realise that saying “this isn’t working” can be more useful than another round of polish.
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’ve worked closely with teams, but I haven’t managed one yet. Hiring and supporting a first team will be a new part of the job for me.
My backend and infrastructure experience is newer than my design and product experience. I’ve spent about eighteen months building production systems alone, compared with four years closer to the user and interface. I’m proud of the progress, but I don’t pretend the two are equal yet.
The independent products prove that I can build; they do not yet prove that I can distribute. Finding users and earning adoption is the part I understand least well, so it is where I need to spend more time now.
IIIHow I got here
The titles tell only part of it. The questions I was asking changed much more.
Pixels
Figma, user flows, design systems, and the negotiation between beauty and the frontend.
How should this screen work?The whole machine
I stopped treating the handoff as the edge of my job — instrumentation, funnels, the data behind the interface, and enough of the system to argue with the people building it. The backend and infrastructure depth came later, and deliberately.
How does this entire product work?Product
A multi-product portfolio. Retention curves, onboarding funnels, pricing, roadmaps. I stopped optimising components and started optimising outcomes.
Why should this exist?Systems
Depth again, at a different altitude: shared platforms under many products, failure direction chosen per surface, and infrastructure cost treated as a design constraint rather than a bill.
What breaks at scale — and what survives it?Owning the whole thing
Product, architecture and code on one surface, with nobody to hand any of it to. The backend and infrastructure depth is recent and deliberate — it is what this rung cost.
What is worth building, and who does it answer to?IVThe 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. The mobile apps are submitted to the App Store and Google Play; a Knowledge Library and Vaulth for Doctors and Hospitals are in active development.
Product Manager, multi-product platform
Worked across eleven products in fintech, Web3, gaming, payments and AI. I started in design and was promoted into a product-management role that had not existed before.
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.
VEducation
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
The roles changed. The habit didn’t: I kept following the problem further than my title required.