The PM role

Startup PM jobs: getting hired and the first months

Lesson 44 of 45~9 min read
In this lesson10 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

At an early startup, a PM job often means being the first product manager at a company that has managed without one, so you're hired to fix a problem the founders already feel. Getting hired leans on introductions more than job postings, and on a real interest in this company's problem. Once you're in, nobody hands you a job description.

Greta, an invented candidate, has four years as a PM at a restaurant-booking company, where she shipped deposits and reminder texts that cut no-shows. At university she worked weekends on a physio clinic's front desk. She wants to join an invented seed-stage startup selling appointment scheduling to small physio and dental clinics: ten people, including four engineers and a designer, and 60 paying clinics.

Why a startup hires a PM at all

Plenty of small companies run without a product manager. The founders decide what to build and engineers talk to customers themselves, until the gap is plain to everyone: the CEO promises features on sales calls that engineers hear about afterwards, or the CTO answers support email at midnight. That's usually when a PM arrives, and within weeks you'll be judged on whether that pain has eased.

Those sales-call promises are made to clinic owners, who buy. But the front desk decides whether a clinic stays: a receptionist who fights the calendar all day will push for a switch at renewal. Where staff pick up a tool on their own and a manager pays once it has spread, daily users decide the sale too.

Judging a startup before you apply

A funding announcement gives the round and its date: $3.5 million, ten months ago. Spending you estimate. Greta took the ten people on the team page at about $18,000 a month each with taxes, benefits and tools ($180,000), minus about $21,000 from 60 clinics at the website's $350 monthly price: roughly $160,000 a month. That's $1.6 million gone and $1.9 million left, just under 12 months at the same rate. Raising takes months, so pitching probably starts within half a year. In her second conversation she checked:

"How many months of runway do you have, and what will investors need to see before the next round?"

Fourteen months, said the CEO, and investors would want clinics staying past their first year. That answer tells you how your work will be judged. A PM whose area shines while the company runs out of money has failed; at a seed-stage company the result that counts is usually the next funding round. So Greta's first job would be keeping clinics, ahead of winning new ones.

A team expects the version of the PM job it saw last, since there's no agreed definition. So check where the founders and first hires worked before:

They came fromThey'll probably expect from a PM
A large consumer app that tests everythingData, small tests, short documents
Enterprise software with slow releasesDetailed specs, a long roadmap
Consulting or financeStructured problems, slides
Their customers' industry, with no PM experienceTo be shown what a PM is for

Greta's CEO ran operations for 25 physio clinics and had never worked with a PM; the CTO and two engineers came from a large consumer marketplace app. So the engineers would expect numbers and short documents, and the CEO would need to see the job done first. But 60 clinics are too few for the A/B tests the engineers knew, so Greta would learn by talking to clinics. Our guide to choosing a startup has more checks.

Last, the opportunity. Ask of any startup: do customers already pay to solve this, why would this team win, and what has changed lately to make it winnable now? Here, clinics already pay for scheduling software, the CEO knows front desks from the inside, and Greta guessed what had changed: patients booking from their phones after hours, which phone-era systems handle badly. To practise this as a founder would, try Founder Strategy: Choosing and Validating a New Travel Startup Opportunity.

What founders who can't train you need to see

Knowing their customers firsthand proves you'll see their problems without a long ramp. It's why the first PM is often someone the startup already employs, and why Greta's weekends on a physio front desk were worth leading with.

A shipping record proves you can take a feature from idea to customers without someone checking each step. Most startups ask for one; Greta's was the deposits and reminder texts. New graduates do better at startups that already have several PMs, where someone has time to teach them.

Running a company, even one that closed, counts as shipping, and you'll be asked what it taught you. To practise, try Turning Startup Founder Lessons into Product Manager Strengths.

Get in through people

One wrong hire is a tenth of a ten-person company, so a name it already trusts carries weight. Greta found hers in the funding announcement she had read for the runway sum. It named four angels, and one had run product at her company two years earlier; they'd met twice. That was enough to ask for a light introduction to the CEO. Read the announcement for people you already know.

She also asked for a 20-minute call with the designer, the nearest thing the startup had to a product team, and got her best early tip: the CTO answered support email most evenings, a gap a PM would fill. Like nearly everyone at a ten-person company, the designer also interviewed candidates, so making time for a possible colleague was part of the job. Ask for a call like hers before you apply.

A memo built on using their product

Greta ran a made-up clinic's Monday morning in a demo account as the front desk would: two cancellations, a late patient, a walk-in. Filling a cancelled slot from the waitlist took 11 clicks and a phone call, because the waitlist couldn't text anyone.

