Select Product Manager Interview: Questions, Experience & Prep (2026)

Select currently has 13 open Product Manager positions across India, per knok jobradar data from July 2026. Bangalore leads PM hiring nationally, with Delhi also showing strong demand. The interview process at Select typically spans 3-5 rounds, covering product thinking, data analysis, execution, and stakeholder management. Candidates report that interviewers look for clear reasoning, user empathy backed by data, and the ability to drive cross-functional teams without formal authority.

Salary bands for PM roles in India reflect a wide range across seniority levels.

This guide covers the questions that come up most often at Select, frameworks that hold up under pressure, and mistakes that cost candidates the offer.

Candidates who have interviewed at Select report these questions appearing most often. Each one signals what the company values, so treat them as clues to the culture.

1. Walk us through a product you genuinely admire and what single change you would make to it.
2. How do you prioritize a backlog when engineering, sales, and design all want different things?
3. A core metric drops sharply overnight. How do you investigate it and what do you do first?
4. Design a feature to improve retention for a B2B product with a mix of power users and occasional users.
5. Tell me about a product you took from idea to launch. What was your process and what would you change?
6. How do you define success for a new feature before it ships? What metrics would you track and why?
7. A high-value customer demands a feature not on your roadmap. How do you respond?
8. Your engineering team is pushing back on a deadline because of technical debt. How do you handle it?
9. Describe a time you made a significant product call with incomplete or conflicting information.
10. How would you approach expanding an existing product into a new city or market segment in India?
11. Tell me about a disagreement you had with your manager or a senior leader. How did it resolve?
12. How do you collect user feedback at scale and turn it into a prioritized requirements list?

Use the STAR format for every behavioural question. Keep answers to 2-3 minutes. The three examples below show how to structure strong responses.

Q: Tell me about a product you took from idea to launch.

*Situation:* I was the sole PM for a B2B invoicing tool at a mid-size fintech. The sales team was losing deals because competitors had a bulk payment feature we lacked.

*Task:* I needed to scope, prioritize, and ship a bulk payment flow within one quarter without disrupting the existing payment experience.

*Action:* I ran discovery calls with accounts that had churned to confirm the hypothesis. I wrote a brief doc with three scope options and got alignment from engineering and finance in one working session. I chose the middle option, which covered the commonly cited use cases without touching the core payment engine. I ran two rounds of usability testing with a handful of pilot customers before rollout.

*Result:* The feature shipped on time. The sales team reported it resolved objections in their next renewal cycle. I documented the lessons in a post-mortem and shared it with the wider product org.

---

Q: Describe a time you made a product decision with incomplete data.

*Situation:* Our analytics pipeline broke during a key product review. I had partial data and a go/no-go decision due the next morning.

*Task:* I had to recommend whether to roll out a redesigned onboarding flow to all users or hold.

*Action:* I segmented the data I had by user cohort and looked for directional signals rather than absolute numbers. I noted the limitations clearly in my recommendation doc. I listed the risks of delaying versus proceeding, assigned rough likelihoods based on what we knew, and recommended a phased rollout to a smaller segment with a clear rollback plan.

*Result:* Leadership approved the phased rollout. The following week, with full data restored, the results validated the direction. The rollback plan was never triggered. My recommendation doc became a template the team reuses for ambiguous calls.

---

Q: Tell me about a time you disagreed with your manager on a product decision.

*Situation:* My manager wanted to deprioritize mobile improvements in favour of a new dashboard feature for enterprise clients. I believed the mobile gap was driving early churn among SMB users.

*Task:* I needed to make a data-backed case without damaging the relationship or slowing the roadmap.

*Action:* I pulled session data, support tickets, and exit survey responses (all internally available) and built a one-slide summary showing the pattern. I asked for a short slot to present it, framing the conversation as 'here is what I am seeing, tell me what I am missing' rather than a debate. I proposed a compromise: one engineer for two sprints on the mobile fixes, running parallel to the dashboard work.

*Result:* My manager agreed to the compromise. The mobile fixes addressed a commonly cited support category within weeks. The enterprise dashboard shipped on schedule.

Product Sense Questions

When asked to design a feature or improve a product, use a simple structure: clarify the goal, identify the user segment, state the problem clearly, propose solutions, pick one and justify the choice, then define how you would measure success. Interviewers care more about the reasoning chain than the specific idea.

