b1d9f4
Built the same way as everything it lists: a design doc, a dependency-ordered plan, one commit per verified task. The site is not a writeup about the pivot, it is the pivot, running in public.
I like building things people actually use.
Three years shipping data systems in production, now all in on software engineering.
Proof, not promises, one commit at a time.
Currently building Mnemo
A dated feed of what I ship — commits, writes, and milestones — click each item to know more.
184 contributions in the last year
Selected builds — filter by tag, click to expand.
Peer-reviewed papers — click to expand for the abstract.
Roles and internships — click to expand for detail.
Notes on building in public — Substack and LinkedIn.
Substack ·
LinkedIn ·
Follow along on Substack (opens in a new tab)

I spent three years working with data across Kohler, Apna, and Google, building pipelines, automation, and systems that teams relied on every day. Somewhere along the way I realized the parts I loved most were the software parts: designing APIs, shipping products, watching people use what I built. So I'm going all in on software engineering.
I don't have years of a traditional SWE / SDE / Product Engineer title behind me, but I have production experience, I learn fast, and I'm building the proof in the open: every project public, every milestone logged, every lesson written up. If you want to see how I work, it's all here.
Education
University of Illinois Urbana-Champaign
2024–2026
M.S. in Information Management
Manipal University Jaipur
2018–2022
B.Tech in Computer and Communication Engineering