How to get hired
First, a trap. Many posts with "PM" in them are project manager roles: timelines, budgets, vendors, PMP. Product manager roles are about deciding what to build, for whom, and measuring whether it worked. If the post asks for PMP, MS Project and "delivery as per schedule", it is project management; our project manager guide covers that. Everything below is about product.
Route 1: move inside your company
This is how most Indian PMs got their first role. An engineer who keeps asking "why are we building this?", a support lead who knows every customer complaint by heart, a business analyst who writes better specs than the PM, a sales engineer who knows what deals are lost over. Start doing PM work in your current job: write the one-page spec for a small feature, own its launch, and track the numbers after. Then ask your manager for an Associate Product Manager or Product Owner title. Internal moves are far easier than convincing a stranger.
Route 2: MBA campus
Product roles at consumer internet companies, fintechs and SaaS firms are offered at top B-schools, usually to candidates with two or three years of work experience before the MBA (often engineering). Without prior experience, an MBA alone rarely gets you a PM role; it gets you a product analyst or strategy role, which can lead there.
Route 3: product analyst, then PM
Join as a Product Analyst: you live in the funnel data, run A/B test analysis, and sit in every product review. After a year or two of this, the PM step is natural.
Route 4: startups
Early-stage startups hire generalist PMs with less formal experience, if you can show you have shipped something: a side project with real users, a community you built, an internal tool your team adopted.
What PM interviews test
- Product sense. "Design a feature for UPI payments for elderly users." They watch whether you pick a specific user and problem before jumping to solutions.
- Metrics. "Daily orders on our grocery app dropped 8% yesterday. Walk me through it." Check the data first (a tracking bug?), then segment by city, platform, new versus repeat users, and look at what changed (a release, a competitor sale, a festival, rain).
- Prioritisation. Ten requests, capacity for three: which and why. Expect to defend a trade-off.
- Execution and stakeholders. How you'd handle engineering saying a deadline is impossible, or sales promising a feature you haven't agreed to.
- Written case. Many companies ask for a short PRD or teardown as a take-home. It is often the round that decides.
- Technical depth. For B2B and platform PMs: APIs, how a payment gateway callback works, what a database migration risks.
Portfolio
Write two product teardowns of Indian apps you use: who the user is, the core job they hire the app for, what is broken, one feature you'd build, and how you'd measure it. Keep each to two pages. One good teardown sent with a referral request does more than a dozen cold applications.
Certifications
None are needed for product roles. Product Owner certificates (CSPO from Scrum Alliance, PSPO from Scrum.org) help in IT services and banking teams where "Product Owner" is a defined Scrum role, and that can be a stepping stone.
First titles
Associate Product Manager, Product Analyst, Product Owner, Product Manager I, Business Analyst – Product, Product Specialist.
What the work is like
You own outcomes without owning people. Engineers, designers and analysts don't report to you, so you get things done by being clear, prepared and trusted. Weeks swing between deep work (specs, data, user calls) and a calendar full of reviews. Launch weeks and incidents are long, and you'll be the one explaining a bad metric in the Monday review.
The ladder: APM, PM, Senior PM, Group PM or Principal, then Director and Head of Product. Pay jumps sharply at Senior PM, and PMs in fintech, SaaS and consumer internet typically earn more than product owners in services firms.