Getting into PM

Becoming a PM as a student, new grad or MBA

Lesson 36 of 45~7 min read
In this lesson6 sections

An unofficial lesson drawing on the methods in the Getting the Right Experience chapter of Cracking the PM Interview by Gayle Laakmann McDowell and Jackie Bavaro (2014). PracHub is not affiliated with the authors or publisher. Buy the book

You can become a product manager straight out of school, but the door is narrow: a few new-grad programs and entry-level jobs, with far more applicants than seats. This lesson covers what students, new grads and MBA candidates need to show, and how to build that proof before you apply.

We'll follow one invented student the whole way. Maya studies economics with a minor in computer science, and has two years left before she graduates.

Starting in PM straight from school

You don't need two years in another job to earn a PM title. Companies hire product managers out of college.

The hard part is the count. The well-known associate PM programs take a small share of applicants, and new-grad PM hiring has tightened in recent years. Apply, but don't make them the whole plan.

Interviewers often start by asking why you want a job you haven't done yet. A student's answer rings true when it names a time you already did a small piece of the job and wanted more. For Maya, that's deciding what her club app (below) should do next, which turned out to interest her more than the code. Her line closes her walkthrough near the end. To practise that question, try Explaining Your Motivation for Product Management and the Parts of the Job You Enjoy Most.

Comparing new-grad PM programs

Google's APM program is the best known, and it still hires university graduates. LinkedIn replaced its APM program with an Associate Product Builder role that mixes product, design and engineering and asks for a short demo of something you built. Meta's rotational RPM program now asks for about four years of related experience, so for a student it's a later option, not a route out of school. Our comparison of associate product manager programs compares three current programs on rotations and length, and shows how to check eligibility on each live posting. Some windows close a few weeks after opening.

Details change yearly, so compare programs on the same rows, as Maya did with three invented ones:

Program AProgram BProgram C
First roleOne feature on a big productChanges each rotationA small product of your own
Time to full PM title2 years18 months12 months

Maya wants to own something whole early, so C comes first for her, then A, where she keeps one feature, then B. Seats are few, so she applies to all three, plus about 20 entry-level PM openings at mid-size companies and a few product analyst roles where PMs started as analysts. The table also gives her a specific answer to "why this program?" and settles the choice if two offers arrive.

The MBA route: price it before you go

If Maya's first job isn't in PM, she may weigh business school later. Her test starts before she looks at any school: she writes down what she'd want from one, then asks of each item whether a job could give it to her for less.

The PM title fails that test. Some large companies recruit PMs from MBA programs, but you don't need an MBA: an internal move or an entry-level role gets you to PM for far less. Before you count on the degree, check what the PMs on your target teams studied.

Each item has to beat the price. Harvard Business School's published budget for a single student in 2026-27 is $130,318 for the nine-month year, tuition, housing and food included, so two years comes to more than $260,000. Add the salary she gives up, say $120,000 a year less what a summer internship pays, and the total comes close to half a million dollars.

An item that passes is one a job can't give her, such as training in one question: which number are we trying to move, and is it worth the cost? Her answer to "What would you change?" below is a small version of it.

Spend each term on your weakest evidence

Maya's first evidence is her club app. The soccer club organized games in a 400-person group chat, where sign-ups got buried and games fell apart. She built a small web app where each game shows who's in and how many more players it needs. By mid-term, 140 students use it every week.

With AI coding tools, an app like this takes a weekend to build, so the app alone proves little. Interviewers ask what you decided and what happened once people used it. Maya logs sign-ups, no-shows and cancelled games from the first week, and that log becomes her best interview answer. PM side projects covers choosing and presenting a project.

Once the app is live, she checks what her evidence shows. The app and its log cover the product half. Her technical half rests on a minor, which reads thinner than a major at the screen. Her rule: find the weakest part and spend the next term on it.

The rule settles her summer. She has two offers: engineering at a mid-size logistics software company, and PM at a 30-person startup. A result you produced at work is the most believable proof a student has, so either beats a summer of classes. Return-offer rates vary by company and year, so ask the recruiter. The PM role would add to her strongest half, the engineering role to her weakest. She takes engineering and asks to sit in on two planning meetings a month. Asked why, she says:

"My product evidence was already the strong part. What a recruiter might doubt was whether I could hold my own with engineers, so I spent the summer as one."

Two answers to have ready

Most early-career interviews open with a walk through your background. Students tend to tell it in date order, every club included. Lead instead with what you built and what happened, add a line each on your technical base and your internship, and close on why this role. With that little to cover, about a minute is enough, like the short version in our lesson on tell me about yourself. Maya's version:

"Last fall I built a sign-up app for our pickup soccer club, and 140 students now use it every week. I study economics with a computer science minor, and this summer I interned as a software engineer at a logistics company, where I shipped a fix to the route-planning screen and sat in on the PMs' planning meetings. What I liked most was deciding what the app should do next and checking whether it worked. That's why I'm applying to this program: new PMs here own a small product in their first year."

To practise this step, try PM Interview Opener: Presenting Your Background and Career Story and Walk Through Your Background and Motivation.

The second comes when an interviewer turns your project into a product question: "What would you change about it?" Answer from your usage data. Maya's log after a year:

  • About 18 games a week get posted, and a game needs at least 10 players to go ahead.

  • About 5 a week are cancelled for falling short, nearly all on weekday mornings, and roughly 30 players a week had signed up for those games.

  • Weekday-morning players come back the next week 75% of the time when their game went ahead, and 45% when it was cancelled.

Players keep asking for a group chat and a team picker, but the log points at cancelled games. Maya compares only weekday-morning players, who might return less often anyway: the 80% return rate across all games would overstate the loss. Like for like, she loses about 9 players a week (30 × 30%).

"I'd go after cancelled games. They cost me about 9 players a week who would otherwise come back. I'd close sign-ups at 9pm the night before, which gives the app time to merge two short morning games into one and tell everyone before they set out. I'd judge it by how many players return the next week. Some people will lose the time slot they wanted, so I'd also check that merged games really reach 10 players."

Interviewers at AI companies often add a third question: what draws you to their field. Maya's link is small but her own: she had a language model sort the free-text reasons players give for dropping out, then checked 50 of its labels by hand and found it filed injuries under schedule clashes. To practise it, try Describing Your Personal Interest in AI for a PM Role at an AI Company.

All motivation and fit questions

Recruiting events: leave with one name

Many fairs now run online, on platforms like Handshake, and most applications go through screened portals, so a fair is one channel among several. Go with one goal: leave with one named person who remembers you and a reason to write.

At her virtual event, with 10-minute video slots, she spent hers with a PM at a payments startup. She left with an OK to follow up, sent three sentences and a link the next morning, and two weeks later the PM referred her for the company's new-grad PM opening.