Issue Nº 001
Launching Feb 2026

"The best product managers don't get hired for their frameworks. They get hired for the stories they tell about decisions they made under uncertainty."

Shipped

Weekly · Every Tuesday

Waitlist

1,847

Offers Tracked

214

StripeFigmaNotionLinearAnthropic

Reserve your seat — free to read

I'm sharpening for later
Reverse-engineered PM offersStripe · Figma · Notion · Linear214 offers tracked across 38 companiesWeekly · Every TuesdayMid-career PMs · Senior ICs · Career switchersReverse-engineered PM offersStripe · Figma · Notion · Linear214 offers tracked across 38 companiesWeekly · Every TuesdayMid-career PMs · Senior ICs · Career switchers
§ 01

The Thesis

The PM interview market has a content problem. There's an enormous amount of advice about how to answer product sense questions, and almost nothing about what the people who actually got the job said when they answered them.

Shipped closes that gap. Each issue profiles one PM who landed an offer at a company known for a rigorous bar — Stripe, Figma, Notion, Linear, Anthropic — and reverse-engineers the specific artifacts, framings, and decision narratives that moved them through the panel.

This is not career coaching. It's forensic journalism applied to the PM hiring process. We find the evidence, we annotate it, and we let you draw your own conclusions about how close your own work is to the standard that gets you hired.

"We're not telling you what to do. We're showing you what was done — and precisely why it worked."

— Editorial Position, Issue Nº 001

01

We read the actual submissions

Not Reddit threads about what worked. Not LinkedIn posts about lessons learned. We tracked down the portfolios, case study documents, and take-home exercises that were actually in the room when the hire was made.

02

The hiring manager's lens, not the candidate's

Every profile we run is annotated from the panel's perspective — what they were looking for, where the candidate exceeded it, and the one thing that tipped the decision. It reads like a debrief, not a brag sheet.

03

Specificity is the whole product

We don't say "strong narrative." We show you the exact sentence structure, the precise metric framing, the specific moment in a portfolio walk-through that made the interviewer write "strong hire" in their notes.

214

PM offers tracked across 38 companies since 2024

Stripe · Figma · Notion · Linear · Anthropic · Google · Meta · Amazon

§ 02

Inside an Issue

A deconstructed table of contents from Issue Nº 002 — "How a PM from McKinsey landed L6 at Stripe." Hover each section to read the editorial annotation.

1–2
Openingcontext

The Hire

Who they are, where they landed, what the role was

3–7
Section Ianalysis

The Portfolio Anatomy

Three projects, annotated with what each was doing for the narrative

8–14
Section IIforensic

The Case Study, Frame by Frame

The take-home exercise prompt, their response structure, the panel's reaction

15–20
Section IIIprimary

Three Answers That Moved the Room

Verbatim reconstructions of the product sense, estimation, and behavioral answers

21–22
Closingapplication

The Replication Brief

Four things you can apply to your own work this week

Editorial annotation

Hover a section to read the editorial thinking behind each structural choice.

Issue Nº 002

"How a PM from McKinsey landed L6 at Stripe in 4 rounds"

22 pages
14 annotations

73%

of strong-hire candidates opened their case study with a constraint, not a solution

Based on 89 case study transcripts reviewed in Issues 001–007

§ 03

Who Reads This

01

The Midnight Rewriter

Mid-career PM at a Series B, 4 years in. Has rewritten their resume eleven times this quarter. Knows their work is good — can't figure out why the portfolio isn't landing. Needs a reference point, not another template.

Typically targeting L5–L6 at growth-stage or FAANG. Has shipped. Needs to prove it differently.

StripeFigmaAirbnb
02

The L6 Candidate

Senior IC — engineer, designer, or researcher — preparing for the FAANG PM panel. Has the product instinct. Doesn't yet have the vocabulary, the framing, or the artifact structure that reads as "PM-native" to a hiring committee.

The hardest reader to serve. Knows everything about building; needs to learn how hiring panels read builders.

GoogleMetaAmazon
03

The Career Switcher

Consultant or engineer who thinks in products but can't yet prove it on paper. Has strong analytical bones and weak narrative muscle. Reads Shipped to understand what a PM story actually looks like when it's working.

Needs case studies more than anything. Shipped's archive is their reference library.

LinearNotionAnthropic

"I've read every PM interview guide published in the last three years. Shipped is the first one that made me feel like I was actually reading primary sources."

Priya Mehta

PM · Waitlist reader · Actively interviewing

38

companies whose hiring bar we've mapped from the inside

Updated with each new issue · Growing weekly

§ 04

From the Archive

Three excerpts from past issues. Drag the slider to lift the redaction and read the full analysis — then decide if this is worth a seat on the waitlist.

Issue Nº 003
Figma · Senior PM, Collaboration · L5 → L6
PortfolioFramingL6 Rubric

The portfolio had no metrics until page 7. Here's why that was the right call.

████████████ opened her portfolio walk-through with a constraint, not an outcome. "I want to show you how I think about ████████," she said, "not what I shipped." The panel noted this framing in ████████ of the five scorecards.

Drag to reveal — 0%

Editorial note

The decision to delay metrics was deliberate. Figma's L6 rubric weights strategic framing above execution evidence at the portfolio stage. Aiko had read the room.

Reveal the excerpt to read the annotation.

Issue Nº 005
Notion · PM, Enterprise · L4 → L5
EstimationConstraint-firstEnterprise PM

The case study answer that used three words where everyone else used thirty.

When asked to estimate the number of ████████ in ████████, ████████ paused for four seconds and said: "I'd start with the ████████." The room went quiet. The hiring manager later said it was the ████████ answer they'd heard to that prompt in two years.

Drag to reveal — 0%

Editorial note

The pause was real. Four seconds is long in an interview. What Okafor was doing was identifying the frame before the calculation. That single move signaled systems thinking more clearly than any framework slide could.

Reveal the excerpt to read the annotation.

Issue Nº 007
Linear · PM, Core Product · Senior IC → PM
Career SwitchEngineering → PMDeveloper Tools

She came from engineering. The portfolio showed it. The panel loved it anyway.

The portfolio was structured like a ████████ document, not a PM deck. There were ████████ diagrams, ████████ traces, and exactly zero slides about ████████ strategy. The panel hired ████████ because the ████████ was the strategy.

Drag to reveal — 0%

Editorial note

This is the career-switcher case study. The engineering background wasn't a liability — it was the entire thesis of the hire. Linear was building for developers. Sofia could think like one. The lesson isn't to hide your background. It's to understand what the company is actually hiring for.

Reveal the excerpt to read the annotation.

Free sample issue

Read Issue Nº 001 in full — no strings.

22 pages. The McKinsey PM who landed L6 at Stripe. Your email in exchange for the PDF — and we'll add you to the waitlist at the same time.