Start by understanding what a PM actually does, then build visible proof of product thinking — this matters more than any certificate. Take up product-adjacent work in your current role, work on 1–2 end-to-end projects or case studies, and learn basic frameworks for prioritisation, metrics and roadmaps. Network with PMs, ask for referrals, and target APM programs, startup PM roles and internal transfers, since these are the most realistic entry doors in India.

You don't need a "PM" title to start building PM experience — you need evidence. Pick problems around you, talk to users, ship a small solution (an app, a feature, a process fix) and document the outcome like a case study. Combine this with a tailored resume, a few mock interviews, and applications to startups and associate PM roles, where hiring is more skills-driven than title-driven.

Consulting transfers well: structured problem-solving, stakeholder management and data skills are exactly what PM interviews test. Your gaps are usually product sense, technical fluency and execution experience, so work on product case practice, learn how teams build and ship, and take ownership of a product-like initiative. Reposition your resume around outcomes you drove, and target startups and strategy-adjacent product teams that value consulting backgrounds.

There is no fixed degree requirement — PMs in India come from B.Tech, B.Com, design, MBA and even non-technical backgrounds. What recruiters screen for is product thinking, communication and analytical ability, not a specific qualification. An engineering or business degree helps clear initial filters at some companies, but a strong portfolio of projects and clear interview performance matter far more.

Build on regular PM fundamentals first, then add the AI layer: learn what models like LLMs can and cannot do, get comfortable with concepts such as prompts, context, latency and evaluation, and understand the tradeoffs behind AI products. The fastest credibility comes from shipping something — even a small tool built on an AI API — and being able to explain the user problem, design choices and metrics behind it. Companies increasingly want PMs who can bridge AI capability with real user needs.

Most PM interviews test a predictable set of skills: product design and sense, analytical and metrics questions, guesstimates, and behavioural rounds. Prepare a repeatable structure for each type, practise answering out loud rather than just reading, and go deep on the projects listed on your resume. Company research is critical too — be ready with specific feedback on the company's product and how you would improve it.

Give yourself 4–6 focused weeks: learn the common question types first, then practise one or two cases daily across product design, metrics, guesstimates and behavioural stories. Do at least a few mock interviews with experienced PMs or peers, because thinking aloud under time pressure is a separate skill from knowing frameworks. Finally, research each target company's product, users and recent launches so your answers feel specific rather than generic.

For most working professionals, 4–8 weeks at 1–2 hours a day is realistic if your fundamentals are in place. Freshers or career switchers often need 2–3 months, since they also have to build product thinking and portfolio projects from scratch. Consistency beats duration — daily case practice for a month outperforms irregular prep spread over six months.

Always structure before you speak: clarify the question, state your assumptions, pick a framework and then walk the interviewer through it. For product design questions, move from user and problem to solutions, tradeoffs and success metrics; for analytical questions, show your reasoning step by step instead of jumping to a number. Interviewers evaluate how you think, so a clear, structured answer beats a rushed "correct" one.

Expect around 3–5 rounds: a recruiter or hiring manager screen, one or two case rounds on product sense and execution, an analytics or metrics round, and sometimes a guesstimate or technical-fluency round, which is especially common in Indian companies. Each round usually runs 30–60 minutes and is conversational — you'll be asked to think aloud, structure on a whiteboard, and defend tradeoffs. Behavioural rounds probe your past projects in depth, so know your resume inside out.

Freshers typically get product design prompts ("design X for Y users"), improvement questions on well-known apps, guesstimates (like estimating daily orders on a delivery app), "favourite product and why" questions, and basic metrics or prioritisation problems. Interviewers also probe motivation — "why product management without prior experience" is almost guaranteed. They are judging structured thinking and curiosity, not job experience, so walk through your reasoning clearly.

Keep it to one page and make every bullet follow an "action + impact" structure, ideally with a number attached — grew, reduced, automated, shipped. Mirror the keywords of the job description, lead with product work even if it came from a non-PM role, and describe one or two projects as mini case studies: problem, what you did, measurable outcome. Avoid generic responsibilities; recruiters want evidence of product thinking and ownership.

Use a clean, reverse-chronological format — it is what recruiters and ATS tools in India expect. Order the sections as contact details, a short summary (optional), work experience, projects, skills and education, and keep it to one page unless you have several years of experience. Export it as a PDF with standard fonts, and avoid tables, graphics or multi-column layouts that can break applicant tracking systems.

With no full-time PM experience, lead with education, internships and two or three strong projects — college work, freelance builds, or self-initiated products — each written as a problem–solution–outcome story with real numbers wherever possible. Add a skills section covering tools and analytics, and include coursework or certifications only if they add genuine signal. Anything that shows ownership, user focus or measurable results is worth a bullet; everything else can be cut.