A recruiter opens your resume. They spend 6 seconds. In that time, they need to answer three questions:

1. What role does this person want? (Read: your headline)
2. Have they done PM work before? (Read: your first job, first bullet)
3. Have they shipped things at scale? (Read: numbers)

If your resume doesn't answer all three in 6 seconds, you're out.

Every bullet should follow the Outcome → Action → Context pattern.

Weak bullet (before)

"Worked on the checkout flow and improved conversion."

Strong bullet (after)

"Increased checkout conversion 22% ($4.3M ARR uplift) by removing 3 form fields and adding Apple Pay, driven by session-replay analysis of 500 abandoned carts."

Same work. Very different signal.

1. Engineer → PM Transition (Sarah, Google L4)

Before: "Developed backend services for the payments team using Go and Kubernetes."

After: "Led the migration of payments infrastructure from Python to Go (5x throughput, $180K/yr cloud savings), coordinating a 6-person team across 3 timezones — first PM-adjacent role."

2. Consultant → PM Transition (Ryan, Airbnb Sr PM)

Before: "Advised Fortune 500 clients on digital transformation strategy."

After: "Owned a $12M revenue turnaround for a Fortune 500 e-commerce client: identified 3 top drop-off points, defined product roadmap with client's VP Product, and shipped in 90 days — 18% conversion lift."

3. Marketing → PM Transition (Priya, Stripe Sr PM)

Before: "Managed multi-channel marketing campaigns."

After: "Built and shipped a self-serve onboarding flow that replaced 4 marketing campaigns: 61% activation lift, $2.1M ARR unlocked in first quarter."

4. Design → PM Transition (Alex, Figma Sr PM)

Before: "Designed the collaborative canvas experience for enterprise users."

After: "Defined and shipped the multi-cursor collaborative canvas: doubled team-plan adoption in 6 months, drove $8M in expansion ARR — collaborated with 3 engineers and 2 researchers as de facto PM."

5. APM at Startup → Senior PM at FAANG (Dennis, Google Senior PM)

Before: "Owned the mobile app roadmap at [startup]."

After: "Owned the mobile roadmap for a 2M-DAU consumer app: shipped 14 features across 4 quarters, grew D30 retention from 22% → 34% (top decile in category), managed $3M annual OKR."

1. No numbers: "Improved performance" → dead. "Improved p95 latency 40%" → alive.
2. Buzzwords without proof: "Led cross-functional teams" → prove it with team size, project scope, outcome.
3. Verb salad: Every bullet starts with "Led," "Managed," "Drove." Vary your verbs.
4. No context: "Increased revenue $2M" → good. But "Increased revenue $2M by launching X for Y customers" is much better.
5. More than 3 lines: Cut it. If it takes 4 lines, the story is unclear.