Miranda House Students: Product Management vs Product Analyst Internships, Compared

A product management internship is about deciding what gets built and why, while a product analyst internship is about measuring what happened and explaining it with data. Most Miranda House students can start in either, but the better first step depends on whether you prefer writing and prioritising or querying and interpreting. The comparison, scorecard and worked example below help you decide in about an hour.

The short version: two roles, one product team

Both roles sit inside the same product team and often share a manager, a backlog and a weekly meeting. The difference is the question each one owns.

• Product management (PM) intern: “What should we build next, for whom, and how will we know it worked?”
• Product analyst (PA) intern: “What is the data telling us about how people use the product, and what should we do about it?”

In small companies and startups the boundary blurs. A PM intern may pull their own numbers, and an analyst intern may write a feature proposal. Job titles vary between organisations, so read the task list in an internship description rather than relying on the title.

Side-by-side comparison

The table below describes typical patterns in entry-level product work. Individual teams differ, so treat it as a map and not a promise of any particular internship.

A closer look at daily tasks

What a PM intern usually does in a week

• Reads support tickets, app-store reviews or survey responses and groups them into themes.
• Writes a problem statement: who is affected, how often, and what happens today.
• Drafts user stories with acceptance criteria that an engineer can test against.
• Scores backlog items using a simple framework such as reach, impact, confidence and effort.
• Compares three competitor products on a specific flow, such as onboarding or checkout.
• Takes notes in meetings and circulates clear action items afterwards.

What a PA intern usually does in a week

• Pulls a dataset, checks for duplicates, missing values and odd dates, and documents the fixes.
• Defines a metric precisely, for example what counts as an “active user” in a given week.
• Builds a funnel from sign-up to first key action and finds the largest drop.
• Splits users into cohorts by sign-up week and compares retention.
• Summarises an experiment: sample sizes, the metric moved, and whether the difference is large enough to trust.
• Turns findings into a one-page note with a recommendation, not only charts.

Skills you need before you start

For product management

1. Written clarity. Can you explain a problem in five sentences a stranger understands?
2. Prioritisation. Can you justify why one idea comes before another?
3. Basic metrics literacy. You should know conversion, retention and average values well enough to set a goal.
4. User research basics. Writing a short interview guide and spotting patterns in answers.
5. Light technical fluency. You do not code, but you should understand what an API or a database table is.

For product analysis

1. Spreadsheet depth. Pivot tables, lookups, conditional formulas and clean charts.
2. SQL fundamentals. SELECT, WHERE, GROUP BY, JOIN and simple date handling.
3. Statistics basics. Mean versus median, sampling, confidence in a difference, and the idea that correlation is not causation.
4. Visualisation judgement. Picking the right chart and labelling it so it can be read without you in the room.
5. Narrative. Ending every analysis with “so what”.

The practical asset: a role-fit scorecard

Rate each statement from 1 (not like me) to 5 (very like me). Add up each column separately. This is a self-reflection tool and not a validated test, so use it to start a conversation with yourself, not to close one.

How to read your result

• PM column leads by 8 or more: start with a PM-style internship and add basic SQL on the side.
• PA column leads by 8 or more: start with an analyst-style internship and practise writing short recommendation notes.
• Within 7 points: either works. Pick the task list that excites you more, or look for a generalist product internship that includes both.

Worked example: product analyst vs product manager internship (illustrative)

The scenario below is invented to show how the two roles handle the same situation. It is not a real company, dataset or result, and no code or figures here come from an actual run.

Situation: A fictional notes-sharing app notices that many new users sign up but never upload a first note.

The analyst’s path

1. Define the metric: “first-note rate” is the share of new sign-ups who upload at least one note within seven days.
2. Build the funnel: sign-up, profile completed, upload screen opened, note uploaded.
3. Find the biggest drop. Suppose the largest fall is between “upload screen opened” and “note uploaded”.
4. Segment by device and sign-up source to see whether the drop is general or concentrated.

A starting query might look like this (illustrative only, not executed):

