QA to PM Without Quitting: Ganesh’s Internal Switch Story 

Who Is Ganesh Basankar? 

Ganesh is a product manager at Motilal Oswal, one of India’s largest financial services firms. He has spent roughly 5.5 years in a single field, the capital markets domain, and reached PM without an MBA or any product degree or certification when he started. 

He has a BSc in computer science, which has easily gotten him into IT. His first job was as a junior software tester at a broking firm, where he stayed for about two years. He then moved to another company as a QA engineer. About a year in, he made the switch that defines this story: he moved from QA to product management inside the same organization, without leaving. He was a PM there for around 2.5 years before moving to Motilal Oswal. 

Most transition stories start with someone quitting and betting on themselves. Ganesh doesn’t. He never left a job to “find out” if he wanted product. He found out first, on the company’s clock, and kept his salary the whole time. 

Why QA Engineers Make Unusually Good Product Managers 

QA engineers already do the hardest part of the PM job: they think about why a product exists, not just whether it works. Ganesh was, by his own description, an exceptional QA, good at finding bugs and suggesting improvements. But what actually moved him toward product was a different habit. 

As a QA, he kept asking the question testing doesn’t require: not just how does this feature work, but why does this feature exist, why does the user need it, and why does the business need it. That instinct is product thinking. His seniors noticed it before he had any title for it

This is the through-line of his whole story, so it is worth stating plainly. The PM mindset is not granted by a job title. It is a habit you start before anyone gives you permission. Ganesh built it by interrogating his own product, and later by interrogating products he simply used as a customer. 

There was also a ceiling he saw coming long before he hit it. The QA track had a fixed shape, and he didn’t like where it pointed. 

That is worth sitting with if you’re in QA now. The pull toward product often isn’t about hating testing. It’s about seeing the next few rungs of your current ladder and realizing none of them is the job you actually want. 

If you are in QA right now and want to start today, pick one feature in your current sprint and write down why it was built, who needs it, and what you would have decided differently. That is product thinking. You can begin without changing anything about your title. For a structured version of this path, HelloPM’s full QA to PM roadmap walks through the seven steps in order. 

How to Transition From QA to PM Internally, Without Quitting Your Job?

The move that worked for Ganesh was a low-risk internal pitch, not a resignation. He went to the head of product directly and asked for a chance, framing it around the QA work that had already impressed them. The answer wasn’t an immediate yes. It was a trial. 

His head of product offered a split: 60% QA, 40% PM, for a three-month period. Then he handed Ganesh a big module to own, specifically to test whether he could work independently. The result is the most citable thing in this story. 

In that single trial module, Ganesh ran the full product cycle for the first time: discovery, research, ideation, validation, user interviews, multi-stage environments, and go-to-market. He didn’t know the terminology going in. He learned the concepts by doing the work. After three months, his head of product moved him to a 100% PM role. 

One honest part Ganesh doesn’t skip: even after the internal move, people outside his team questioned his skills because he held no product degree or certification. He didn’t argue. He took it as feedback, recognized that he had skipped over fundamentals in three fast months, and decided to fix the gap before it followed him for years. That decision is what led him to enroll in HelloPM’s product management program while already working as a PM. 

He picked the program the same way he’d evaluate a product. He ran competitor analysis on the options, went through their sites, got on calls, and listed the pros and cons before committing. What sold him was mentors who didn’t take students for granted and a depth that still challenged someone who was already a working PM. After that, the outside questioning stopped: he had the hands-on experience, the fundamentals, and the certification to back it all. 

Why He Switched Internally Before Changing Companies? 

Ganesh chose the internal route on purpose because it removed every variable except the one that actually mattered: could he do product work? Moving to a new company to become a PM would have meant joining a new team, learning new processes, and proving himself from scratch, all on top of learning the craft itself. 

By staying, he worked with people who already trusted him and knew his capabilities. He didn’t have to re-earn credibility while also learning what a PRD was. As he puts it, if an organization is willing to transition you internally, they have already seen something in you and will back you for at least 3 to 6 months to prove it out. 

