mock interview playbook
We're nervous about doing interviews because we don't do them every day. You do your job every day — that's where you feel confident. The familiarity is what builds confidence.
Most PM candidates prepare for interviews the wrong way. They read frameworks, memorize CIRCLES and STAR, watch YouTube walkthroughs, and then walk into an actual interview and freeze. The problem is obvious once you see it: they studied interviews the way you study history — by reading about it. But interviews are a performance skill. You get better at them by doing them, badly, with someone watching you fail and telling you exactly where you fell apart.
I have watched over ten thousand PM interview performances across Pragmatic Leaders cohorts. The single strongest predictor of interview success is not intelligence, not experience, not even product sense. It is the number of mock interviews someone did before the real one. Candidates who did fewer than five mocks had a roughly 20% conversion rate. Candidates who did ten or more were above 60%. Same people, same knowledge — different preparation method.
This page is the playbook for how to run those mocks well. Not just “practice with a friend.” That is step zero. This is the system.
Why most mock interviews are useless
The typical mock interview goes like this: two friends hop on a Zoom call, one asks “Design a product for elderly users,” the other talks for ten minutes, and then they say “that was good, maybe you could have structured it better” and move on.
That mock was worthless. Here is why:
No evaluation criteria. Neither person knows what “good” looks like for that question type. The interviewer is not evaluating against a rubric — they are going on vibes. The candidate gets vague praise and learns nothing.
No time pressure. Real interviews are timed. If you take fifteen minutes on a product sense question that should take ten, you have failed — even if your answer was brilliant. Mocks without a timer build the wrong muscle.
No uncomfortable follow-ups. Real interviewers push back. “Why not option A?” “What data would change your mind?” “Your competitor just launched this — now what?” A friendly mock partner nods along. A real interviewer does not.
No recording. You cannot improve what you cannot observe. Candidates who record their mocks and watch them back improve twice as fast as those who do not. Watching yourself ramble for ninety seconds before reaching your point is deeply uncomfortable and deeply educational.
Finding mock interview partners
This is where Indian PM candidates actually have an advantage — if they use it. The PM community in India is large, concentrated in a few cities, and almost everyone is preparing simultaneously. You are not short on partners. You are short on a system for finding them.
Tier 1: Structured practice groups (highest value)
Form a group of three to five people who are all actively interviewing. Not “thinking about switching.” Actively interviewing — with applications submitted, recruiter calls scheduled, or interview rounds coming up in the next four to eight weeks.
Three to five is the right size. Two people run out of variety. Six or more means scheduling becomes impossible and some people coast.
Where to find them:
- PM communities on Slack and Discord. In India specifically: Pragmatic Leaders alumni, Product Folks, PM School alumni networks. Do not lurk — post that you are looking for a mock interview group with a specific commitment level.
- LinkedIn. Post that you are forming a mock interview pod. Be specific: “Looking for 3-4 PMs with 3-7 YOE who are actively interviewing for senior PM roles. Commitment: two mocks per week for six weeks.” Specificity filters out tourists.
- Your own extended network. Message five former colleagues who are PMs. At least two are probably interviewing right now and will not tell you unless you ask.
Tier 2: Senior PM mentors (for calibration)
Your practice group helps you build reps. But you also need someone who has been on the other side of the table — an interviewer, not just another candidate. One session with a senior PM who hires is worth five sessions with a peer.
Reach out to senior PMs in your network and ask for exactly thirty minutes. Not “can you mentor me.” People ignore that. Say: “I have a PM interview at [Company] in two weeks. Can I do one thirty-minute mock with you and get your honest feedback? I will send you the question type in advance so you can prep.” That request is specific, bounded, and respectful of their time. Most will say yes.
Tier 3: Paid platforms (for volume)
If you need more reps than your group provides, paid mock interview platforms exist. PM Exercise, Pramp, and Exponent all offer mock interviews with other candidates or professional interviewers. The quality varies, but the volume is useful. Treat these as supplementary reps, not your primary practice.
How to structure a mock interview session
A well-run mock takes forty-five minutes. Not thirty — that is too short for real feedback. Not sixty — that leads to rambling debrief conversations that feel productive but are not.
The 45-minute format
Minutes 0-2: Setup. The interviewer states the question type (product sense, estimation, behavioral, strategy) and gives the question. The candidate can ask one clarifying question about the format if needed — not about the question itself. Start the timer.
Minutes 2-12: The answer. Ten minutes for product sense and estimation. Eight minutes for behavioral. Twelve for strategy or case study. The interviewer stays in character. They take notes on a rubric (more on this below). They ask follow-up questions at natural pause points, just like a real interviewer would.
Minutes 12-15: Interviewer follow-ups. The interviewer pushes on the weakest part of the answer. “You said you’d prioritize X — but Y has higher reach. Why X?” This is the part most mocks skip, and it is the part that matters most. Real interviews are won or lost in the follow-ups.
Minutes 15-30: Structured feedback. Not “that was pretty good.” The interviewer walks through the rubric, criterion by criterion.
Minutes 30-45: Role reversal or second question. If you have a partner, switch roles. If you have an observer, they give their written feedback. If you are using recorded solo practice, spend this time reviewing the recording.
The feedback rubric
Use this for every mock, every time. Print it, share it with your group, and grade each criterion on a three-point scale: strong, adequate, needs work.
| Criterion | What “strong” looks like | What “needs work” looks like |
|---|---|---|
| Structure | Visible framework. Clear transitions between sections. Interviewer can follow without effort. | Stream of consciousness. Ideas appear in random order. Hard to track the argument. |
| User focus | Specific user segment defined early. Needs grounded in real behavior, not assumption. | Designing for “everyone.” Assuming user needs without stating who the user is. |
| Depth vs breadth | Goes deep on one solution. Explains trade-offs, metrics, risks. | Lists five ideas at surface level. No commitment to any single approach. |
| Communication | Concise. Signals transitions (“Now let me move to prioritization…”). Finishes within time. | Rambles. No signposting. Goes over time by three or more minutes. |
| Follow-up handling | Engages with pushback. Adjusts position when logic demands it. Holds ground when reasoning is sound. | Folds immediately under any pushback. Or becomes defensive and rigid. |
| India context (if applicable) | References specific Indian market realities: UPI penetration, tier-2 behavior, data costs, language diversity. | Generic global answer that could apply to any country. |
Post-mock debrief. The interviewer is reading from their rubric notes.
Interviewer (Rohan): “Okay, structure was strong. You clearly laid out user, problem, solutions, pick, detail. I could follow everything.”
Interviewer (Rohan): “User focus — adequate. You said 'young professionals in metros' but never got more specific. Who in metros? A 24-year-old in Bangalore making 8 LPA and a 35-year-old in Mumbai making 40 LPA are completely different users.”
Candidate (Priya): “Fair. I was rushing to get to the solution. I should have spent thirty more seconds narrowing the segment.”
Interviewer (Rohan): “Exactly. And the follow-up handling was weak. When I asked 'why not a subscription model,' you said 'yeah that could work too.' That is not a PM answer. A PM answer is: 'Subscription does not work here because this user segment has irregular income and will churn in month two. Here is why transactional pricing fits better.'”
Candidate (Priya): “Got it. I need to have a point of view and defend it.”
This is feedback that changes behavior. Specificity, not praise.
Vague feedback is wasted time. Every criterion gets a rating and a specific example.
The practice schedule that works
I am not going to tell you “practice as much as possible.” That is useless advice. Here is the specific schedule that works, based on what I have seen across thousands of candidates.
The 6-week interview preparation sprint
Weeks 1-2: Foundation (3 mocks per week). Focus on structure only. It does not matter if your ideas are brilliant. What matters is that your answer has a visible skeleton: user, problem, solutions, pick, detail. Record every session. Watch it back the same night.
Product sense questions only in weeks 1-2. This is the most common question type and the one where structure matters most. Do not scatter your practice across five question types. Build one muscle first.
Weeks 3-4: Expansion (4 mocks per week). Add estimation and behavioral questions. One product sense, one estimation, one behavioral, one mixed (interviewer’s choice). Start timing strictly — if you go over, you fail that mock. Period. The follow-up pressure increases. Your mock partner should be actively trying to poke holes.
Weeks 3-4 addition: solo drills. Between mocks, do two solo practice sessions per week. Set a timer, ask yourself a question from a question bank, answer out loud into a recording, and review it. These solo reps are where you build speed. The group mocks are where you build quality.
Weeks 5-6: Simulation (3-4 mocks per week). Full interview simulations. String three questions together — behavioral, then product sense, then estimation — with five-minute breaks between them. This builds the endurance you need for a full interview loop. By week 5, you should feel like mocks are boring. That is the goal. Boring means fluent.
The weekly rhythm
| Day | Activity | Duration |
|---|---|---|
| Monday | Solo drill — product sense question, timed, recorded | 30 min |
| Tuesday | Group mock — you are the candidate | 45 min |
| Wednesday | Review Tuesday’s recording. Write down three things to fix. | 20 min |
| Thursday | Group mock — you are the interviewer (builds evaluation skills) | 45 min |
| Friday | Solo drill — estimation or behavioral, timed, recorded | 30 min |
| Weekend | One simulation round with a different partner. Or rest if you have done four mocks that week. | 60 min |
Total time commitment: roughly five hours per week. That is less than most people spend reading interview prep articles that teach them nothing actionable.
Playing the interviewer: the skill nobody talks about
Here is something counterintuitive: playing the interviewer in mock sessions makes you a better candidate. When you are on the other side of the table, you see patterns you cannot see from inside your own answer.
You notice when someone rambles because you lose attention at the same moment a real interviewer would. You notice when someone skips the “why” and jumps to the “what.” You notice when a follow-up question reveals that the candidate’s solution was surface-level.
When you interview your mock partner, do these things:
Ask the question and shut up. Give them exactly the question with no hints, no softening, no “take your time.” Real interviewers do not warm you up.
Take notes on the rubric while they talk. Do not just listen passively. Grade each criterion in real time. This forces you to listen like an evaluator, which is exactly what you want to internalize.
Push back at least twice. Find the weakest claim in their answer and challenge it. “You said users would pay for this — what evidence do you have?” This is not adversarial. This is what good interviewers do.
Give feedback in the order of the rubric. Structure first, then user focus, then depth, then communication, then follow-up handling. Do not start with “that was great” — start with the first criterion and rate it.
Do this exercise with one partner this week. Not next week. This week.
- Choose roles. One interviewer, one candidate. If you have a third person, they observe and give written feedback.
- Interviewer picks a question. Use one of these if you need a starting point:
- “Design a health insurance comparison product for first-time buyers in India.”
- “How would you improve Google Pay’s bill payment experience?”
- “Estimate the number of auto-rickshaws in Bangalore.”
- Run the 45-minute format described above. Time everything. Record the session.
- Use the rubric. Print it or have it open on screen. Rate every criterion.
- After the debrief, the candidate writes down three specific things to change in their next mock. Not “be more structured” — that is vague. Something like “Spend the first 60 seconds only on clarifying questions before I start my framework.”
- Switch roles and repeat within 48 hours.
The first mock will feel awkward. That is the point. The fifth mock will feel mechanical. That is also the point. By the tenth mock, you will be thinking about the content of your answer, not the process of delivering it — and that is when you start winning real interviews.
Giving feedback that actually changes behavior
Most mock interview feedback is useless because it is either too nice or too vague. “That was pretty good, maybe just structure it a bit more” teaches nothing. The candidate nods, feels okay about themselves, and makes the same mistakes next time.
Good feedback has three properties:
It is specific. Not “your answer lacked structure.” Instead: “You started talking about the solution at the 40-second mark without defining the user. The interviewer had no context for why this solution matters. Next time, spend the first 60 seconds on user and problem before you mention any solution.”
It is behavioral. Not “you seemed nervous.” Instead: “You said ‘um’ fourteen times in eight minutes, and you broke eye contact every time I asked a follow-up. Practice maintaining eye contact during follow-ups — that is where interviewers read confidence.”
It references the rubric. Not “I think you could improve.” Instead: “On the rubric, I rated you ‘needs work’ on follow-up handling. When I pushed back on your prioritization, you abandoned your original answer entirely. A stronger response: acknowledge my point, explain why your original reasoning still holds, or adjust your answer with a specific reason for the change.”
The hardest part of giving feedback in Indian culture is being direct. We are socialized to soften criticism. In mock interviews, softening is sabotage. Your partner is about to walk into a room where a stranger will judge them in thirty minutes. The kindest thing you can do is tell them the truth now, so they do not hear it for the first time from someone who is deciding their career.
You are the interviewer in a mock session. Your partner just answered a product sense question about designing a payment app for street vendors. Their answer was unfocused — they jumped between three user segments, never committed to one solution, and went four minutes over time. They look at you expectantly and say, 'How was that?'
You need to give them feedback. They have a real interview at Razorpay in nine days.
your path
Common mock interview mistakes to avoid
Practicing only with people at your level. If everyone in your group is preparing for the same role, you build fluency but not calibration. You need at least one session with someone more senior who knows what “hire” versus “no-hire” actually looks like.
Skipping question types you are weak at. Candidates who are strong at product sense will practice product sense all day because it feels good. The estimation round they are dreading? They avoid it. Your mock schedule should allocate more time to your weakest area, not your strongest.
Not recording. I will say this again because people skip it: record your mocks. Watch them back. You will discover tics and habits you had no idea existed. The candidate who says “basically” thirty times does not know they say “basically” thirty times until they hear it.
Treating mocks as social time. The debrief should not turn into a forty-minute conversation about career advice, company gossip, or general PM philosophy. Forty-five minutes, rubric feedback, specific actions, done. Save the socializing for after.
Stopping practice once you feel ready. You are never ready. The candidates who perform best in real interviews are the ones who were still doing mocks the night before. Not because they were anxious — because they treat mocks like a warmup, not a remediation. Athletes stretch before every game, not just when they are injured.
You have a PM interview at Flipkart in 10 days. You have done zero mock interviews. A friend who is a PM at a startup offers to do one mock per day for the next 10 days.
The call: Do you do 10 mocks back-to-back, or space them differently and why?
You have a PM interview at Flipkart in 10 days. You have done zero mock interviews. A friend who is a PM at a startup offers to do one mock per day for the next 10 days.
The call: Do you do 10 mocks back-to-back, or space them differently and why?
Where to go next
- Understand all PM interview formats first: PM Interview Types
- Sharpen product sense answers: Product Sense Questions
- Nail the behavioral round: Behavioral and STAR
- Get estimation questions right: Estimation and Guesstimate
- Build the underlying skill that powers every interview answer: Product Thinking