SELECT signup_week,
       COUNT(*) AS new_users,
       SUM(CASE WHEN first_note_at IS NOT NULL
                 AND first_note_at <= signup_at + INTERVAL '7 days'
                THEN 1 ELSE 0 END) AS uploaded_in_7d
FROM users
GROUP BY signup_week
ORDER BY signup_week;

Deliverable: a one-page note stating where the drop occurs, which segment is most affected, and one suggested follow-up test.

The PM’s path

1. Write the problem statement: new users reach the upload screen but do not complete an upload.
2. Collect qualitative evidence: five short user conversations and a scan of support messages about uploading.
3. List possible causes: file size limits, unclear format rules, or no reason to upload straight away.
4. Prioritise three candidate fixes using reach, impact, confidence and effort.
5. Write a one-page PRD for the top option with a success metric, such as an increase in first-note rate, and a review date.

Deliverable: a prioritised list and a one-page requirement document that engineers can estimate.

What the example shows

The analyst’s output tells the team where to look. The PM’s output tells the team what to do. Each depends on the other, which is why many product teams ask interns in both roles to review each other’s work.

Tools to practise before applying

• For PM: a free docs tool for writing PRDs, a Kanban board for backlog practice, and any free prototyping tool to read wireframes.
• For PA: Google Sheets with a public dataset, a free SQL practice environment, and a free dashboard tool.
• For both: pick a product you use daily and write a two-page teardown covering the user, the problem, three metrics and one improvement idea.

Portfolio pieces that prove each skill

Where to try the work first

If you want low-risk practice with product tasks before applying to larger programmes, CareerSwami offers a free two-week online internship with a free offer letter and a free completion certificate after successful completion, across 26 tracks. Whichever route you take, produce a work sample you can show, since a document or dashboard says more than a certificate line.

Miranda House and product internships: using the Placement Cell for PM or analyst work

Miranda House describes itself as a women’s college under the University of Delhi, and the Placement Cell brochure (2024-25 edition) gives its founding year as 1948. For a student weighing a product management role against a product analyst role, the most useful starting point is the college’s own career machinery rather than a generic job board.

The college runs a Placement Cell microsite with sections including The Process, Past Recruiters, Archive and a student login to a career advancement portal. Past Recruiters is worth reading before applying anywhere: look for companies with product, analytics or technology teams, then check whether they hired interns or full-time staff. The brochure also says the cell arranges jobs and internship opportunities, extension lectures and exam guidance. In practice, that makes the cell the first place to ask which product-style openings, if any, reach the college.

The same brochure reports that its Chrysalis 6.0 job and internship fair was held offline on 29 April 2024. That is a 2024 event, so treat it only as a sign that such fairs happen, and check the portal for current dates. The brochure also states a One Student One Offer policy (shown as an excerpt). If you apply through the cell, ask how this affects accepting an outside internship alongside a campus offer.

On curriculum, the brochure’s course list covers B.A. Programme, B.El.Ed, B.A. (Hons), B.Sc. (Hons) in Botany, Chemistry, Mathematics, Physics and Zoology, and the B.Sc. Programme in Physical and Life Sciences. It lists no computer science or MBA programme. Most students therefore build product skills such as SQL, spreadsheets, user research and writing alongside their degree, and a role-fit scorecard helps decide which path to test first. Internship and credit rules were not confirmed here and appear to follow University of Delhi documents, so check them before assuming anything counts toward your degree. The Academic Calendar page is the place to look for break dates.

Checks before you commit to a product internship

• Log in to the Placement Cell portal and note whether product, analytics or business-analyst internships are listed, and who the contact is.
• Ask the cell whether outside internships must be registered, and how the One Student One Offer policy applies to internships.
• Ask your department which University of Delhi internship or skill-enhancement scheme applies to your course, and request the current document.
• Open the Academic Calendar and plan a two-week trial around exams and internal assessments.
• Ask what certificate or letter format is accepted, and who signs a permission letter if needed.
• Check the dates of the next job and internship fair on the portal rather than relying on the 2024 date.

