Do product management recruiters at ISB require prior PM or product experience?

Most PM recruiters at ISB do not require a formal PM title in your background, but they almost universally expect product-adjacent experience, and that distinction matters enormously when shortlists go out.

What Recruiters Actually Screen For

Companies like Google, Microsoft, Flipkart, Amazon, and Meesho recruit PMs from ISB every year. Their shortlisting filters are not about job titles.

They look for evidence that you have shipped something, influenced a product decision, or worked directly with engineers and designers to solve a user problem. An SDE at Swiggy who built a feature end-to-end reads as a stronger PM candidate than a strategy consultant who has never touched a product roadmap.

The practical consequence is that engineers from product companies clear shortlists at a noticeably higher rate than finance, operations, or general management profiles from the same batch. This is not rumor.

It is a consistent pattern across recent ISB cohorts.

The Engineer Advantage

If you are an SDE or engineer from a product-first company, your profile is genuinely well-positioned. Recruiters treat hands-on engineering exposure at a product firm as a reasonable proxy for PM readiness.

You understand technical trade-offs, you have probably sat in sprint planning sessions, and you can credibly discuss build-versus-buy decisions. That background travels well into PM interviews at companies like Razorpay, PhonePe, and Atlassian, all of which have recruited from ISB.

This does not mean the path is automatic. You still need to demonstrate structured thinking, user empathy, and metric-driven prioritization in your interviews. But you are starting with the shortlist barrier already cleared.

Non-Tech Profiles: The Honest Picture

This is hard, and pretending otherwise does you no favors. If your background is investment banking at Goldman Sachs or Kotak, or operations at Tata Steel or HUL, PM shortlists without product-adjacent signal are genuinely difficult to secure.

A few candidates from these backgrounds do break through each year, but they typically have something concrete to point to: a side project with real users, an internal tool they built, or a clearly documented case where they acted in a product capacity.

Vague claims like "I have a product mindset" do not move shortlisting committees. Specific artifacts do.

Work Experience and Timing

Work experience requirements among PM recruiters broadly range from 2 to 5 years.

ISB's own 24-month minimum admission requirement means most students already clear the lower end of that band on day one. The years themselves are less important than what you did with them.

Building Product Signal Before or During ISB

If your background is outside tech, the most useful moves are concrete ones. Take a no-code or analytics tool and build something small with measurable usage.

Document your thinking in a product teardown or case study and publish it. During the ISB year, seek product-focused internships aggressively, even unpaid or part-time ones, because even 8 weeks of legitimate PM exposure changes how your resume reads at shortlisting.

No amount of ISB brand substitutes for the experience filter PM recruiters apply. The barrier is real, the timeline is short, and the batch is competitive.

Engineers from product companies have a structural head start. Everyone else needs to manufacture the signal before interviews begin.