SRCC Students: Preparing for Product Management Internship Interviews and Case Rounds

To prepare for a product management internship interview, practise a small set of case prompts out loud, and score each answer on the same rubric: clear problem framing, sensible metrics, defensible prioritisation and honest trade-offs. Commerce students at Shri Ram College of Commerce (SRCC) already have a useful base in numbers and structured argument, so the gap to close is usually product vocabulary and speaking in a tight structure. This guide gives you the prompts, the rubric, a worked example and a 14-day plan.

What a product case round is actually testing

Companies run product interviews in different ways. Some use a conversational case, some give a written exercise, and some mix in a guesstimate or a metrics question. Do not assume one format. Whatever the format, an interviewer needs to see whether you can think clearly about a user problem and make a decision you can defend. That reduces to four skills, and the rubric later in this article is built on them.

• Framing: who is the user, what is the problem, and what is the goal of the business or product?
• Metrics: how would you know the product is working, and what could go wrong while that number rises?
• Prioritisation: given limited time and people, what do you do first, and why?
• Trade-offs: what do you give up with your choice, and how would you limit the damage?

Notice what is missing: drawing wireframes, knowing code, or reciting a famous framework by name. Frameworks are scaffolding. The interviewer is listening to your reasoning, not checking a template.

SRCC: Using the Placement Cell Route for Product Management Interview and Case Preparation

Shri Ram College of Commerce is a constituent college of the University of Delhi, and its Placement Cell page explains how internships and placements are organised. The cell manages the placement process and engages corporates and other organisations for internship opportunities. The page adds that first- and second-year undergraduate students are eligible to seek formal internship opportunities, while third-year students may apply for placement through the cell, subject to its rules and guidelines. For a student aiming at product management roles, this means preparation for interviews and case rounds should be timed to your year of study, not left until the final year.

The placement page describes the cell as the link between companies and students, and says opportunities include placements, internships and articleships. Student support listed there includes CV vetting, training sessions on various topics and casebook training resources. Those resources are a natural starting point for case practice, because they reflect how the cell prepares students for recruiters’ selection rounds.

The page also notes that a recruitment brochure is published for each season, and earlier brochures are linked for reference. Details on eligibility, process and timelines are not set out on the page itself, so the current brochure and the cell’s own announcements are the sources to read. The page does not describe a product management track, and employers’ shortlisting criteria differ year to year, so do not assume a particular format.

Use the college’s guidance as a framework only: it does not promise any internship, offer or particular company visit.

Questions to put to the cell before case season

• Ask which year of study the cell currently accepts for internship applications and what registration is needed.
• Obtain the latest recruitment brochure and check which sectors and roles are listed.
• Ask when CV vetting and casebook training sessions are scheduled, and whether they are open to all years.
• Check whether product management or general management roles are mentioned in recent recruiter lists.
• Confirm any rules about applying to companies outside the cell’s process.

The scoring rubric

Use this rubric on every practice answer. Record yourself on a phone, play it back, and score honestly. If you practise with a friend, have them score using the same table, then compare. Each row is scored from 0 to 4, giving a maximum of 24.

Reading your total

• 0-10: you are listing, not deciding. Repeat the same prompt until you can finish with a recommendation.
• 11-17: your structure works. The usual weak spots are metric definitions and specific trade-offs.
• 18-24: you are answering at a level where small refinements matter, such as pacing and handling interruptions.

The totals are only a self-diagnostic tool. They are not a prediction of any interview result.

Eight practice case prompts

These prompts are illustrative practice material written for this guide. They are not questions taken from any company’s interviews. Spend 15 minutes on each: two minutes of clarifying questions, eight of structured answer, five of self-scoring.

Prompts grouped by the skill they sharpen

• Metrics: prompts 1, 2, 5 and 8. Practise stating a metric as a ratio with a time window.
• Prioritisation: prompts 3 and 7. Practise choosing criteria before ranking.
• Trade-offs: prompts 4 and 7. Practise saying what you are choosing not to do.
• Framing: prompt 6. Practise narrowing the user before generating ideas.

Worked illustrative example: prompt 3

This is an illustrative answer written to show the shape of a good response. No product data is real, and the numbers are invented for the demonstration.