A two-week plan for testing a role

Use this plan to try a role before committing. Each day takes around one to two hours.

1. Days 1-2: choose a product and read its public reviews. Write down the three most common complaints.
2. Days 3-4: for PM, write a problem statement. For PA, define five metrics for the product and how each would be counted.
3. Days 5-7: for PM, run a competitor comparison. For PA, load a public dataset and build a funnel or cohort table.
4. Days 8-10: for PM, prioritise three solutions. For PA, draft a dashboard with a clear takeaway.
5. Days 11-12: write the one-page PRD (PM) or the one-page insight note (PA).
6. Day 13: ask a friend or senior to read it cold and tell you what is unclear.
7. Day 14: revise, save it as a PDF, and add it to your portfolio.

Notice which days felt energising and which dragged. That reaction is better evidence than any scorecard.

Reading internship listings critically

Titles are unreliable, so scan the responsibilities section for these signals.

• PM signals: “write requirements”, “prioritise”, “coordinate with engineering and design”, “user research”, “roadmap”.
• PA signals: “SQL”, “dashboards”, “A/B test analysis”, “cohort”, “reporting”, “data cleaning”.
• Mixed listings: “product operations” or “associate” roles often combine both. Ask which tasks take most of the week.
• Warning signs for either role: no named manager, no description of deliverables, or a request for a fee to take part.

Questions worth asking before you accept

1. Who will review my work, and how often?
2. What will I deliver by the end, and who will read it?
3. Which tools will I get access to?
4. Will I work with real data or only sample data?
5. Will I receive written feedback or a reference at the end?

Common mistakes in each path

Product management

• Writing solutions before defining the problem.
• Listing features without saying who benefits.
• Setting goals with no number and no date.
• Prioritising by personal taste rather than a stated method.

Product analysis

• Using a metric without defining it.
• Showing a chart with no conclusion.
• Ignoring small sample sizes when comparing groups.
• Treating a correlation as proof of cause.

Frequently Asked Questions

Do I need to know coding for a product management internship?

No. You need to understand how software is built at a conceptual level, such as what an API or database does, but you are not expected to write production code. Basic SQL is a useful extra because it lets you check numbers yourself.

Is a product analyst internship harder to get than a PM internship?

Not necessarily. Analyst roles usually screen for concrete skills such as SQL and spreadsheets, which you can demonstrate with a small project. PM roles screen more on structured thinking and writing, which are harder to test but also showable through a PRD or teardown.

Can I move from product analyst to product manager later?

Yes, this is a common route, since analysts develop a strong sense of what moves metrics. The move usually requires showing that you can write requirements, work with engineers and make trade-offs, so seek out those tasks during the internship.

Which one suits a non-technical background?

Both can. The PM path leans on writing, research and communication. The analyst path needs numerical comfort, which can be built with a few weeks of practice in spreadsheets and basic SQL.

How many tools should I learn before applying?

Fewer than you might think. For PM, one docs tool and one board tool are enough. For analysis, spreadsheets plus basic SQL cover most beginner tasks. Depth in two tools beats surface familiarity with ten.

As a student writing a first PRD for a PM internship, what should it contain?

Keep it to one page: the problem, the target user, the evidence, the proposed solution, what is out of scope, the success metric with a target, and open questions. Brevity shows that you can prioritise.

Will a short online internship help my profile?

It helps if you finish with a real work sample and can explain your choices. A short programme such as the free two-week internship mentioned above gives a structured way to produce one, but it is your documented work and reasoning that interviewers will discuss.

How do I know whether my college accepts an internship for credit?

Credit rules are set by your programme and university, so ask your department in writing and keep the reply. Until you have that confirmation, treat any internship as extra experience and not as a degree requirement.

Related Product Management guides

• Product Management Internship Guide for University of Delhi Students: Skills and Case Preparation
• Product Management Internship Portfolio for University of Mumbai Students: Writing a Product Case Study
• Evaluating a Product Management Internship Offer: A Checklist for Savitribai Phule Pune University Students
• All Product Management internship guides