Getting into PM
How to become a product manager from another role
In this lesson7 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
Moving into product management from design, analytics, sales or marketing comes down to evidence: product work you have already done in your current job, with a result you can name. Here is how to build that proof on purpose, then use it inside your company or outside it. Engineers have their own route in software engineer to PM.
We'll follow Lena, a product designer at an invented pet-pharmacy subscription app. Prescription items can't ship until the pet's vet approves them. Her next project is a checkout redesign.
The question a 73% result gets
The PM's goal was checkout conversion, the share of started checkouts that end in an order, from 70% to 74%. It reached 73%. An interviewer will ask what produced three points and what kept the fourth away.
Lena could answer that for this project only. On earlier ones she had moved on before launch, so she could name almost none of their results. This time she had asked the PM, before the work began, which number would judge it, and stayed until it came in. Make that your habit. With no PM record to check, an interviewer reads your current job for stand-ins: judgment, comfort with data, bringing people round, getting things done. A project you left before launch shows none of them.
To practise this step, try Describe your background and top PM skills: tell your background as calls you made and projects you finished.
Where the fourth point went
To say what produced three points, Lena needed conversion by phone type, and the analysts had a three-week queue. So she got read access to the reporting database and learned enough SQL (conditional counts and rates covers the pattern) to compare the four weeks either side of the March 2 launch:
SELECT device,
started_at >= DATE '2026-03-02' AS after_launch,
round(100.0 * count(order_id) / count(*), 1) AS conversion_pct
FROM checkout_sessions
WHERE started_at >= DATE '2026-02-02'
AND started_at < DATE '2026-03-30'
GROUP BY 1, 2;
With 9,000 checkouts started per phone type per period, iPhone went from 70% to 75% and Android from 70% to 71%, so 73% overall. The same weeks a year earlier were flat, so it wasn't the season.
The gap traced back to scope. The redesign had six parts and the quarter about seven engineer-weeks. Lena ranked the parts with the PM, and four fit, among them a one-page checkout, a vet approval status and a phone-wallet payment. The wallet fit on iPhone only, since the Android version needed an extra week.
To practise this step, try Behavioral PM: Describe How You Analyzed Data to Reach a Decision and Its Outcome and Weighing Usage Metrics Against User Research When Making Product Decisions.
Behavioral PM: Describe How You Analyzed Data to Reach a Decision and Its Outcome
A behavioral product manager prompt asking for a specific time the candidate analyzed data to reach a conclusion.
Weighing Usage Metrics Against User Research When Making Product Decisions
A product manager interview question on how to weigh quantitative evidence, such as usage metrics and experiment results, against qualitative...
Trading the timeline for one line
The vet approval status was in the plan because about a third of "where is my order?" tickets were prescription orders stuck waiting on a vet, with nothing in the app saying so. Lena designed it as a three-stage timeline. Mid-quarter, Sam, the checkout engineer, found the pharmacy system reports only "approved" or "not yet", so the timeline would take two more weeks.
Lena took one line of text that day: "Waiting for your vet to approve this." She disliked it. But it fit the time planned for the status and did the job it was there for, while the timeline would have cost two more for a nicer look. It shipped on time, and prescription "where is my order?" tickets fell from 160 in the six weeks before launch to 70 in the six after. The habit she kept: before ranking a design, ask what other system it touches.
Many PM listings still ask for a computer science degree, and AI and platform roles ask more, such as reading API documentation or judging a model's test results. What a hiring manager wants to know is whether engineers will work with you. Sam changed her plan and she changed his, so he is who Lena would ask to vouch for her.
To practise this step, try Grammarly PM Behavioral: Negotiating a Product Trade-off Alongside Engineers and How a PM earns engineers' trust: what an engineering team needs from its product partner.
Grammarly PM Behavioral: Negotiating a Product Trade-off Alongside Engineers
A behavioral question for a Grammarly product manager role: describe a time you worked with engineers to settle a trade-off.
How a PM earns engineers' trust: what an engineering team needs from its product partner
A behavioral product manager question about what engineering teams need and expect from their PM.
The answer, from cause to next step
Missing a goal is fine if you can say why. Put together, Lena's answer to the 73% question:
"I designed our checkout and ranked its parts with the PM. When the vet-approval timeline turned out to cost two more weeks, I shipped a one-line status instead, and prescription order-status tickets fell from 160 to 70. Conversion rose from 70% to 73% against a goal of 74%. My own query showed iPhone up five points and Android one. The wallet shipped on iPhone only. I showed the roadmap meeting the split, and the Android wallet is first next quarter."
To practise telling a project by its result, try Walking Through a Past Project You Owned, From Problem to Measured Result and Behavioral: walk through a product you owned that failed and what you learned.
Walking Through a Past Project You Owned, From Problem to Measured Result
A behavioral product manager interview question asking you to walk through one project from your past work.
Behavioral: walk through a product you owned that failed and what you learned
A behavioral product manager question asking the candidate to describe a product or feature they worked on that failed.
Moving inside: the vet-wait email
Lena's vet-wait email cut prescription "where is my order?" tickets from 70 to 45 over six weeks, nearly all of the drop from orders it reached. Nobody had assigned it.
Orders waiting on a vet over 48 hours still drove many of those tickets, so she pitched an email to those customers with their vet's phone number. Engineering had no room, so she borrowed marketing's receipt tool, fed it the pharmacy team's daily list of waiting orders, and wrote the wording with the support lead. Finding a way when the usual queue says no is what interviewers call scrappy. She told the checkout PM first, so it read as help, not a grab at his area. Leading without authority covers the skill once you have the title.
That email is what a sponsor can name. Lena asked the checkout PM to be hers: someone with standing who will say, where moves are discussed, what they watched you do. Hand them the line: "You saw me trade the vet timeline for one line, pull the phone-type split and ship the vet-wait email."
She also asked the head of product, who would approve a move:
"I want to move into product management within a year. What would you need to see from me?"
He named a revenue call, which the email doesn't show.
Lena's gap audit
The revenue call was one gap. To find the rest, Lena set each PM skill beside what her design job already proves, and named one project or duty to close each gap:
| PM skill | What she can show | Gap | How she'll close it |
|---|---|---|---|
| Business sense | Little | A revenue call, which the head of product asked for | Put a revenue figure on the Android wallet |
| Leading without a title | The vet-wait email, bug triage while the PM was on leave | Nothing large yet | Run the backlog of the pharmacists' tool, which has never had a PM, for a quarter |
| Owning a number | Explained the PM's 70% to 73% result | Has never owned a goal herself | Own the Android wallet's goal |
| Technical sense | Traded the vet timeline for one line; a weekend prototype | The systems behind the app | Have Sam walk her through the order system |
Prefer projects that also help your team, so your manager has a reason to say yes.
Other backgrounds usually come up short on a different row:
| You come from | Row it usually lacks | What closes it |
|---|---|---|
| Sales, such as signing up vet clinics | Business sense | Size the demand behind one big customer's request |
| Analytics | Owning a number | Own a result, as Priya, an analyst there, did: she proposed a "pause one month" option for subscribers who skip a delivery, agreed a target with the PM and tracked cancellations after launch. See business analyst to product manager |
| Marketing | Technical sense | Time with engineers, learning what each change costs |
Expect interviewers to press hardest on the technical row. Lena built a reorder-reminder app over a weekend with an AI coding assistant. A side project can fill a gap your job can't, but with AI help the app alone proves little. What impressed an engineer was her explaining where the reminder dates lived and why it broke for two pets on different schedules.
To practise talking about your technical depth, try PM technical depth: rating yourself, a technical decision you shaped, and a system diagram.
The outside route
Applying elsewhere, Lena would swap "designed the checkout" for "ranked checkout scope with the PM and owned the conversion analysis". The resume lesson for career switchers covers that wording. Automated screening filters out most applications, so a referral counts, best from someone who watched the checkout work. If Sam moves to another company, his word there carries the trade-off he saw her make.
Her LinkedIn should read the same way. The headline can say "Product designer: checkout scope and conversion analysis", and the latest role can name the 70% to 73% result and the one-line vet status that cut prescription order-status tickets from 160 to 70. Posts earn their time mainly with startups, whose interviewers may read them before the call.