Skip to content
中文Sign in

New-grad PM: from listing features to clarifying first

Example

In round one he answered the product design question with a list of eight features and got cut off. After the debrief he learned to spend thirty seconds clarifying first, and the same kind of question went much better in round two

WhoGraduating this year, two product internships: internal tools at a content community, and a bit of everything at a startup

Example scenario: written around a typical user. People, companies and numbers are made up to show how the product works. Not a real student.

01

Background

He prepared by reading other people's interview notes. His self-introduction was polished and walked from university through both internships.

The trouble: new-grad interviewers don't have much to ask about, so whatever you mention, they dig into. He was handing the interviewer full control over the topics.

02

The dossier: what went in

He created a dossier for each of three companies, sharing one resume

ResumeTwo internships. The first says "independently owned the ops console redesign"
Job descriptionNew-grad PM at an internet company. "Design product solutions starting from user needs"
NotesHR said round one is forty minutes with one product design question
03

Key calls in the prep

The two most useful points in the prep weren't answers. They were about what this round actually tests.

  1. Your intro hands the interviewer their follow-up threads

    Reading your resume in order lets them pick anything. Lead with the internship you can go deepest on, light it up with one result, and the follow-ups land where you've prepared.

  2. Design questions test how you break down a problem, not how many features you know

    The JD says "starting from user needs", so a design question is almost certain. Clarify the user, the situation and the metric first, then give a solution with trade-offs, then how you'd measure it.

  3. "Independently owned" will be probed

    When an intern writes that, interviewers ask which decisions were theirs. Prepare three levels: what changed, why, and how you knew it worked.

04

What happened in the interview

The reworked intro worked. The interviewer spent a long stretch on the ops console and he handled all of it.

The design question was "design a second-hand marketplace feature for college students". Nervous, he listed eight features and was cut off at the fifth: "Which one matters most, and why?" He didn't have an answer.

05

What the debrief said

The debrief first confirmed the intro change worked, then took the design question apart.

QuestionSelf-introduction Strong

Next timeThe thread he planted got picked up, and the follow-ups landed on prepared ground.

QuestionMarketplace feature design Lost points

Next timeBeing cut off means you're drifting. Next time, ask first whether the goal is more transactions or more trust, pick one situation, go deep, and say why it comes first.

QuestionAfter being interrupted Weak

Next timeHe kept going through the remaining features. When interrupted, close in one sentence and answer the new question.

06

What changed for the next round

"Lists features on design questions" went into his account memory. The prep for the other two companies put it at the top.

  1. Practice a fixed opener: "Let me confirm the goal and the user first", then pick a single situation
  2. Lead with the conclusion, then expand, and keep it short
  3. Swap the question about overtime for "what does doing well look like in the first three months"

Keep reading

Try it with your own resume and JD

Create a job dossier and get prep for your next round