I came to product through systems engineering — understanding how systems fail taught me how products succeed.

Tharun Kumar S
IIM Calcutta · MBA 2025
Hyderabad, India · Open to PM roles
My path to product management started with three years as a Systems Engineer at Infosys, writing JavaScript and Python automation for enterprise client workflows. I wasn't a PM then, but the questions that stuck with me were PM questions. What breaks first? Who owns it when it does? Most of what I learned came from watching small missed edge cases turn into expensive problems for the client months later.
At IIM Calcutta I headed the Internet Solutions Group, a 12-person team running IT infrastructure for 5,000+ campus users. The MBA gave me P&L frameworks and strategy vocabulary, but the ISG was the real education. We migrated five legacy applications from AWS to Azure without service disruption. I also built an internal ticketing system in Python after watching cross-functional requests fall through the cracks, and resolved over 100 issues that had no playbook.
Simpl put that instinct to work on consumer credit. For the SPaD product I ran 100+ user interviews across four delinquency cohorts. The number that mattered never showed up in a dashboard: 49% of new-user failures came from confusion about what the product even was, not intent to default. You only hear that in conversation. The finding made it into a go-to-market P&L decision and reshuffled what the team prioritised on the roadmap.
I'm based in Bangalore and open to PM, APM, and product-adjacent roles in fintech, payments, lending, and AI.
Systems
Three years as a Systems Engineer at Infosys before the MBA. Shipped automation scripts in JS and Python. Built internal tooling at IIM Calcutta.
Research
100+ interviews at Simpl across four delinquency cohorts. Research that shaped the SPaD roadmap and informed a go-to-market decision.
Business
Research that informed a go-to-market P&L decision on the SPaD product line.