Prompt: You have one engineer-month. A language-learning app’s backlog has streak reminders, offline lessons, a leaderboard, and a redesigned onboarding. Pick one.

Step 1: Clarify

Ask two questions: what is the company’s current goal, and where are users being lost? Suppose the interviewer says the goal is to grow the number of learners who are still active in week four, and that most users stop within the first three days. That single fact reshapes the answer.

Step 2: State the metric

Primary metric: the share of new users who complete at least one lesson on each of three separate days within their first 14 days. Numerator: new users who meet that condition. Denominator: all new users in the cohort. Guardrails: lesson completion quality (for instance, quiz accuracy, so we do not reward shallow tapping) and uninstall rate within 30 days (so reminders do not annoy users into leaving).

Step 3: Score the options

Choose three criteria and be explicit about them: impact on the primary metric, confidence in that impact, and effort. Rate each from 1 to 3, where 3 is best (so low effort scores 3).

The ratings are judgement calls and you should say so. What matters is that another person can see your reasoning and disagree with a specific cell.

Step 4: Recommend and name the trade-off

Recommend streak reminders. Users drop out in the first three days, reminders directly target that window, they are cheap to build, and the effect can be measured quickly with an A/B test. The trade-off: reminders can feel naggy and raise uninstalls, and they do not fix a confusing first session. Mitigation: cap frequency, let users set the time, and watch the uninstall guardrail. Reversal signal: if uninstalls rise faster than week-one retention improves, pause and move to onboarding in the next cycle.

Step 5: Close

Finish in one sentence: “I would ship streak reminders first, measured against three-day activity, and queue onboarding redesign next.” Then stop talking. Interviewers often ask follow-ups, and filling silence with new ideas weakens a clean answer.

Scoring this answer on the rubric

• Framing: 3 (clarified the goal and the drop-off point, but did not segment users further).
• Primary metric: 4 (numerator, denominator and window defined).
• Guardrails: 4 (two, each tied to a specific risk).
• Prioritisation: 3 (explicit criteria, but ratings are subjective).
• Trade-offs: 4 (cost, mitigation and reversal signal).
• Communication: 3 (clear, though step 3 could be shortened).

Total: 21 out of 24.

Three mini-toolkits for the three core skills

Metrics: a five-question checklist

1. What is the goal of the product or feature, in one sentence?
2. Which single number best shows progress toward that goal?
3. How exactly is it calculated, and over what time window?
4. What would a cheating or careless way of raising it look like, and which guardrail catches that?
5. Is it a leading indicator (moves quickly) or a lagging one (confirms later)? Which do you need now?

A useful habit: whenever you hear a metric that moved, ask whether the numerator rose, the denominator fell, or both. Many metric prompts, including prompts 5 and 8, hide the answer there.

Prioritisation: choose criteria first

Many candidates name a framework and then fill it with arbitrary numbers. Reverse this. Decide what the business needs right now, then pick two or three criteria that reflect it.

• If the goal is growth, weight reach and impact on the acquisition or activation step.
• If the goal is retention, weight impact on repeat use and how early in the user journey the change appears.
• If the team is small, give effort and risk more weight.
• If the evidence is thin, favour the option that teaches you the most cheaply, even if its upside is modest.

Trade-offs: a sentence template

Practise this form until it is automatic: “I would choose X over Y because the goal is Z. The cost is C, and it falls mostly on group G. I would limit it by M, and I would change course if signal S appears.” Four short clauses cover cost, affected party, mitigation and reversal. Any trade-off answer missing one of the four will feel incomplete to a listener.

Common mistakes and how to fix them

A 14-day preparation plan

This plan assumes about 60 to 90 minutes a day alongside classes. Shift days around your timetable and exams.

