The most interesting problems sit at the boundary between what engineers are building, what product managers are prioritizing, and what founders need to decide. That boundary is where this career has been heading.

Starting as a software engineer, the shift happened at Krutrim, where working closely with the founder and Chief of Staff opened up a different kind of work: understanding what the data actually meant, talking to customers to find out what was driving adoption, and then building the alignment across senior leaders needed to act on it. The hardest part was rarely the analysis. It was figuring out who needed to believe what, in what order, and how to bring them there without making anyone look bad.

The operating instinct that runs through this work is a preference for building from the bottom up. Going to the engineers and analysts first, understanding their reality, and then translating that upward into something executives can act on. That approach surfaced the insight that shifted Krutrim's investor pitch strategy, and it also resolved a three-week standoff between a locked engineering roadmap and a better product direction.

The next step is a role where that instinct can operate at full scale, working directly with a founding team on the problems that matter most.