The PM role

How PM jobs differ by company and product

Lesson 41 of 45~8 min read
In this lesson7 sections

An unofficial lesson drawing on the methods in the Companies 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

The same product manager title can mean very different work from one company to the next, and even between two teams in one company. Knowing which version a role is helps you choose where to apply and answer specifically when asked why you want the job.

Cracking the PM Interview compares real employers, but its 2014 examples have aged, so this lesson invents its companies.

Maya has spent three years as one of five PMs on a consumer subscription app's growth team, shipping a test most weeks. She was a data analyst before that and has no engineering degree. One of her two postings is at a 300-person fintech whose software matches a mid-sized company's incoming payments to the invoices it sent, so finance can close the month. The other is on the notifications platform of a large food-delivery app: the internal service 40 product teams use to message customers and couriers.

What the week would hold

Every PM answers for results, but postings rarely say what fills the week, so read them for clues. The lines that changed Maya's choice:

What the posting saysPosting
"Talk every week with controllers and receivables teams"Fintech
"Own the roadmap with the head of product"Fintech
"Monthly release after change review"Fintech
"Your customers are the product teams that send messages"Platform
"Daily deploys behind feature flags"Platform
"Shape the roadmap within yearly company priorities"Platform

The weekly calls are the fintech's draw: what controllers and receivables specialists say would decide most of what gets built, and she'd turn it into a direction to argue for with the head of product. She'd be the only PM, with 12 engineers, a designer and a compliance lead, so every request from sales, support and compliance would reach her, and engineering time is what she'd ration. The monthly release is what worries her. More on decoding a posting: how to read a product manager job description before applying.

To practise rationing scarce engineering time, try Allocating One Engineer-Week Among Conflicting Enterprise Customer Asks. To practise describing your own scope, try Why this role and team scope?

The platform team lists three PMs, 24 engineers and no designer, and its customers are the product teams that send messages. So her first month would go to engineers' problems, not screens: she'd write how the API behaves, sit in API reviews and draft migration plans for 40 teams that each want something different on their own schedules. Which asks get done is mostly settled by the yearly priorities. To move them, she'd take an idea to a director with numbers behind it, the way her growth ideas got built only once she tied them to the sign-up numbers the company watched weekly.

The service is also mature, and every order the company takes depends on it. The risk is a year of small fixes, such as showing teams which messages arrived, that never add up to anything a customer notices.

To practise improving a product that has been out for years, try Improving a Mature Tax-Filing Product: TurboTax Pro Strategy.

Her first quarter at the fintech

The first hard decision would likely come out of a weekly customer call: a large customer asks for a matching rule built just for them. The person who signs is the controller, who answers to auditors; the person who uses it is a receivables specialist matching payments all day. Maya has one real story for this job, reconciling subscription revenue with finance every month-end as an analyst, so she knows a version of the controller's work. She'd weigh that customer's revenue against the plan for everyone else. See B2B product manager interview questions.

To practise the pull between big customers, try Prioritizing conflicting feature requests from two strategic customers.

Whatever she decides, the rule then meets the release process, where her testing habit stops working. Her growth team shipped on Tuesday, read the A/B test on Friday, and shipped again. Here, customers' auditors watch every change to how the software matches payments, so none is tried on a random half of customers. Maya would have to learn before release instead of after: run the new rule against last month's payments, compare its answers with what accountants did, and try it with three customers who agree to see early versions. Then the compliance lead and the change review approve a written description. With monthly releases, a change can take a quarter from idea to customers. The fintech is remote-first across the US and Europe, so approvals happen in documents, which suits her habit of deciding in writing; lining up approvers is the part she'd have to get better at. In regulated fields such as finance, health and insurance, expect a compliance or legal partner in the core team and some experiments off limits.

