Product Management (Experienced) Interview

Experienced business hiring in India usually runs a recruiter or HR screen on background, reason for change and compensation; a hiring-manager round that goes deep on one or two things you personally owned, with the numbers, the misses and what you changed; a role round led by a senior practitioner, which for sales is a deal or territory review and often a mock pitch, for product a case or a product-sense and metrics discussion, and for operations and supply chain a planning or costing scenario; and a behavioural or leadership round, sometimes with a skip-level or business head. Loops take two to four weeks and often include an assignment such as a territory plan, a product teardown or an S&OP case. ExamPilot compresses this into one 17-minute panel: an HR screen, a hiring-manager round on your real targets and launches, a role-specific technical round where quota math, distributor margins, funnel metrics and inventory turns must be right, a STAR behavioural round and a closing on expectations. Each round is scored on role knowledge, problem solving, communication and attitude, with feedback that names the number you fudged or the trade-off you missed.

1. 1

   Launch ownership

   Walk me through one product you launched end to end: what problem it solved, which metric moved, and what you cut to ship it.

   What a strong answer covers

   Describe the user problem with evidence, the solution and its alternatives, the launch plan, the before and after metric with numbers, and what was cut and why. Separate your decisions from the team's. Avoid a feature list with no outcome or claiming credit for the whole roadmap.

2. 2

   Metrics

   Define a north-star metric for a UPI-based bill-payments product, and the guardrail metrics you would watch alongside it.

   What a strong answer covers

   Propose a north star like monthly active payers completing successful bill payments, explain why it reflects user value, and add guardrails such as payment failure rate, refund time and support tickets. Discuss how input metrics drive the north star. Avoid choosing downloads or GMV alone without explaining the trade-offs.

3. 3

   Retention analysis

   Day-seven retention for new users dropped from forty to thirty-two percent after a release. How do you investigate?

   What a strong answer covers

   Confirm data accuracy, compare cohorts before and after the release, segment by platform, acquisition channel and geography, review funnel changes and qualitative feedback, then rank hypotheses and test fixes. Avoid assuming the release is guilty without checking other changes such as marketing mix.

4. 4

   Saying no

   Sales promises a large client a custom feature in six weeks without asking you. How do you handle it?

   What a strong answer covers

   Understand the client need and revenue impact, assess against the roadmap with RICE or cost of delay, propose options such as a configurable solution or a later date, and agree with sales leadership. Communicate the decision clearly. Avoid either blindly agreeing or refusing without evaluating the opportunity.

5. 5

   Requirements

   What makes a requirements document good enough that engineers can build from it without you in the room?

   What a strong answer covers

   A clear problem statement, user stories with acceptance criteria, edge cases and error states, non-functional requirements, analytics events, dependencies and out-of-scope items. Mention reviewing it with engineering and design early. Avoid writing solution-only specs or leaving ambiguity for engineers to guess.

6. 6

   Build vs buy

   For a technical PM role: would you build your own notification service or buy one, for an app sending fifty million messages a day?

   What a strong answer covers

   Compare cost at scale, reliability, latency, vendor lock-in, data residency and compliance, team capacity and time to market. Propose a decision with a reason and an exit plan. Avoid choosing by gut or ignoring operational costs of building in-house.

7. 7

   Backlog management

   As a product owner in an agile team, how do you decide what goes into the next sprint when the backlog has eighty items?

   What a strong answer covers

   Refine and prioritise based on goals, value and dependencies, keep the top items ready with acceptance criteria, agree sprint goals with the team, and balance new features with tech debt and bugs. Avoid letting stakeholders bypass the backlog or overloading sprints.

8. 8

   Failed launch

   Describe a launch that failed. What did you learn, and what would you do differently?

   What a strong answer covers

   A STAR answer: the hypothesis, what was built, the result versus target, how you discovered the failure, what you did next such as iterate or roll back, and a specific change in your process. Avoid a story where the failure was entirely someone else's fault.

9. 9

   Engineering conflict

   Your engineering lead strongly disagrees with your priority call. How did you handle such a situation in the past?

   What a strong answer covers

   A STAR story: the disagreement, how you understood their concerns, the data or compromise used, the decision and the working relationship afterwards. Show respect for engineering input. Avoid pulling rank or escalating without discussion.

• English
• Hinglish (Hindi + English)Hinglish