My story
An intentional career built on an accidental foundation.
Where it started
I started my career as a Business Data Analyst at a global consulting firm — part of a project for an international client, working on coal demand and supply forecasting in India. My team cleaned, consolidated, and analyzed massive datasets to make data-driven recommendations at the executive level. It was rigorous, methodical, and important work.
That work was valuable — data pipelines and executive reporting are essential for sound decisions, and I'm glad I built that foundation. But after a year, I realized I wanted to be closer to the problem, with more ownership, iteration, and visible impact. A fixed-scope, repetitive role with little challenge wasn't going to give me that — because real learning comes from being challenged.
So I did something that made everyone around me nervous: I quit. Without another job. Without a plan B. Without a safety net.
"I had no idea what came next. What I did know was that staying would cost me more than leaving."
What followed was one of the most clarifying periods of my life. Instead of blasting LinkedIn with applications, I did something quieter — I started having real conversations. With friends. With former colleagues. With people I hadn't spoken to in years. No pitch, no agenda. Just genuine curiosity about what they were building and where they were headed.
One of those conversations changed everything. A friend offered to pass my resume along to his company. A few days later I had an interview scheduled. Three rounds later, I had an offer — for a role I hadn't even heard of six weeks prior.
That company was BillDesk, one of India's largest payment aggregator firms. I joined as a Business Analyst. I had no idea I was about to accidentally become a Product Manager.
The pivot
At BillDesk, things moved fast. Within months of joining, I found myself taking ownership of one of their largest client products — sitting at the intersection of engineering, business, operations, customer service, and client teams. Every stakeholder looked to me for answers. Every ambiguity landed on my desk.
I didn't have a PM playbook. I learned by doing — writing user stories, managing roadmaps, running sprint ceremonies, translating business requirements into technical specs, and doing it all in reverse on the way back. I learned what a PRD was by writing one. I learned stakeholder management by being in the room when it went wrong, and then making it go right.
My title eventually caught up to what I was already doing. Business Analyst became Technical Product Owner. The transition wasn't a career move — it was a recognition of work I was already performing.
A moment I'm proud of
I was asked to present a complex, backend-heavy technical project to a large group of senior and executive business stakeholders — people who had no interest in architecture diagrams. I spent days preparing. I mapped every technical component to a business outcome. I wrote the Dos and Don'ts for myself. I circulated a detailed agenda and reference documents in advance.
The presentation landed. Not just "it went fine" — I received an appreciation email from the Director of Program Management. Colleagues reached out personally. Senior leaders called out my ability to translate technical complexity into business language with clarity and precision.
That moment told me something important: this is what I'm built for. Not just shipping products — creating alignment. Making people believe in what the team is building.
Education
Most people do the degree first. I did the work first — and that made all the difference. I enrolled in my MS knowing exactly what I needed from it. That's a luxury you only get after years in the room.
By the time I started my MS in Project Management at Northeastern, I knew exactly what I was walking in to fill — sharper frameworks around product strategy, business analysis, and stakeholder dynamics that I was already practicing but couldn't yet name with precision. Academic models mapped directly onto real decisions I'd made, real tradeoffs I'd navigated, real systems I'd shipped.
I graduated with a major in Product Management and a minor in Business Analysis. The degree didn't start my career. It compounded it.
What I bring
Everything below was earned on the job — in sprint rooms, stakeholder meetings, and the occasional late-night Slack thread.
User stories, PRDs, BRDs, functional specs — written for engineers who need precision and stakeholders who need clarity.
From C-suite presentations to daily standups — I adapt my language to my audience without losing the substance.
Engineering, business, operations, client teams — I've sat at every table and know how to get them to agree on the same thing.
Payment infrastructure at scale and consumer-facing EdTech — both ends of the product spectrum, different muscles, same craft.
My roots are in data. I ask "what does the data say?" before forming opinions, and I know how to turn numbers into narratives.
I use AI tools daily to write faster, think sharper, and build things I couldn't before. This website is proof of that.
I'm actively exploring PM opportunities at Big Tech companies. If you're hiring or just want to connect, I'd love to hear from you.