1. Days 1-2: vocabulary. Write one-line definitions for funnel, cohort, retention, A/B test, MVP, backlog, sprint and guardrail metric. Use each in a sentence about an app you use daily.
2. Days 3-4: product teardown. Pick one app and write down its user, its goal, its likely primary metric and one thing you would change. Do this for two apps.
3. Days 5-6: metrics prompts. Do prompts 1, 2, 5 and 8. Score each with the rubric.
4. Day 7: review. Re-read your four scores and identify your lowest-scoring dimension.
5. Days 8-9: prioritisation prompts. Do prompts 3 and 7. Rebuild the scoring table for each with different criteria and see whether the winner changes.
6. Days 10-11: trade-off and framing prompts. Do prompts 4 and 6. Use the four-clause trade-off template aloud.
7. Day 12: mock with a person. Ask a friend or senior to play interviewer, interrupt you, and challenge one assumption.
8. Day 13: behavioural stories. Prepare three true stories from coursework, society work or projects: one where you used data, one where you handled disagreement, one where something failed. Keep facts accurate.
9. Day 14: full run. Do two random prompts back to back with a timer, then write down three habits to keep and one to fix.

Build proof of practice before you interview

Interviewers respond well to evidence that you have actually done some product thinking. A short written teardown, a one-page feature proposal or a small structured exercise gives you something concrete to talk about. If you want a structured, low-stakes way to do this, the free two-week online internship from CareerSwami offers 26 tracks, a free offer letter and a free completion certificate after successful completion. It is an independent programme and has no connection with SRCC. Treat it as practice and portfolio material; it does not replace the preparation above.

Questions to settle with SRCC before you apply

Use this list to get accurate, current answers from official sources rather than relying on hearsay from seniors or social media.

• Internship rules: ask your department office or the relevant faculty coordinator in writing whether internships are mandatory, optional or for credit in your course and year, and ask for the circular or handbook page that says so.
• Career-development or placement activity: check the college website and official notice boards for the name of the committee or cell that handles it, its contact email, and its registration process.
• Eligibility and timing: ask whether there are attendance, year-of-study or no-objection requirements before applying for external internships.
• Letters and certificates: ask what documents the college will accept as proof of an external internship if your course requires one.
• Recruiter processes: if a company visits or posts an opening through the college, rely on that company’s own brief for the selection stages instead of assumptions passed around by peers.

Frequently Asked Questions

Do I need a technical background to clear a product case round?

Not for most internship-level case rounds. You need to understand how products are built well enough to discuss effort and feasibility sensibly, which the vocabulary work in days 1-2 of the plan covers. Deep coding knowledge is not what a general case answer is scored on, though some roles may expect more, so read each role description.

How many practice cases are enough as a Shri Ram College of Commerce student?

Eight to twelve done properly, with scoring and a repeat of your weakest type, beat thirty done casually. The point of repetition is to make the structure automatic so your attention goes to the content.

Should I memorise frameworks like RICE or CIRCLES?

Know what they are, but do not recite them. RICE-style scoring is useful for the prioritisation step, and any structured approach to a design question can help, but your answer should sound like a person reasoning. Choosing criteria that fit the stated goal matters more than the framework’s name.

What if I do not know the product in the prompt?

Say so briefly and ask the interviewer for a one-line description, then proceed. Pretending to know a product and getting details wrong costs more than admitting you have not used it.

How do I use my commerce coursework in a product answer?

Bring in unit economics, margins, pricing logic and basic statistics where they genuinely apply. For example, in prompt 4 a short comparison of revenue per seller against revenue per buyer shows commercial thinking. Do not force them into every answer.

How long should an answer to a case prompt be?

Around five to eight minutes of speaking, after a short clarifying exchange, is a sensible practice target. The real length depends on the interviewer, who may interrupt or redirect, so practise being stoppable at any point.

What should I do if I freeze mid-answer?

Pause, restate the goal in one sentence, and return to your last clear point. Saying “let me check my structure” is acceptable. Practising with interruptions in the day-12 mock makes recovery easier.

Can a short online internship help my interview preparation?

It can give you something specific to discuss, such as a task you completed and what you learned. How much weight any employer gives to it is up to that employer, so present it honestly as a short, free learning experience and focus on what you can explain.

Related Product Management guides

• Hindu College, University of Delhi: Product Management Internship Tasks from Research to Roadmaps
• Lady Shri Ram College for Women Students: Product Management Internship Report Structure and Evidence
• Miranda House Students: Product Management vs Product Analyst Internships, Compared
• All Product Management internship guides