He is also honest that the internal path “favored” him, and that is exactly why he later pushed himself to switch companies. He wanted to know whether he could be a PM somewhere that hadn’t watched him grow up. That is the search that gets real in the next section. 

Breaking Into PM in Capital Markets Without a Finance Degree 

Ganesh’s edge wasn’t a finance degree; it was years of domain knowledge built inside one industry. He has spent his entire career, around 5.5 years, in the capital markets domain: broking, trade applications, and mutual funds. When he moved to Motilal Oswal, he deliberately stayed inside that same domain. 

For the LinkedIn outreach that drove his external search, he split his targeting. The people he messaged for referrals were almost all from the same capital markets domain, because domain familiarity is what gets a fintech hiring manager to take a referral seriously. The broader cold-email net was domain-agnostic; he was open to any PM role, any city. 

Why this matters for fintech PM roles: 

In a regulated, jargon-heavy field like capital markets, knowing how trades, brokerage, and mutual funds actually work is an edge a generalist PM does not have. Ganesh didn’t compete on PM Polish alone. He competed on PM thinking, plus a domain that most candidates can’t speak fluently. For a broader view of this field, check HelloPM’s guide to fintech product management in India.

What the External Job Hunt Actually Took: 500+ Applications for One Offer?

The external search was brutal, and Ganesh is specific about the numbers, which is what makes them useful. Landing his Motilal Oswal offer took a funnel most people never see laid out honestly. 

The channel breakdown matters as much as the totals. Very few of his interviews came from cold emails, maybe one or two. Almost all of his interview calls came from LinkedIn: not the easy-apply button, but the company’s own job portal reached through LinkedIn, combined with directly messaging people for referrals. His own rule of thumb for outreach, offered as advice rather than logged data, is that roughly five or six out of ten people will reply to a genuine referral request.

His tactic when a job showed 100-plus applicants within minutes: don’t give up on it. Search for the same role on LinkedIn, find three or four people on that team, send your CV, and ask for a referral. That is how he got traction on the Motilal Oswal role itself. 

Across roughly two months, he describes the hardest part not as the rejection itself but as the silence: doing assignments, clearing rounds, and getting no feedback at all. His answer was to keep the pipeline running. Never pause your applications to wait for one company’s reply. 

Inside the Motilal Oswal PM Interview 

The Motilal Oswal process included a take-home assignment, followed by two distinct interview rounds. Ganesh treated the assignment as the place to win, and it became the bonus that set him apart from other candidates. 

The assignment was a deliberately vague prompt: how can a product manager tackle the emotional aspect of a trader? Instead of jumping to a solution, he broke the vague statement into smaller pieces, identified the real problem, and validated whether it was a real problem at all. He researched it, brainstormed solutions with ChatGPT because he had no one to brainstorm with, built assumptions, ran a user interview within his own organization, and built a prototype. The interviewer was, in Ganesh’s words, “damn impressed.” 

Two preparation tactics did the heavy lifting. First, the HelloPM mock interviews: he did two rounds with a HelloPM mentor, and walked in feeling like he already had a question bank. Second, a ChatGPT prompt he recommends to anyone: tell it the role and who is interviewing you, and ask it to generate the questions that the interviewer is likely to ask. He used it to surface both the behavioral and the strategic questions before they came up live. 

The Part Nobody Warns You About in PM Job Search

The hardest part of the external search wasn’t the rejection. It was the silence. Two months of assignments, interview rounds, and final stages, with almost no feedback on most of them. That isn’t a logistics problem. It’s a psychological one, and it’s the part that makes people quit.

His response to the silence was the opposite of what most people do. He didn’t slow down and wait for one company’s reply. He kept the pipeline full and refused to spend the two months sitting in a hole, hoping for a callback. 

The same resolve had shown up earlier, when the internal PM role got hard, and the safety of QA started to look appealing again. He came close to retreating and talked himself out of it. 

