A private, invite-only program
You already do the hardest part of product management. You just do it from the wrong seat.
The judgment you practise every day in testing is the core of product work. This is where it goes to earn what it is worth.
The shift you have already felt
If you work in QA, the ground has moved under you. The pure-execution work, the scripted runs and the regression checklists, is being automated quickly, and the market has started to say so out loud. Testers who only execute are being quietly marked down. Testers who bring judgment are being paid more for it. You are not imagining the shift. You are early to noticing it.
What almost no one connects out loud
The judgment that survives in QA is not a testing skill. Deciding what is worth building. Reading where the risk to a real person actually sits. Choosing what to ship and what to hold. That is product management, and a strong tester already practises a quiet version of it every single day. You have been doing a junior version of the job for years. This is about giving it the title, the seat, and the salary that match.
What this is
The QA Stoic is not open-ended coaching sold by the hour. It is a private, fixed-outcome program with one job: to move you from QA into a product role, deliberately and on your own terms. The outcome is a complete product case for yourself: your positioning, one product artifact you built, and the interview answers that carry both. Twelve weeks.
Who it is for
- You are in QA or testing: manual, automation, SDET, or QA lead.
- You have felt the pull toward the product side of the room.
- You want a deliberate move, not a lottery ticket.
Who it is not for
- You want a generic product course you can buy anywhere.
- You are not in QA or an adjacent role.
- You want someone to do the work for you.
What you walk away holding
- A product-positioned profile and story. Your CV, your LinkedIn, and the way you talk about your own work, rewritten so a hiring manager reads product judgment instead of test execution.
- One real product artifact, built by you. Not a template and not a portfolio exercise. A piece of product work on a domain you already know, taken to the standard expected of someone already in the seat, and defensible when someone pushes on it.
- Interview and stakeholder readiness. The answers to the questions that end most QA-to-product interviews, rehearsed under pressure, and the framing to hold a room once you are in it.
- Direct access to the Coach, who has already guided testers through this exact move.
How it works
- Request an invitation. A short application, not a sales call.
- Profile review. I personally review whether this is the right move for you now. Most of the value is in an honest yes or no.
- Invitation. If it is a fit, you are invited to a discovery conversation.
- The work. A defined path over twelve weeks, built for a constrained schedule.
- The outcome. Your product case, built and yours to keep.
Proof
The QA Stoic began because one tester I guided made the move, and the referrals started arriving on their own.
For years I felt boxed in as "just QA," even though I was the one flagging usability issues before they reached engineering, negotiating trade-offs with product and design, and understanding user pain points better than some of the PMs I worked with. I knew I could do the job. I just didn't know how to prove it.
Pranjal helped me see my QA background as a different lens on the same skills PM hiring managers actually screen for: prioritization, cross-functional influence, and customer empathy. We rebuilt my resume and portfolio around product decisions I had shaped, not just bugs I had caught, and ran mock interviews until product sense questions stopped feeling like guesswork. He pushed me to go after Senior PM roles when I would have settled for an APM title, then coached me through the offer negotiation.
3 months later I signed up for my first official title and role as a Senior Product Manager. I didn't just change my title, rather I changed how I talk about my own experience. If you're in QA wondering whether PM is actually within reach, it is, and Pranjal knows exactly how to get you there. Cannot thank him enough!
The investment
This is a premium program and it is priced as one. The figure is deliberately decoupled from hours, because you are buying an outcome, not a meeting count.
I discuss it directly with you on the discovery conversation, once I know whether this is the right move for you at all. Quoting a number to someone I have not reviewed would be a sales tactic, not an honest answer.
My honest commitment
I do not promise you a job. Anyone who does is selling you something.
What I commit to is a defined outcome you can see and hold: your positioning, your artifact, and your interview readiness, finished to an agreed standard. If you do the work and that outcome is not delivered, we keep going at no further cost until it is. The standard is written down before you start, so neither of us has to argue later about what finished means.
Why invitation only
Places are limited by design. I take a small number of people per cohort because the work is personal and my time is deliberately constrained. The review exists to protect both of us from the wrong fit, because the wrong fit wastes your money and my time.
Request an invitation
If it is not the right move for you now, I will tell you. That honesty is the first thing you are paying for.
For years I felt boxed in as "just QA," even though I was the one flagging usability issues before they reached engineering, negotiating trade-offs with product and design, and understanding user pain points better than some of the PMs I worked with. I knew I could do the job. I just didn't know how to prove it.
Pranjal helped me see my QA background as a different lens on the same skills PM hiring managers actually screen for: prioritization, cross-functional influence, and customer empathy. We rebuilt my resume and portfolio around product decisions I had shaped, not just bugs I had caught, and ran mock interviews until product sense questions stopped feeling like guesswork. He pushed me to go after Senior PM roles when I would have settled for an APM title, then coached me through the offer negotiation.
3 months later I signed up for my first official title and role as a Senior Product Manager. I didn't just change my title, rather I changed how I talk about my own experience. If you're in QA wondering whether PM is actually within reach, it is, and Pranjal knows exactly how to get you there. Cannot thank him enough!
Questions people ask before applying
I only have an hour or two a week. Good. The program is built for constrained schedules, and the outcome is decoupled from live hours by design.
I am “just” a manual tester without a computer science degree. The move is about judgment, not credentials. If you can tell what should ship and why, you have the raw material.
Should I not just learn the AI tools and stay in QA? You can. This is for people who would rather move their judgment somewhere it is valued more than spend the next few years defending shrinking ground.
Why an application instead of a checkout button? Because the wrong fit costs you real money and me real time. The review is how I keep this worth it for the people who are right for it.