Product Manager interview questions (India, 2026): what to ask and what to listen for

12 interview questions for a Product Manager role, grouped by what each round should establish, each with what a strong answer contains, plus a five-point scorecard so every interviewer rates the same things.

Last updated 3 September 2026. Competitor pricing and plan limits are re-verified against each vendor’s own pages.

Interviewing a Product Manager well means asking about work the candidate has actually done, listening for specifics, and scoring every candidate on the same five criteria. The questions below are grouped by what they establish; each one comes with what a good answer contains, which is the part most question lists leave out.

A Product Manager in an Indian startup decides what the engineering team builds next and why — talking to customers, writing specs the team can build from, prioritising against the company's goals, and owning the outcome — usually as the first person between the founder and the engineers.

Use the screening questions on the job description page to filter before anyone reaches an interview, and the scorecard at the end so a panel can compare candidates rather than impressions.

What they have shipped and decided

Tell me about a feature you shipped that moved a metric. What was the problem, how did you decide it was the priority, what did you cut, and what happened?: A strong answer: A real outcome with a number, a prioritisation reason, and something cut — PMs who never cut anything have never owned a deadline.
Tell me about something you killed or refused to build, and how you handled the person who wanted it.: A strong answer: Judgement, a reason grounded in users or strategy, and a respectful no. Saying no is most of the job.
Describe a customer conversation that changed a decision.: A strong answer: Regular customer contact and evidence that it matters — a specific conversation and a specific change.
Show me a spec you wrote. Where did engineers come back with questions, and what did you change in how you write?: A strong answer: Clear structure with edge cases and acceptance criteria, and a learning loop about ambiguity.

Product thinking

Here is a real problem from our product [describe one]. How would you approach it in the next two weeks?: A strong answer: Asks about users and data before proposing, frames the problem, proposes the smallest thing that tests the hypothesis, and defines success.
Two customers want opposite things and both are valuable. How do you decide?: A strong answer: Returns to the strategy and the broader user base, looks for the underlying need, and makes a call with a reason rather than splitting the difference.
How do you decide what to measure for a release, and what have you measured that turned out to be the wrong metric?: A strong answer: Leading and lagging metrics, guardrails, and a story about a vanity metric they stopped using.
What would you cut from our product today, and why?: A strong answer: Preparation, an opinion with a user-grounded reason, and comfort proposing removal.

Working with the founder and the team

The founder wants to build something you think is wrong. What do you do?: A strong answer: Makes the case with evidence, proposes a cheaper test, and commits fully if overruled — while documenting the disagreement. Neither a yes-person nor a blocker.
An engineer says the spec will take three weeks and you have one. What happens next?: A strong answer: Understands why, cuts scope to the core, and does not push the engineer to just work harder.
How much of your week was writing, talking to customers, in meetings, and testing builds? What should it be here?: A strong answer: Realism about a hands-on first-PM role and a deliberate allocation.
Why product, and why a company at our stage?: A strong answer: A genuine reason for wanting breadth, the founder relationship and the ambiguity of an early role.

Scorecard for Product Manager interviews

Score each candidate on these five criteria, one to four, straight after the interview and before talking to the other interviewers. Written scores taken independently are what make a panel decision defensible; a discussion first produces one opinion with several signatures.

Outcomes: shipped things that moved metrics; cut and killed things with reasons.
Customer grounding: regular conversations that changed decisions.
Spec quality: clear, complete, with a learning loop on ambiguity.
Product judgement: frames problems, tests hypotheses cheaply, picks the right metric.
Founder and team relationship: makes the case, commits, cuts scope, stays hands-on.

Screen before you interview

Most Product Manager interviews that go badly were avoidable at the application stage. The job description template for this role carries five screening questions that settle the deal-breakers — notice period, location, the one or two hard requirements — before anyone books a slot.

Have you owned product decisions and their outcomes — roadmap, specs, metrics — for at least 2 years? — knockout
How many years of product management experience do you have? — for context
Are you able to work [from our City office X days a week / hybrid]? — knockout
What is your current notice period, in days? — for context

Questions, answered straight

What is the best Product Manager interview question?

Ask about something they killed or refused to build and how they handled the person who wanted it. Saying no with a grounded reason is most of the job, and PMs who have never done it have never owned a roadmap.

Should a PM interview include a case?

Yes, using a real problem from your product rather than a hypothetical: how would you approach it in the next two weeks. Watch for whether they ask about users and data before proposing, and whether they define success.

How do I assess a PM's relationship with a founder?

Give them the scenario of a founder who wants to build something they think is wrong. The answer you want makes the case with evidence, proposes a cheaper test, and commits fully if overruled — neither a yes-person nor a blocker.