Metric Drop Questions

Always start by checking whether the drop is real (data pipeline issue, tracking bug, definition change) before diagnosing the cause. Then break the metric into its components. If daily active users drop, look at new versus returning users, by platform, by geography, and by acquisition channel. Narrow the problem space before jumping to a root cause.

Prioritization Questions

A lightweight approach: score each item on user impact, business value, and implementation effort. Show the trade-offs explicitly. Candidates report that Select interviewers want to see you hold multiple stakeholder perspectives simultaneously without losing sight of the user.

Estimation Questions

If asked to size a market or estimate a figure, state your assumptions out loud, use round numbers, sanity-check against something you already know, and flag where your uncertainty is highest. The interviewer is watching your structure, not checking your arithmetic.

Behavioural Questions

Use STAR (Situation, Task, Action, Result). Keep Situation and Task brief. Spend most of your time on Action (what you specifically did, not 'we') and Result (what changed, what you learned). Quantify results where you honestly can, and hedge when data is thin.

User Empathy Grounded in Data

Select interviewers typically want to see you move between user stories and numbers without losing either. Saying 'users are frustrated' is weak. Saying 'users drop off at step three, which session recordings confirm is the upload screen' is strong.

Clear Thinking Under Pressure

Candidates report that interviewers sometimes interrupt or push back deliberately. They want to see whether you hold your reasoning or crumble. When challenged, pause, acknowledge the point, and either defend your answer with logic or update it with a clear reason.

Ownership Without Authority

PM roles require influencing engineers, designers, and business teams you do not manage. Interviewers look for examples where you drove alignment, resolved conflict, or unblocked a team through communication rather than escalation.

Business Awareness

Good product thinking connects features to revenue, retention, or competitive position. Interviewers typically expect candidates at the PM (3-6 year) level and above to speak the language of business outcomes, not just user outcomes.

Structured Communication

Organize your answer before you speak. A brief pause to structure a response is always better than a rambling two-minute answer. Use signposts like 'I will cover three things' or 'let me start with the user, then the business angle.'

Week 1: Understand Select

Research Select's products, recent news, and any publicly available blog posts or case studies. Understand who their users are and what problems the product solves. Practice the metric drop framework daily using a product you personally use.

Week 2: Active Practice

Do mock interviews for product sense and behavioural questions. Record yourself and watch the playback. Candidates report that seeing yourself on video catches filler words and vague answers faster than any other method. Prepare 5-6 STAR stories covering: a launch, a prioritization call, a conflict, a failure, and a decision made with incomplete data.

Week 3: Polish and Gap-filling

Review each STAR story for specificity. Replace 'we improved retention' with the specific action you personally took. Research commonly cited PM interview questions for the sector Select operates in. Prepare two or three thoughtful questions to ask the interviewer about product strategy and team structure.

On the Day

For every question, pause before answering and state your structure out loud. If you do not know something, say so and reason through it. Ask clarifying questions before diving into any design or estimation problem. Candidates report that interviewers reward intellectual honesty over false confidence.

While you are preparing, knok checks 150+ job sites nightly, applies to roles that match your resume, and messages HR for you, so you do not miss Select's openings or similar PM roles as they go live.

Jumping to Solutions

For design and product sense questions, many candidates skip straight to features without clarifying the problem, the user, or the goal. Interviewers notice this immediately. Always spend the first minute on framing before proposing anything.

Using 'We' Instead of 'I'

Behavioural answers must be about what you specifically did. 'We launched a feature' tells the interviewer nothing about your contribution. Say 'I wrote the spec,' 'I ran the user interviews,' 'I made the call to cut scope.'

Vague Metrics

Saying 'it improved significantly' or 'users were happier' is weak. Use actual figures where you have them, and hedge honestly where you do not: 'the exact number is confidential but the direction was clear and we tracked it consistently.'

Ignoring Trade-offs

Prioritization answers that make every decision sound easy signal inexperience. Good PMs name what they gave up and why the trade was worth it.

Skipping Clarifying Questions

Jumping into a design question without clarification suggests you make assumptions in real work too. Ask about the user segment, the constraint, the goal, and the time horizon before answering.

Over-preparing Scripts

Memorised answers sound flat and collapse when the interviewer pushes back. Know your stories well enough to retell them naturally, not recite them.