The quarter's biggest call would be the suggested matches, for payments the matching rules can't pair. Change review will ask how often a guess is wrong, so before release she'd set the bar: a set of real test cases, often called evals, and the error rate customers accept. Ordinary tests miss too much, since a model can answer the same input differently, sometimes confidently wrong. Whether controllers will trust a machine's guess at all is still open, so her first release would be suggestions a specialist confirms by hand, on one kind of payment, for a few customers. She could prototype it with AI coding tools before asking engineers for time. See AI product manager interview questions.

Her first quarter on the platform

Her Tuesday-to-Friday rhythm fits here: daily deploys behind feature flags, fixes out the same afternoon, and each change reaching one team before the rest. What changes is reach. When a notification change goes bad late in the day, it can stop 40 teams' customers from hearing about their orders, and she may have minutes to decide whether to roll it back.

The API reviews would be harder: the posting wants a strong technical background and someone who reviews API designs, depth Maya doesn't have. The team is in the office three days a week, so those calls get settled in the room, not in her documents. Apply where your background is the profile they prefer. Preferences change, so check current postings and PracHub's reported questions for Google, Meta, Amazon, Microsoft, Apple, Uber and Airbnb.

What she could not live with

Judge the pace from evidence, not the careers page. Two of Maya's platform interviewers mentioned launch weekends, and the delivery company reorganized recently with talk of speed. The fintech's people describe a steady pace. Maya knows from her own launch seasons that a monthly crunch wears her down. For ways to ask, see questions that help you assess a role.

To practise naming the conditions that would make you turn a job down, try Explaining the Job Conditions That Would Make You Turn Down a PayPal PM Role.

Scoring the two roles

Maya scores each role's fit for her from 1 to 5:

Her question about this postingFintechNotifications platform
What happens to my Tuesday-to-Friday testing?2: monthly releases; it moves before release3: daily deploys fit, but 40 teams ride on each change
Is there an AI feature to own, and can I decide in writing?4: suggested matches; remote-first2: no AI work, office three days
Does my month-end story count here?3: a version of the controller's work2: they want technical depth she lacks
Could I live with a monthly crunch?4: steady pace2: launch weekends
Total139

Read the rows before the total: one score you can't live with outweighs several good ones. The fintech's low row is her testing habit, and she has a plan for it. The platform's three low rows, on AI and office days, her background and the pace, are ones effort changes less.

What she still has to ask

Her least certain rows become questions. For the fintech:

  • "Before a matching change reaches customers, what happens, and how long does it take?"

  • "Have any customers agreed to try early versions?"

  • "When a large customer asks for something off the roadmap, who makes the call?"

For the platform team:

  • "How do the three PMs split the platform, and who decides when two product teams want opposite things?"

  • "Does a PM here review API designs or write them?"

  • "What did the last launch weekend look like, and how often does one happen?"

Two checks fit any role. Where a posting doesn't say who sets direction, ask:

"Where did the last big project on this team come from?"

Team counts move with layoffs, reorganizations and AI coding tools, in both directions, so confirm the real ones too.

Turning the scores into your answer

The same questions make your answer to "why this company?" specific: how this team works, something you've done that fits it, and what you'd have to learn. Maya, to the fintech's hiring manager:

"What draws me here is owning a whole product and talking every week with the people who use it. As an analyst I reconciled subscription revenue with our finance team every month-end, so I know a version of their job. The part I'd have to learn is your release pace, so I'd move my testing earlier, running new matching rules against past payments and trying them with a few customers first."

To practise a why-this-role answer for one particular team, try Making a Specific Case for Why You Want a Product Manager Role at Block.

Maya named her doubt before anyone asked. Interviewers sometimes ask for doubts directly, so have a real one ready, with what you'd do about it. Practise with Sharing Honest Hesitations About a PM Role Without Hurting Your Candidacy.

Before each loop, write two sentences: which version of the PM job this role is, and which part will be hardest for you. Maya's for the fintech:

"This is the sole PM on a business product with a compliance partner in the team. The hard part for me will be learning before a release instead of after it."

Practise it with Naming the hardest part of the PM role and how you manage it.

All career and values questions