Product manager hiring in Indian IT staffing is messy because the title spans junior product owners who maintain JIRA backlogs to senior PMs who own P&L for a revenue line. Most candidates over-claim. Four distinct jobs, four distinct salary bands — 8 to 15 lakhs for a product owner, 15 to 30 lakhs for a mid-level PM, 30 to 60 lakhs for a senior PM, and 60 lakhs and up for a principal PM or director at Bangalore product companies. The strong IT PM combines three hard-to-fake qualities — customer empathy from real interview practice, technical literacy from engineering or design background, and ruthless prioritization from saying no more often than yes. Weak PMs get by on meeting attendance and politeness. One caveat specific to Indian staffing: many strong PMs come through engineering at product companies (Flipkart, Swiggy, Razorpay, PhonePe) without an MBA. Conversely, many weak PMs have MBAs from good schools and zero shipping experience. Weight the interview more than the paper.
Has done real customer interviews — 30 or more across their career, some in the last year. Can describe what they learned from a specific interview and how it changed a decision. Not "I do NPS surveys" or "sales talks to customers." Firsthand practice is non-negotiable.
Has used and can defend a real framework — RICE, ICE, Kano, WSJF, opportunity scoring. Not "I prioritize by gut" or "by what the loudest stakeholder says." Senior PMs articulate why they chose a framework for a context and when they break from it.
Has substantive conversations with engineers about architecture and trade-offs without becoming a bottleneck. Ideal: former engineer, designer, or analyst who moved into product. Direct-to-PM is fine at 7+ years with demonstrated tech vocabulary.
Has owned at least one metric (activation, retention, revenue, conversion) end-to-end with baseline, target, and result. Not "I worked on features that hopefully improved retention." Outcome attribution is the fastest separator between PM and product owner.
Writes crisp PRDs, clear exec updates, structured emails. Ask for a sample PRD, redacted if needed. PMs who can only communicate in meetings struggle in distributed teams and lose political battles they could have won in writing.
PMs with prior engineering or design produce shippable specs that engineers do not need to interpret. Worth a premium. Most of the strongest PMs at Indian product companies started in one of these roles.
Fintech, healthtech, B2B SaaS, e-commerce, logistics. Reduces ramp dramatically and earns the right to push back on stakeholders with context. Ask for the name of their last domain problem they solved.
PMs who pull their own data make five times faster decisions than those who depend on an analyst. SQL fluency is the single highest-leverage skill for a PM and most do not have it.
Tells the product story to executives, sales teams, and customers compellingly. Many strong PMs are also strong presenters — not coincidentally. Watch for clarity under light pressure in the interview itself.
Has shipped a pricing change, tier rework, or packaging experiment. Under-hired skill in Indian B2B SaaS. Worth a premium especially at senior level where revenue ownership is expected.
Walk me through a feature you killed or a project you shut down in the last 18 months. What did you learn, and what did you do with the team on that project?
What to listen for
Real example with real reasoning — data showed it would not move the metric, strategic priorities shifted, cost exceeded opportunity. Handled the team transition thoughtfully. Extracted specific lessons. Vague "we decided to deprioritize" without detail means they have not actually killed anything — they are conflict-averse.
How do you decide what NOT to build when three executives each have a strong opinion about what is most important?
What to listen for
Cost-of-delay analysis, opportunity cost relative to strategic goals, clear framework applied consistently. Facilitates the disagreement, does not unilaterally decide. Uses data where available. Strong PMs know how to make "no" land softly.
Describe the last customer interview you did yourself. Who was it with, what did you ask, what surprised you?
What to listen for
Specific person with role and context, specific open-ended questions (not "would you use feature X"), specific insight that was surprising and changed a direction. Weak candidates describe sales conversations or user testing sessions, not discovery interviews.
A senior exec wants a feature you think is wrong for the product. What do you do, step by step?
What to listen for
Asks why, digs into the underlying goal rather than the specific feature, presents data and alternatives, escalates if disagreement persists, then commits once made. Senior PMs disagree-and-commit rather than passive-aggressive execute. Weak: "I would ship it and say I told you so later."
A metric you owned personally. Tell me the baseline, the interventions you tried, and the outcome.
What to listen for
Specific numbers (not "we improved retention" but "D30 retention went from 18 percent to 27 percent"), specific interventions (three named experiments), honest attribution (what worked, what did not, what we still do not understand). Strong PMs are comfortable with attribution ambiguity.
Write me the first page of a PRD right now for a feature I describe — add multi-language support to our invoice generation.
What to listen for
Problem statement first, user personas affected, business goal and metric, scope (what is in, what is explicitly out), success criteria, dependencies, rough sizing, open questions. Not a JIRA ticket. Strong PMs have a template.
Name a product decision you would make differently today than you made a year ago. Why?
What to listen for
Honest reflection with specific decision and specific cost. Strong candidates mention something they failed at, not just something that worked. Weak candidates describe a generic lesson about "communication" without a specific decision.
A competitor just launched a feature you were about to ship. Walk me through your next week.
What to listen for
Evaluates whether the competitor feature changes the market, talks to customers about their reaction, reconsiders positioning and timing, does not panic-ship or cancel reflexively. Strong PMs treat competitor launches as data, not emergencies.
Score each candidate against these weighted criteria. Total: 100%.
| Criterion | Weight | Signal |
|---|---|---|
| Customer discovery | 25% | Real interview practice with specific insights that influenced decisions. Not surveys, not sales calls — direct discovery conversations. |
| Prioritization discipline | 20% | Has and can defend a prioritization framework. Has killed features. Says no often and well. Can defend a no to a senior stakeholder. |
| Outcome ownership | 20% | Moved real metrics with baselines, targets, and results. Attributes outcomes honestly to specific decisions or experiments. |
| Technical literacy | 15% | Substantive engineering conversations. Informed questions about architecture, dependencies, deployment. Not pretending to code, but not clueless. |
| Communication and storytelling | 20% | Crisp PRDs, persuasive exec updates, clear narratives. Adjusts depth for audience. Can sell a decision without being pushy. |
Has never killed a feature or project in their career — signals conflict avoidance and weak prioritization
Cannot name a specific customer insight that changed a decision last year — has not done real discovery
Defaults to "engineers said it would take too long" as the reason for any scope decision — offloading ownership
Has never owned a measurable outcome with a baseline and a result — was a feature factory, not a product manager
Treats PRD writing as ticket writing — specs are small, technical, with no problem statement or success criteria
Upload Product Manager CVs and let AI score every candidate against the same 42-point evidence rubric.
Try CVPRO Free