About me
I grew up in Mumbai. Cricket in the lanes, football whenever there was space, and a strong pull towards anything that involved numbers. For most of my early years I assumed I'd end up in mechanical engineering — that felt like the natural destination for someone who liked math and wanted to build things.
Then in class 11, I encountered C++ for the first time. That was it. Something about writing code — the logic of it, the fact that you could describe a system precisely and watch it behave exactly as you described — felt more immediate than anything I'd come across before. I kept going. The more I wrote, the more I wanted to write.
I studied Information Technology at the University of Mumbai, then moved to the US to finish my degree at Penn State, graduating in 2025. Somewhere along the way, coding stopped being the whole answer. I realized I was just as interested in the decisions that happened before anyone wrote a line of code — what to build, for whom, and why. That question has been sitting with me ever since.
Right now I work in data and integrations, building the plumbing that connects systems together. I also think and write about products, places, health, and whatever else I can't get out of my head. This site is where that thinking lives.
Education
Work
I work across data, integrations, and product execution — somewhere between engineering and the business. Day to day that means building Python pipelines, connecting systems via APIs, defining KPIs with finance and leadership, and sitting in the middle of conversations between customers, operations, and internal teams. It's taught me a lot about how decisions actually get made inside a company, which is different from how they look on paper.
Built microservices with Spring Boot and PostgreSQL, worked on authentication, performance optimization, and CI/CD pipelines. Short stint but I wrote a lot of code and learned what good backend architecture actually feels like in practice.
Built integrations, automated workflows, and created dashboards that people actually used. First time I realized that the most valuable thing wasn't the code itself — it was understanding what the business needed well enough to build the right thing.
Download resume ↓