ISB admits students in multiple rounds every year. You first check eligibility — a bachelor's degree is mandatory, and for the flagship PGP you need at least 24 months of full-time work experience by the programme start date, while PGP YL is meant for final-year students and recent graduates with under 24 months of experience. Next, you take the GMAT or GRE and submit the online application through the ISB application portal with essays, a detailed résumé and one recommendation, along with the application fee. Shortlisted candidates are then interviewed, and offers are released round-wise a few weeks after the interviews.

The core requirements are a bachelor's degree, a valid GMAT or GRE score, essays, one letter of recommendation and a current résumé, all submitted with the application fee within your chosen round. For the PGP, you need a minimum of 24 months of full-time work experience by the time the programme begins; final-year students and fresh graduates with less experience apply through PGP YL instead. Shortlisted applicants complete an interview as the final stage. Since essay prompts and formats are updated every cycle, always confirm the latest checklist on the official admissions page before applying.

The ISB application fee has been around ₹6,000 per application in recent years, though the exact amount can change from cycle to cycle and may vary slightly by programme. It is a one-time, non-refundable payment made online when you submit your application for a particular round. If you reapply in a later round or the next admissions year, the fee generally has to be paid again, so it makes sense to submit only when your GMAT/GRE score, essays and résumé are genuinely ready.

ISB usually opens applications in the middle of the year and closes them in stages — typically a Round 1 deadline around September, Round 2 around November, and in some cycles a final round in January. Exact dates shift every admissions year and are announced on ISB's official admissions page, so treat those months as an indicative pattern rather than a fixed calendar. Applying in an earlier round is generally advantageous because interview slots and scholarship consideration are distributed across rounds.

When you enter your test scores, ISB asks for identifiers that let it match and verify your self-reported score with GMAC's records, and for the newer GMAT Focus Edition this is done using the GMAT Focus ID — the unique ID attached to your exam attempt. You can find it by logging into your mba.com account and opening your official score details. Enter it exactly as shown so there is no mismatch during verification, and make sure your official score is released to ISB through mba.com when the institute asks for it at a later stage.

Start with your own application: ISB interviews are largely profile-based, so re-read your essays and résumé and be ready to defend or expand on every claim in them. Get absolute clarity on why you want an MBA, why ISB, and what your short-term and long-term goals are, since these come up in almost every interview. Prepare five or six well-structured stories covering leadership, teamwork, conflict and failure, and practise saying them aloud instead of memorising scripts. Finally, do two or three mock interviews — ideally with ISB alumni — so you get comfortable thinking on your feet and handling follow-up questions.

The most frequent ones are "tell me about yourself", "why MBA now", "why ISB specifically", and "what are your short-term and long-term goals". Expect deep dives into your current role, key projects and measurable impact, plus questions drawn directly from your essays, as panels often probe anything that looks inconsistent or vague. Many candidates also face opinion-based or current-affairs questions, such as views on a recent business development, and behavioural ones about teamwork, failure or leadership. The interview usually ends with "do you have any questions for us?", so keep one or two thoughtful questions ready.

After each round's shortlist, selected candidates receive their ISB interview dates and slot options by email, with interviews typically conducted over a window of a few weeks, either online over a video call or in person. The panel usually has two members — often an admissions committee member paired with an alumnus — and the conversation lasts roughly 25 to 40 minutes. It plays out more as a structured conversation than a stress test, with most questions revolving around your profile, goals and awareness of current business trends. Final decisions are generally communicated within a few weeks of the interview, round-wise.

Most PM interviews draw from four buckets. Product design questions ("How would you improve WhatsApp?" or "Design a product for X"), execution and metrics questions ("How would you measure the success of a feature?" or "A key metric dropped 20% — how would you diagnose it?"), product strategy questions ("Should this company enter that market?"), and behavioural questions about conflict, failure and working with engineers. Fresher-level interviews also commonly include guesstimates such as "How many food deliveries happen in a city in a day?" Knowing the categories helps you prepare frameworks and stories for each instead of reading random question banks.

The key is structure, not memorised answers. For product design questions, clarify the goal and users first, list use cases, prioritise one problem, propose solutions with trade-offs, and close with success metrics. For execution questions, start with a hypothesis, break the metric down into components, and walk through possible causes logically instead of jumping to conclusions. For behavioural questions, use the STAR format — situation, task, action, result — with real examples from your own experience. Whatever the question, think aloud, check in with the interviewer, and refine your answer when they push back, because they are evaluating your reasoning more than your final answer.

Treat it as a preparation project rather than a one-off attempt. Build fluency in the core areas — product sense, execution and metrics, strategy and behavioural — and practise answering out loud, since silent thinking rarely translates well under pressure. Research the company's product deeply, use it yourself, form opinions on what you would improve, and back your points with numbers wherever possible. Most importantly, do multiple mock interviews with experienced PMs and iterate on the feedback after each one; candidates who convert offers usually credit mock-driven refinement, not just reading frameworks.

A typical PM hiring loop has a recruiter screen followed by three to five rounds with PMs, senior PMs or the hiring manager. Product sense or design rounds test how you think about users and trade-offs, execution rounds test metrics, prioritisation and diagnosing metric changes, strategy rounds test business thinking, and one round is usually behavioural. Some companies add a take-home assignment, a written product critique or a case presentation. Across all rounds, interviewers check whether you can structure ambiguous problems, communicate clearly and ground decisions in user and business context — not whether you have one "correct" answer.

For freshers, interviewers focus on fundamentals and structured thinking rather than industry experience. Expect "what does a PM actually do?", "why product management after your degree?", app teardowns like "pick an app you use daily and tell us how you'd improve it", simple guesstimates, and basic metrics questions such as how you would measure the success of a feature. Internships, college projects, hackathons and even running a club or a small online initiative become your evidence base. What usually separates selected freshers is clarity of thought and a genuine habit of analysing everyday products, so build both before the interview.

Start with one fundamentals-plus-practice book rather than collecting many. "Cracking the PM Interview" is the standard starting point for understanding the role and the hiring process, "Decode and Conquer" is useful for frameworks for design, metrics and strategy questions, and "Swipe to Unlock" helps non-technical candidates get comfortable with basic tech concepts. Whichever book you pick, remember that reading alone will not get you through — the real improvement comes when you close the book, answer questions aloud and get feedback on your thinking. Use books for frameworks, and use practice and mocks to actually build the skill.

It depends on your starting point. If you are completely new to PM interviews, a structured course can save weeks of confusion by giving you a clear syllabus, solved examples and a practice plan. If you already know the frameworks, a course adds limited value, and your time is better spent on mock interviews with experienced PMs, where you get personalised feedback on how you actually think and communicate. A sensible approach is to use a course to build the base, then invest heavily in practice and feedback — that combination is what converts into offers.