Resumes and cover letters
PM resume for students and career switchers
In this lesson6 sections
An unofficial lesson drawing on the methods in the Resumes 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
A student or career switcher has no product manager title to point to, so a PM resume has to show product work some other way, mostly through things you built and the people who used them. This lesson works through one student's page line by line, then shows what changes when you're switching careers.
We'll follow Maya, the economics student with a computer science minor from becoming a PM as a student, as she applies for new-grad PM roles in her final year. Her first draft has three problems. The first thing under her education is a block of skills with nothing behind them. Her software engineering internship reads like a job ad. And the whole thing runs to two pages.
Lead with proof, including what you left off
On a student's page, education usually comes first. The space right under it belongs to whatever best shows you can do product work. No rule settles what qualifies. If an item would leave a recruiter more curious about you or more sure of you, it has a claim on that space.
Before you polish a single bullet, look for what's missing. Two questions turn up most of it. Has anyone else used something you made or set up? And what have you kept at for months because you wanted to? It might be a how-to guide that newer students still pass around, or a newsletter they've kept sending for a year.
Maya gave the space under her education to her skills block, and her best evidence barely showed. The sign-up app she built for her university's pickup soccer club, which 140 students use every week, appeared only as two words inside the block: React and SQL. She planned to bring it up in interviews, but she thought of a resume as a record of jobs and grades, and nobody had paid her for the app.
That isn't a reason to leave it out. Work earns a line by what it shows about you, not by who paid for it.
To practise this step out loud, try Presenting a Strength Your Resume Leaves Out, Backed by Evidence.
Write a project the way you'd write a job
After paid work, projects are the strongest evidence a PM resume can carry, and a student has little paid work. Give each project a line or two that covers four things: what the project does, your part in it, who it serves, and whether it worked.
People skip the last one most. Use the measure the project already has. For Maya's app, that's the 140 students who use it every week. A small number you can explain beats a big one you can't.
Here is the skills block from Maya's draft:
Languages: Python, SQL, JavaScript, React, HTML/CSS
Tools: Figma, Excel, PowerPoint, Jira, Notion
Strengths: product thinking, leadership, communication, teamwork, problem solving
The rewrite drops the block and lets two projects make the case. The second came later, from the gap step below.
Built the soccer club's game sign-up app alone, replacing a group chat; 140 students use it weekly.
Built a shift-swap prototype for student jobs with an AI coding tool; after 5 of 8 testers quit at one step, replaced the step, and all 6 new testers finished a swap in under a minute.
Both lines cover all four. The second also shows a decision she made because of what testers did, which is about as close to product work as a student can get. Testing the change on new people makes the second number hold up. The first fits on one line, the target in writing PM resume bullets, and neither runs past two. The step itself (connecting a calendar, swapped for a plain list of open shifts) can wait for the interview.
Nobody asked Maya to build the soccer app, and that answers a doubt every junior PM resume raises: will you start something on your own? Already working full time? A side project or volunteer effort you led, with results, shows initiative your job title can't.
She keeps one short skills line under the projects: SQL and JavaScript, the two she used to build and measure the app. Screening software matches those words to a posting, and the projects back them. "Product thinking" and "teamwork" are gone. Anyone can type them.
A company you started that later closed goes on too, written like any other project, with the same four things.
Say what each job was for
Engineering internships usually get written as tasks. A PM reader wants to know who the work was for and what changed for them. Here's Maya's draft:
Software Engineering Intern. Fixed bugs in the route-planning web app. Attended daily standups and sprint planning. Wrote unit tests.
And the rewrite:
Cut load time from 9 seconds to 2 on the screen dispatchers at 60 customer depots open every morning.
Watched two dispatchers work and found each lost about 25 minutes a day retyping emailed orders; proposed an email import, which the team shipped before the internship ended.
The first line names the users, the scale and why speed mattered to them. The second shows her reaching past her own ticket queue toward the PM's job, by watching people use the product and putting a number on what she saw. Standups and unit tests went; every intern does those.
Engineers moving into PM need this habit most: name the user or business reason each thing you built existed. The rest of that move is in software engineer to PM. And write only numbers you can explain, since an interviewer may well ask how Maya measured the 9 seconds or the 25 minutes.
Her campus library job, listed next, gets the same question: who was the work for? Since September she has made the weekly desk schedule for nine student assistants and found cover whenever someone drops a shift, and the desk hasn't missed an opening hour all term. Nobody reports to her, but nine people's weeks run on her schedule. That one line answers a second doubt about any junior PM resume: has anyone's work ever depended on you? It needs no title.
Keep only what no other line says
To get from two pages to one, the right length for a student, Maya read each line and tried to finish one sentence: "This tells a PM recruiter that I..." Lines she couldn't finish, or that another line finished better, went.
| Line in her draft | "This tells a PM recruiter that I..." | Decision |
|---|---|---|
| Twelve courses listed by name | ...took the courses my major requires | Cut; the databases course shows in her SQL skill, which the app backs up |
| Library desk assistant | ...make the schedule nine assistants work from | Kept, one line; no other line shows people relying on her |
| Lantern, Project Lead | ...built a food bank's volunteer sign-up page, which took 210 sign-ups in its first month | Kept, with that result in the line |
| Member, Economics Society | ...joined a club | Cut |
A course you take on your own faces the same sentence. Certificates are so common now that a course name alone finishes it weakly; name something you made in it, like a graded project or a working app.
With the skills block gone too, the page runs in this order: education, the two projects, the short skills line, the internship, the library job, then Lantern. It fits on one page.
Run the same test each year after you graduate. Maya's app will hold its place until her work as a PM shows the same things better. A GPA usually goes sooner: some new-grad PM applications ask for it, but many tech employers stop weighing it once you have a few years of experience.
Anything you cut can still come up in an interview. To practise bringing one in, try Going Beyond the Resume: A Personal Story That Shows How You Work as a PM.
Close a gap with a project, not a phrase
Read your page against the PM jobs you want and look for an expectation nothing on it backs up. Better wording won't fill that gap. A real project or role will, and then it goes on the page.
That's where Maya's second project came from. This fall she read her page against twenty new-grad PM postings. Most asked for experience testing ideas with users, and nothing on her page showed it: the soccer app had gone straight from idea to full build. So she picked a problem she dealt with every week, desk shifts that fell through when a swap got lost in a group text. She spent two weekends building a swap prototype with an AI coding tool, watched student workers from the library and two dining halls try it, and changed it when most of the first group got stuck.
You no longer need to write code for this. AI coding assistants and no-code tools let a non-engineer ship a working prototype in a few weekends, and one that real people have used shows a real interest in technology. Paying a freelancer to build what you designed counts too, if you say who built it. Name the tool in the line, as Maya did, because interviewers ask how a project was built. For picking a project worth the time, see PM side projects.
To practise talking about a build like this, try Present a Self-Built AI Project and the Product Decisions It Required.
The career switcher's version
Everything above applies to a career change, with two additions.
First, name the path in one line at the top of the page. A recruiter who sees six years of teaching on a PM application has to guess why. Tell them, and tie the line to one fact they can check.
Sam, a middle school math teacher, wants associate PM roles at learning-software companies. His summary line:
Moving from teaching into product management for learning software. Six years teaching middle school math, the last two also as the department's contact with its software vendors.
The vendor role appears nowhere else on the page. A summary that repeats the top bullet wastes the one line every reader sees.
Second, describe your earlier work by the decisions you made and the numbers they moved. Sam's draft said:
Taught algebra and geometry to 150 students a year; planned lessons, set and graded homework, met with parents.
His rewrite:
Ran a four-week trial of two homework apps in 6 classes; recommended the one with the higher on-time homework rate (78% against 64%), adopted for all 14 classes.
Cut parents' "what's due" emails from about 20 a week to 3 with a Friday digest in the school's app.
Neither line calls Sam a product manager, and he keeps his real title: an interviewer will ask about any title that stretches the truth. The work reads as product work anyway. He compared two options on a number and acted on what he found. For more ways to find the product work inside a non-PM job, see Product Manager Resume with No PM Experience, and for planning the move itself, how to become a product manager from another role.
Switchers are almost always asked to explain the path out loud, and the spoken version should agree with the line at the top of the page. To practise it, try Explaining Your Path Into Product Management and What Draws You to the Role.