About
I follow problems that interest me until they ask me to learn something new.
I did not set out to collect unrelated roles. I kept following problems that interested me, and each one asked me to learn a different part of the work.
The original ask is rarely the real problem. I stay long enough to find the useful version.
What pulls me in
I get drawn to work that is useful, a little ambiguous, and slightly beyond what I already know. When I do not know something yet, I learn what the work actually needs — a tool, a process, a product, or a clearer question — rather than waiting for a familiar shape to appear.
That is why the chapters look different from the outside. A consumer business, analytics leadership, an independent product, and a small automation system are not a collection I planned in advance. They are what happened when I took the next interesting problem seriously.
A business that had to work for customers
Gâteaux d’Amour was the first time that habit had to survive real customers, a small team, and a live range. I co-founded the business in Jaipur and operated it from February 2019 to March 2022 — three years and two months of product, marketing, customer experience, and the day-to-day of keeping the place going.
The documented rule is still the one I trust: we used customer feedback, research, and demand to decide what to add, keep, or cut. We did not grow the catalogue just to look more complete.
What I do professionally today
I am a Lead Data Analyst at Indium Software. My current assignment is multi-region marketplace analytics: helping a reporting portfolio stay owned, checked, and transferable so delivery can continue when people and context move.
I lead the operating design — inventory, ownership, quality checkpoints, handover — and I review judgment. Analysts and partner teams do the underlying reporting and analysis. I am careful not to collapse those two.
Building when the tool does not exist yet
When I need something that is not already there, I try to make a first version. Independently, I am building an AI-assisted rental condition report for tenants and property owners. AI can suggest an observation from a photo. A person has to review it before anything enters the record. The product is still in development. It is not released, and I am not attaching users or revenue to it.
I also started turning my own job search into a system, because it had too many moving parts. The piece that exists today is a listing agent: it collects roles from several sources, filters and organizes them, and keeps a persistent tracker. The wider system is still being documented.
How I work with people
I care about whether the real question is named, whether someone owns the work, and whether a person still needs to decide. Ambiguity is usually sitting underneath the original request. I would rather leave a gap visible than invent a tidy answer.
That applies to teams as much as to products. Guiding analysts, reviewing quality, and coordinating stakeholders is part of the current chapter. So is saying what I did not do: I did not build every report, and team output is not personal output.
What I am in the middle of
I am still in the analytics chapter, and I am still building. I want the next stretch of work to keep both: judgment about complex delivery, and the habit of making something concrete enough to inspect.
If you want to see how that looks in practice, start with the work. If you have an interesting problem or a thoughtful role in mind, I would be glad to hear from you.