That walkthrough became a one-page memo. It made one bet: fixing the waitlist would do more for clinics than any new feature. The test was auto-texting the waitlist when a slot frees up, measured by cancelled slots filled per clinic each week. Mention what you saw in the product without sending its builders a list of faults.

Make the bet arguable; a memo nobody could dispute says nothing. The measure is what lets someone argue back: the weekly count of filled slots would settle it either way.

To practise choosing a first product bet, try Founding a New-Hire Onboarding Startup: Mission, Segments, Vision and MVP.

Answers only you could give this company

Founders listen for two things in your reason for joining: why their problem matters to you, and why you'd be good at solving it. "I love fast-moving teams and want to grow quickly" answers neither. It would fit any startup, so it tells them you'd take any job. Build the reason from your own history: something about their problem you know firsthand, something you've done that bears on it, and what you'd want to find out first. Greta's:

"I spent three years of weekends on a physio clinic's front desk, and the worst hour was Monday morning, phoning the waitlist to fill cancelled slots. At the restaurant company I shipped deposits and reminder texts that cut no-shows from 11% to 7%. I want to find out whether clinics would trust software to fill those slots without a phone call."

In late rounds, founders often ask what you'd do first. Don't promise fixes for problems you haven't seen: build on what you learned on the way in, and say how you'd find the rest. Greta's:

"First I'd take the support inbox off the CTO and talk to ten current clinics, since the next round depends on clinics staying. Before changing how anyone works, I'd ask each engineer what slows them down, then change one thing, explain why, and drop it if it doesn't help."

To practise the reason for joining, try Making a specific case for joining Sierra as a product manager or Making a Specific, Credible Case for Joining Perplexity as a Product Manager.

Start with the pain the engineers name

Greta got the offer. She asked the four engineers what slowed them down, and three named the same thing: requests from the CEO's sales calls arriving in direct messages, sometimes two clinics promised the same week. A first PM who answers that with sprint rituals and ticket rules can lose a startup's engineers within a week: most joined to ship, and they read new meetings as overhead. Then again, a team often hires a PM because it already misses some structure, and hers had just named which part.

So she added one thing, a one-page note every Monday: this week's work, what isn't being done and why, and who asked for each item. Any engineer can challenge it by replying on the note before noon. She gave the reason first:

"I'm not adding a planning meeting. I'm writing down what we already agreed, so requests from sales come to me first instead of landing on you mid-week."

She offered to drop it after a month if it saved them no time. Whether it's a weekly note or a milestone date, give every new piece of process a reason, and a way to push back on it.

To practise this, try Building a product team: mission, role mix, hiring order and ways of working.

The first 60 days: choose which unowned work to take

Nobody would hand Greta a list of gaps, but her search had already turned up two. The designer had said the CTO answered support email most evenings, which meant two-day replies and less of the CTO's time. The CEO had said the next round depended on clinics staying, yet nobody was asking current clinics why they leave.

Her 60-day plan took exactly those: the support inbox from week one, and ten interviews with current clinics in the first month. Both bore on whether clinics stay. She added one job of her own, a short note to clinics whenever a screen changed, because front desks kept being surprised by new screens.

She told the founders what she was taking and what she wasn't, and used video calls and a spreadsheet, not a paid research tool. Your first 90 days as a PM covers the early weeks at any company.

To practise the interview story, try Ownership story: stepping into work that sat beyond your formal role.

Settle roadmap fights by agreeing who the product is for

By week six the same argument kept returning. Half the team talked about patients and half about front desks, and a request for a patient app split them along that line. Greta drafted two statements of who the product serves, one leading with patients and one with front desks, and tested each against three real requests from the last month. She took the one that settled more to the CEO, who made the call: "Small clinics fill every open appointment without the front desk living on the phone." It went at the top of every Monday note, and the patient app, which did nothing for the front desk, dropped to the bottom.

To practise setting a principle and making it real, try Product Team Culture: The Principles You Build and How You Make Them Real.

All ownership and execution questions

Calls that would sit above you at a large company

Greta's second month brought two, each hers to make or shape. Sales wanted a custom billing export to win one dental chain, while current clinics reported calendar bugs. She fixed the bugs first, since front desks hit them daily and decide whether a clinic renews, and renewals were what the next round needed.

Then pricing. A solo physio paid what a twelve-room practice did. She proposed charging per treatment room for new sign-ups only, so current clinics had no reason to leave before the next round.