Can a candidate with 22 months of gap and 7 months of business analyst experience secure Product Management roles at an MBA?

Securing a Product Management role at MBA placements with 7 months of business analyst experience is genuinely difficult, and the 22-month gap adds another layer of complexity. Here is an honest breakdown.

The core challenge with PM roles

PM roles at most MBA placement cells tend to attract candidates who can demonstrate clear product thinking backed by meaningful pre-MBA exposure. That usually means 2 or more years of work in tech, product, or closely adjacent roles.

A 7-month BA stint is not a disqualifier on its own, but it does mean the candidate needs to position that experience very carefully - highlighting any product-adjacent work done during those months, such as requirement gathering, user research, product roadmap inputs, or cross-functional coordination with engineering or design teams.

Students from IT/ITES backgrounds with shorter work stints often report finding PM shortlists competitive during both Summer Internship Placements (SIP) and final placements. This is not a documented cutoff rule, but a pattern that emerges consistently across recent batches.

The gap question

A 22-month gap is a legitimate concern that will come up in PI rounds well before placement season. Admissions committees will probe it, and so will recruiters.

The gap needs a clear, credible narrative - freelance work, certifications, health, family, entrepreneurship attempts - anything substantive. A gap that is explained well is manageable.

An unexplained gap raises red flags at every stage.

Analytics as a more accessible alternative

A common observation from recent batches is that Analytics roles are more accessible than PM roles for candidates with IT/ITES backgrounds and limited work experience. Analytics roles, particularly in BFSI, e-commerce, and consulting-adjacent functions, tend to evaluate candidates more on quantitative aptitude and problem-structuring skills.

A BA background with data or reporting exposure maps reasonably well to these roles.

This is a generalisation, not a guarantee. But if the candidate's actual skills are closer to data and analysis than product strategy, targeting Analytics alongside PM is a more realistic approach than narrowing entirely to PM.

What can improve the PM candidacy

• Any product-adjacent work from the BA stint should be surfaced prominently in the resume and MBA application.
• Pre-MBA initiatives - a product case study, a side project, a product management certification (like AIPMM or similar) - can help signal genuine PM intent.
• The MBA program itself matters. Programs at stronger placement institutions with active PM recruiting from tech and consumer internet companies give a better platform.
• Networking within the batch with peers who have stronger PM profiles, and targeting PM roles at early-stage or mid-stage startups rather than only large tech firms, opens up more realistic paths.

The honest summary: PM is a stretch given the profile as described, but not impossible with deliberate positioning. Analytics is a more natural fit given the background.

Running both tracks in parallel during placement season is a practical approach.

Compare MBA programs by placement profile if you want to see which schools have stronger PM recruiting pipelines relative to their intake profile.