If you’re a senior person making this switch, this is the cost that doesn’t show up in any funnel diagram. The bet feels bigger because you have more to lose. Ganesh’s framing is worth borrowing: name the worst realistic outcome out loud. Usually, it’s “I keep looking for another job,” not a catastrophe. That’s a survivable downside. 

Ganesh’s Three Rules for Any Non-PM Trying to Switch

When asked what he’d tell a QA or any non-PM eyeing a product role, Ganesh gives three rules, each tied to something he actually did. 

1. Act as a PM before you have the tag 

This is his core principle, and he repeats it for a reason. Don’t wait for the course, the resume, or the offer to start thinking like a PM. Question the products you already use every day. Why does Spotify run a subscription model? What are its pros and cons? Spend five to ten minutes a day interrogating a random product, even an air conditioner. That is how product sense gets built.

2. Don’t wait for the perfect moment; run everything in parallel 

Prepare and apply simultaneously. Don’t treat it like a stack where you finish learning before you start applying. The interview itself is the best practice you will get, and the rejections are the curriculum. Keep the processes running simultaneously. 

3. Write everything down 

Product observations, notes after every interview, and doubts to ask seniors. Writing forces your brain to question things in a structured way, and structured thinking is most of the PM job. He credits frameworks like Jobs To Be Done and The Mom Test for giving that thinking a shape during his three-month trial. 

And a bonus rule, the one this whole story rests on: if you can transition inside your current company, do that first. It removes the cost of starting over with strangers and lets you focus entirely on the craft. 

Frequently Asked Questions 

1. Can you become a product manager internally without changing companies? 
   Yes. The lowest-risk path is to pitch your manager for a trial split between your current role and product work. Ganesh negotiated a three-month, 60% QA and 40% PM arrangement, owned one module to prove himself, and then moved to a full-time PM role at the same company. You keep your salary and your credibility while you learn the craft. 
2. How many job applications does it take to land a PM role? 
   It varies, but it is usually a large funnel. For Ganesh’s external move, it took more than 500 applications and over 100 cold emails to generate 10 interview calls, 2 final rounds, and 1 offer, over roughly two months. The point is not the exact number. It is that volume and persistence, not a single perfect application, that produce an offer. 

3. Are cold emails or LinkedIn better for getting PM interviews?
   For Ganesh, LinkedIn clearly won. Only one or two of his interviews came from cold emails. Almost all came from applying through the company’s job portal via LinkedIn and from messaging team members directly for referrals. When a role already has 100+ applicants, find three or four people on that team, share your CV, and ask for a referral instead of relying on the apply button. 

4. Do you need a finance degree to become a fintech or capital markets PM? 
   No. Ganesh became a PM at a major capital markets firm with a BSc in computer science and no finance degree. What carried him was years of domain knowledge in brokering, trade applications, and mutual funds. In regulated, jargon-heavy fields, deep domain familiarity is often more valuable than a formal finance qualification. 

5. Do you need a product management certification to be taken seriously as a PM? 
   It isn’t mandatory, but it can close a credibility gap. Ganesh transitioned without one and still faced people questioning his skills because he had no product qualification. He used a structured PM program to cover the fundamentals he had skipped, which removed those doubts. Hands-on proof matters most; a credential can reinforce it. 

6. How do you prepare for a product manager interview with limited time?
   Run mock interviews and use AI to predict questions. Ganesh did two mock interviews with a mentor and reviewed notes from 10+ past interviews. He also prompted ChatGPT with the role and interviewer details to generate likely questions. Always have a strong, specific “tell me about yourself” script ready, since it sets the first impression. 

7. Should you change industries when moving into product management? Not necessarily. Staying in a domain you already know reduces how much you have to prove at once. Ganesh stayed inside the capital markets across his entire transition, which let his domain expertise do part of the selling. If you do switch domains, expect to rebuild credibility on top of learning the PM role itself. 

.