PM Foundations
The Product Manager Role: Deep Dive
Insight
Why this matters first
The "What is a PM?" question is one of the most common openers in PM interviews. But it is not a trivia question about titles. Interviewers are testing: Do you understand the paradox of PM? Can you articulate it without sounding like a "mini-CEO"? Do you grasp why influence without authority is the defining challenge?
Get this wrong and you will be underestimated for the entire interview. Get it right and you signal product maturity in 30 seconds.
Product Management: The Real Definition
Product Management is the discipline of discovering what customers need, articulating why that need matters for the business, and leading a cross-functional team to build and ship a solution, all without direct authority over the people executing it.
A PM sits at the intersection of three circles: Business (viability), Technology (feasibility), and Users (desirability). Your job is not to pick one circle. It is to find the overlap where all three agree, and navigate ruthlessly when they conflict.
Insight
The PM Paradox
You are 100% accountable for the product. You have 0% direct authority to make anyone build it. So how do you get things done?
Through INFLUENCE, built on three pillars:
(1) Credibility, engineers and designers believe you understand their constraints
(2) Clarity, the problem is so well-articulated that the team wants to solve it
(3) Conviction, you believe in this enough to stake your reputation
PMs who master influence-without-authority become directors and VPs. PMs who rely on position power top out at Senior PM.
1
Discover what users actually need (not what they say)
Users rarely articulate their true needs. Ask "what do you want in a shopping app?" and you will hear "faster checkout." The real need might be "I want to feel confident my money is safe." Checkout speed is a symptom. Perceived safety is the job-to-be-done. This is why PMs interview, observe, and experiment, not just survey.
2
Validate the business case
Discovering a need means nothing if it conflicts with the business model. Users of a free app might want "no ads," but if ads ARE the business model, that need conflicts with survival. Your job is to find needs that align with how the business makes money, or advocate to change the business model.
3
Define the solution with ruthless prioritization
You cannot solve every problem. The art is choosing which to solve and in what order. This requires frameworks (RICE, WSJF, MoSCoW) that force you to be explicit about trade-offs rather than hiding behind vague language like "this is important."
4
Communicate the vision so teams align
A PM who discovers a need but cannot articulate it has failed. A PRD that is unclear creates rework. A PM who writes a 2-page brief that aligns 8 people is 10x more valuable than one who writes a 20-page document nobody reads.
5
Lead execution without commanding anyone
Engineering could ignore your prioritization. Design could ship a mockup that does not match your spec. But if you have done steps 1-4 well, they will not. They will actively WANT to follow your lead because the direction is so clearly right. That is influence.
6
Measure and iterate
You ship, you measure, you learn. Did the feature move the metric? Is the user actually happier? A PM who ships and never checks is not doing PM, that is wishful thinking. Nothing kills PM credibility faster than claiming success without data.
| Responsibility | Who Owns It | What PM Does | Common Mistake |
|---|---|---|---|
| Decide which problems to solve | PM + Leadership | Research users, propose priority, make the call with data | Letting the loudest stakeholder decide instead of the data |
| Define HOW to solve it | PM + Design + Eng | Write clear user stories and acceptance criteria | Leaving it ambiguous and blaming engineers for misunderstanding |
| Build it technically | Engineering | Understand the trade-offs, do not write the code | Asking "why is this taking 3 weeks" without understanding complexity |
| Make it usable | Design + PM | Test with users, give feedback, iterate | Shipping without user validation and assuming you know best |
| Launch it to customers | Marketing + Comms + Ops | Brief them, ensure they understand value, monitor adoption | Launching and disappearing; not helping customers understand what changed |
| Measure if it works | PM + Data | Define success metrics upfront, track them, adjust | Launching and never checking results; claiming success without data |
Swipe to see more →
Insight
India PM Market Context (verified July 2026)
Top PM employers by tier:
• Tier 1A: Flipkart, Google India, Amazon India, Microsoft, Apple
• Tier 1B: Swiggy, PhonePe, CRED, Razorpay
• Tier 2 (high growth): Meesho, Zepto, Delhivery, Oyo, Unacademy, BharatPe
Current salary bands (verified July 2026): see Module 7, PM Compensation Negotiation.
Post-MBA at ISB/IIMA PGPX with 6-8 YOE typically enters at Senior PM.