Product Manager Career / Resume Beginner

22 ChatGPT prompts for product managers to write achievement-based bullet points

If you are a product manager staring at a blank “experience” section, these 22 ChatGPT prompts for product manager achievement-based bullets are built for the exact moment you hit save on JIRA, ship the launch, or close out the retro. I have been writing and rewriting PM bullets for a while now, and I can tell you: the gap between “owned roadmap for checkout” and “led checkout rewrite that lifted paid conversion 18% and saved $1.4M in dev hours” is the gap between a quiet inbox and a packed interview calendar. The average corporate job opening now draws around 250 applicants, and recruiters spend about 7 seconds scanning each resume that survives the ATS, according to Zety’s 2025 resume keywords guide (Zety, last updated Dec 19, 2025). So your bullets have to do real work, fast. Below is the prompt library I wish I had three job searches ago, plus the framework, the workflow, the comparison table, and the PAA section that ties it all together.

TL;DR - The single most important stat in this whole article: Recruiters reject up to 75% of resumes before a human ever sees them, and 99% of Fortune 500 companies run an Applicant Tracking System on every application. If your PM bullets are not achievement-based, keyword-aligned, and quantified, an algorithm will quietly kill your application while you sleep. (Zety ATS guide, Nov 24, 2025; Zety keywords, Dec 19, 2025)

Why 9 in 10 PM bullets still say “owned roadmap” (with 2026 data)

Most product manager resumes look the same. They list responsibilities, not results. The data backs this up: in Zety’s 2022 analysis of 133,000 resumes (last updated Nov 12, 2025), “Product Manager” appeared as the job title on 344 documents, and the most common skills listed were Agile (19%), Product Management (17%), Project Management (16%), Leadership (15%), and JIRA (13%) (Zety, Nov 12, 2025). Those are the words of the role, not the wins. Nothing on that list tells a hiring manager you moved a number.

That is the core problem this article solves. Achievement-based bullets answer the only question a recruiter actually cares about: “What did you ship, and what changed because you shipped it?” Once you frame every line of your experience section as a delivered outcome, three things happen almost immediately:

Your resume survives the ATS because it mirrors the language of the job ad.
The recruiter’s 7-second scan lands on a number, not a noun.
Your LinkedIn profile, your interview stories, and your self-review all get easier to write, because the raw material is already there.

Lenny Rachitsky’s March 24, 2026 post on the state of the product job market in early 2026 noted that “PM and eng job openings are the highest in years,” which sounds great, until you remember that the bar is also the highest in years. More openings, more applicants, more competition for the senior PM seat you actually want. ChatGPT is not a shortcut, but the right prompt will let you reframe a year of work in an afternoon.

The 4-part PM achievement-bullet anatomy

Before we get to the 22 prompts, lock in the structure. Every great PM bullet has four parts, and every prompt below is engineered to force ChatGPT to produce all four. I call it the AAMS frame, but you will see the same bones in the XYZ formula from Laszlo Bock’s Work Rules!, in the STAR method, and in Resume Worded’s 6-point framework for high-impact resume bullets.

Here is the anatomy:

Action verb - a strong, specific verb that says exactly what you did. Not “responsible for,” not “helped with.” Things like shipped, redefined, de-risked, sunset, instrumented, negotiated, unblocked.
Achievement / scope - the thing you did, the project, the product, the system, the customer segment. Name the surface area so a reader can visualize it.
Metric / magnitude - a number, a percentage, a dollar figure, a latency, an NPS delta, a retention curve. If you can write it down, you can defend it in an interview.
So-what / business outcome - the why. Revenue, cost saved, risk removed, team velocity unlocked, customers retained, support tickets killed.

A bare-responsibility bullet looks like this: “Owned the checkout roadmap.” A four-part achievement bullet looks like this: “Redefined the checkout roadmap around a single-step guest flow, lifting paid conversion 18% and saving an estimated $1.4M in annual dev hours across three squads.” Same PM, same quarter, but the second one is the one the hiring manager screenshots and sends to the hiring committee.

A quick word on honesty. ChatGPT will happily invent metrics if you let it. Never paste a number into your resume that you cannot defend in a 30-minute interview. Use the prompts below to surface the metrics you already have in Looker, Mixpanel, Amplitude, Heap, or PostHog, and let the model arrange them.

SECTION 1 - Discovery & outcome prompts (prompts 1–5)

These prompts turn the messiest part of the PM job - discovery - into crisp resume bullets. Discovery work is often invisible because it lives in docs, in Notion, in Confluence, in FigJam, in Dovetail, and in 90-minute user calls. The prompts below force you to extract the wins from that work and put them on the page.

Prompt 1 - The “discovery to dollars” translator

Purpose: Most PMs run tons of discovery but never tie it to a business outcome. This prompt turns a discovery effort into a single quantified bullet.

Prompt text:

You are a senior product resume coach who specializes in achievement-based bullets for product managers. I am going to paste raw notes from a discovery project I led. Rewrite them as 3 resume bullet points that follow this 4-part structure:

1. Strong action verb (e.g., spearheaded, instrumented, reframed, synthesized)
2. The scope or surface area (product, feature, customer segment, team)
3. A quantified metric or magnitude (number, percentage, dollar, time)
4. A clear "so what" - the business outcome (revenue, retention, cost saved, risk removed)

Rules:
- Every bullet must start with a past-tense action verb. No "Responsible for."
- Every bullet must contain at least one number. If I have not given you a number, write "[INSERT METRIC]" as a placeholder I can fill in.
- Never invent metrics I did not provide. If something is unclear, ask me one clarifying question before writing.
- Keep each bullet to 1–2 lines (max 28 words). PM resume bullets over 3 lines get skipped.
- Use the tone of a Senior PM at Google, Meta, Stripe, Notion, Linear, or Anthropic.
- At the end, give me a "Pro tip" for each bullet explaining why it works.

Here are my raw discovery notes:
[PASTE NOTES]

Example output:

Synthesized 32 customer interviews and 4,200 support tickets into a Jobs-to-be-Done backlog, reframing the onboarding roadmap around a single “aha moment” that lifted D7 retention [INSERT %] and cut time-to-value from [INSERT] days to [INSERT] minutes.
Built a FigJam opportunity solution tree covering 6 customer segments, aligning 4 cross-functional stakeholders on a unified Q3 roadmap and removing [INSERT] weeks of roadmap churn.
Codified a weekly insight-to-experiment loop in Notion, replacing ad-hoc research requests and saving the team an estimated [INSERT] hours of PM and research time per quarter.

Pro tips for use:

Paste your raw discovery notes, not your polished summary. The model does better with the unedited material.
If a bullet has two metrics, that is great - it gives the reader a sense of scale (e.g., “$1.4M saved across 3 squads”).
Run the output through your company’s review process. Some employers have rules about sharing internal metrics with third-party tools.

Prompt 2 - The “user research to shipped feature” bridge

Purpose: This prompt forces you to connect a research insight all the way through to a shipped feature and its downstream impact.

Prompt text:

Act as a PM resume strategist. I will describe a user research effort and the product that came out of it. Generate exactly 1 achievement-based resume bullet for a product manager resume.

Use the structure:
[Action verb] [the research method] [with N participants/users/tickets] → [the product decision] → [metric 1: leading indicator] and [metric 2: lagging business outcome].

Constraints:
- 1 sentence, 22–32 words.
- Start with a strong past-tense action verb.
- Must include at least 2 numbers.
- Must mention a tool, method, or framework (e.g., JTBD, RICE, opportunity solution tree, storyboard, prototype in Figma, unmoderated test in Maze or UsabilityHub).
- Output the bullet, then a one-line "Why this works" annotation.

Inputs:
- Research method: [INSERT]
- Sample size: [INSERT]
- Product decision: [INSERT]
- Leading metric: [INSERT]
- Lagging metric: [INSERT]

Example output:

Ran 24 unmoderated Maze tests and 12 JTBD interviews on 3 checkout variants, greenlighting a single-step guest flow that lifted paid conversion 18% and reduced support tickets about checkout by 32% in the first 60 days. (Why this works: it strings research → decision → leading metric → lagging metric in one line, and names the exact methods a senior PM would actually use.)

Pro tips for use:

This is the prompt to use for roles that explicitly want “data-informed PM” or “customer-obsessed PM” in the job ad.
If you only have one number, the prompt will flag it. Add a proxy metric (e.g., “support tickets per 1k orders”) so the bullet still tells a complete story.
Mention specific tools - Maze, Dovetail, UserTesting, Hotjar, FullStory - they double as keywords the ATS will pick up.

Prompt 3 - The “experimentation engine” bullet

Purpose: Most PMs run dozens of A/B tests but never quantify them. This prompt turns your test cadence into a single, dense bullet.

Prompt text:

You are writing for a senior PM resume targeting Google, Meta, Stripe, Notion, Linear, or Anthropic-level bars. I will give you a list of experiments I shipped in a quarter or year. Aggregate them into 1–2 achievement-based bullets that show both experimentation rigor and shipped impact.

For each bullet, use this frame:
[Action verb] [N experiments] across [surface area] using [tooling, e.g., Optimizely, GrowthBook, Statsig, internal A/B framework], shipping [M winners] that moved [primary metric] by [%] and [secondary metric] by [% or $].

Rules:
- Aggregate numbers, do not list each experiment.
- Include the experimentation tool name when possible.
- Quantify shipping velocity (winners shipped per quarter or per year).
- If I have not given a number, write "[INSERT]".
- 1–2 bullets total. Each bullet 1–2 lines.

My experiment data:
- Quarter / year: [INSERT]
- Number of experiments shipped: [INSERT]
- Tooling: [INSERT]
- Win rate: [INSERT, e.g., 4 of 11, ~36%]
- Top winner: [INSERT metric and lift]
- Cumulative impact: [INSERT, e.g., +$2.3M ARR, +11% retention]

Example output:

Shipped 27 A/B tests in 2025 across onboarding, pricing, and checkout using GrowthBook, shipping 9 winners that lifted activation 14% and added an estimated $2.3M in incremental ARR.
Stood up a 2-week experiment cadence (up from 6 weeks), cutting time-to-decision 70% and unlocking 3 roadmap reprioritizations per quarter based on real signal rather than HiPPO opinions.

Pro tips for use:

“Win rate” is a phrase senior PMs love because it shows you know experiments fail.
“Time-to-decision” is one of Marty Cagan’s favorite metrics from the SVPG operating model - it is a great way to drop a Marty-style frame in your resume.
If you do not have a dollar figure, use engagement, retention, latency, or p99 reliability. Anything that is on a dashboard.

Prompt 4 - The “NPS / CSAT / support deflection” bullet

Purpose: Voice-of-customer bullets are gold for PMs interviewing for retention, growth, or platform roles. This prompt turns qualitative wins into quantified ones.

Prompt text:

Rewrite a vague product manager bullet about customer satisfaction or support work into a quantified achievement bullet.

Original bullet:
[PASTE YOUR VAGUE BULLET]

You must produce exactly 1 bullet that follows this template:
[Action verb] [the VOC program, support tooling, or feedback system] across [surface area or user segment], moving [metric 1: NPS, CSAT, CES, deflection rate, sentiment] from [before] to [after] and reducing [metric 2: tickets, churn, escalations] by [% or $].

Rules:
- 1 sentence, 22–30 words.
- Use real product or tooling names (Zendesk, Intercom, Pendo, Amplitude, Mixpanel, Hotjar, Dovetail, Productboard, Aha!).
- If the original bullet lacks numbers, infer reasonable ranges from public benchmarks and flag them as "[ESTIMATED, VERIFY]".
- Output the bullet and a "Verify before sending" checklist of 3–5 questions I should answer to confirm the numbers.

Example output:

Redesigned the in-app feedback loop in Pendo and rebuilt the Zendesk macro library across 4 surfaces, lifting NPS from 31 to 47 and deflecting an estimated 18% of Tier-1 support tickets within one quarter. (Verify before sending: 1) What was NPS before/after? 2) What is the exact deflection rate? 3) What is the support cost saving? 4) Did you personally write the macros? 5) Was this rolled out in one quarter or staggered?)

Pro tips for use:

The “verify before sending” checklist is the most important part of this prompt. It is the safety net that keeps you honest.
If you are applying to a B2B PM role, swap NPS for logo retention, gross retention, or NRR.
If you are applying to a consumer PM role, swap NPS for App Store rating, store review sentiment, or DAU/MAU stickiness.

Prompt 5 - The “insight to roadmap” bullet

Purpose: Hiring managers for Senior PM roles want to see that your insight actually changed the roadmap. This prompt makes that explicit.

Prompt text:

I am a product manager. I will paste a short paragraph describing an insight I uncovered and the roadmap change it triggered. Produce 1 achievement-based resume bullet for a Senior PM resume targeting Google, Meta, Stripe, Notion, Linear, Anthropic, OpenAI, Shopify, Atlassian, or Airbnb.

Frame:
[Action verb] [N interviews / N data points / N experiments] revealing [the insight], reprioritized the [Q? / H?] roadmap to [new bet], and shipped [feature] that moved [metric] by [% or $] within [time window].

Rules:
- One sentence. 25–32 words.
- One insight, one decision, one shipped outcome.
- Use "storybrand" or "Jobs to be Done" framing only if it actually matches the work; do not force it.
- Mention the artifact that drove the decision: opportunity solution tree (Teresa Torres), discovery brief, North Star metric dashboard, OKR, RICE score.
- Output the bullet plus a 1-sentence "How to talk about this in an interview" coaching note.

Inputs:
- Insight: [INSERT]
- Reprioritization: [INSERT]
- Feature shipped: [INSERT]
- Metric: [INSERT]
- Time window: [INSERT]

Example output:

Synthesized 18 win/loss interviews revealing a single onboarding gap, reprioritized the Q3 roadmap to fix the “first-run experience,” and shipped a 4-step activation flow that lifted D7 retention from 22% to 31% in 6 weeks. (How to talk about this in an interview: open with the insight, walk through the reprioritization trade-offs you made, name what you cut to make room, and close with the metric.)

Pro tips for use:

Teresa Torres’s opportunity solution tree is the cleanest visual artifact for this kind of work. Reference it.
If you cannot name a single insight in one sentence, you do not have a sharp bullet yet. Re-run discovery until you can.
This bullet is also a great template for a “Senior PM vs PM” interview, because it shows scope, judgment, and shipped impact in one line.

SECTION 2 - Strategy & roadmap prompts (prompts 6–9)

Strategy is where PMs get the most vague. “Defined the strategy for X” is the kind of bullet that makes a hiring manager roll their eyes. The four prompts in this section force you to be specific about what strategy you set, what trade-offs you made, and what shipped.

Prompt 6 - The “vision to roadmap” bullet

Purpose: This prompt turns a fuzzy “set the strategy” claim into a concrete, falsifiable bullet.

Prompt text:

You are a product strategy editor. I will describe a product strategy I set. Rewrite it as 1 achievement-based bullet for a PM resume.

Frame:
[Action verb] the [time horizon: e.g., 12-month, 18-month] product strategy for [product / surface area], aligning [N] stakeholders on [N strategic bets or OKRs] that targeted [primary metric: e.g., NRR, activation, MAU, latency], and shipped [N] of [N] bets in [time window].

Rules:
- Name the strategic framework if you used one: OKRs, JTBD, Wardley Maps, Brian Lovin's product strategy canvas, John Cutler's product strategy modes, Porter's five forces (only for B2B or platform plays).
- One bullet, 1–2 lines, 25–32 words.
- Output a "Strategy artifact checklist" of 3–5 docs or visuals I should be able to point to if asked in an interview (e.g., strategy doc in Notion, North Star dashboard in Amplitude, opportunity solution tree in FigJam, OKR tree in Aha! or Productboard).
- If you cannot fill in any number, write "[INSERT]" - do not invent.

My input:
- Time horizon: [INSERT]
- Product / surface area: [INSERT]
- Number of stakeholders aligned: [INSERT]
- Number of strategic bets / OKRs: [INSERT]
- Primary metric: [INSERT]
- Bets shipped: [INSERT]
- Time window: [INSERT]

Example output:

Set the 12-month product strategy for the B2B platform team, aligning 7 cross-functional stakeholders on 4 OKRs targeting NRR, and shipped 3 of 4 bets in 9 months - including a usage-based pricing model that lifted expansion revenue 22%. (Strategy artifact checklist: 1) Strategy doc in Notion, 2) OKR tree in Productboard, 3) Wardley map in Miro, 4) North Star dashboard in Mode, 5) Quarterly business review slide deck.)

Pro tips for use:

The strategy artifact checklist is the cheat code. Most PMs do the work and forget to keep the artifact. Build the habit now.
Use Productboard, Aha!, Roadmunk, or Height for the roadmap layer. Naming the tool in your bullet is a small but real ATS win.
“3 of 4 bets shipped” is more credible than “4 of 4 bets shipped.” Real strategy is the art of cutting things.

Prompt 7 - The “deprioritization” bullet (yes, really)

Purpose: Deprioritization is one of the most senior PM moves, and almost no one writes it on their resume. This prompt fixes that.

Prompt text:

You are a PM resume coach for Senior PM and Group PM roles. Generate 1 achievement-based bullet about killing, sunsetting, or deprioritizing a project. This is a senior signal and you must treat it as such.

Frame:
[Action verb] the decision to [kill / sunset / pause / deprioritize] [project or feature] after [evidence: e.g., 6 weeks of A/B data, 12 customer interviews, a discovery spike], freeing [N engineers / N designers / $X] to focus on [new bet] that moved [metric] by [% or $] within [time window].

Rules:
- This bullet must show judgment, not just decisiveness. The "after [evidence]" clause is mandatory.
- 1 sentence, 25–32 words.
- Include the kill metric or kill threshold (e.g., "<2% lift, <5% activation").
- Output a "How this signals senior PM" annotation.

Inputs:
- Project killed: [INSERT]
- Evidence: [INSERT]
- Resources freed: [INSERT]
- New bet: [INSERT]
- Metric moved: [INSERT]
- Time window: [INSERT]

Example output:

Killed the in-app messaging roadmap after 6 weeks of A/B data showed <1.2% lift, freeing 4 engineers to ship the new onboarding flow that moved D7 activation from 22% to 31% in 8 weeks. (How this signals senior PM: it shows you can read the data, make the call, and reallocate resources. Group PMs and Directors specifically screen for this.)

Pro tips for use:

If you are interviewing for a Group PM, Director of Product, or VP Product role, the deprioritization bullet may matter more than any launch bullet.
The kill threshold is everything. Without “<1.2% lift” or “<5% activation,” the bullet just sounds like you gave up.
Cross-link this bullet to your STAR interview story. The deprioritization conversation comes up in almost every senior loop.

Prompt 8 - The “platform / internal tool” bullet

Purpose: Platform PMs are usually terrible at marketing themselves. This prompt makes internal tools look like revenue.

Prompt text:

You are a platform PM resume writer. I will describe an internal platform, SDK, API, or developer tool I built or improved. Rewrite it as 1 achievement-based bullet that translates internal impact into business impact.

Frame:
[Action verb] [the platform / SDK / API / internal tool], unblocking [N internal teams or N external developers], reducing [internal cost: dev hours, tickets, latency, time-to-ship] by [quantified amount], and enabling [downstream business outcome: new product, new market, new customer segment, $X in revenue].

Rules:
- 1 sentence, 25–32 words.
- Translate "internal" to "business." Never write "improved the platform" without the downstream.
- If the platform is external (public API, SDK, integration), use developer-facing metrics: time-to-first-call, MAU of the API, NPS of the SDK, # of integrations.
- If the platform is internal, use internal-product metrics: dev hours saved, # of teams unblocked, time-to-launch, ticket deflection.

Inputs:
- Platform / tool: [INSERT]
- Audience: [INSERT]
- Internal cost saved: [INSERT]
- Downstream business outcome: [INSERT]

Example output:

Rebuilt the internal experimentation platform in GrowthBook, unblocking 6 product squads, reducing experiment setup time from 4 days to 4 hours, and enabling 3 launches in Q4 that together added $1.8M in ARR.
Launched a public REST API and Node SDK with 1,200 MAU by month 3, becoming the top integration request from enterprise prospects and unblocking 2 deals worth $480k ACV.

Pro tips for use:

Platform PMs get hired on “scale.” Always quantify the number of teams or developers affected.
“Time-to-X” metrics (time-to-first-call, time-to-experiment, time-to-integration) are the most underrated resume phrases for platform PMs.
If the platform is a tooling bet you championed, frame it like Prompt 6 - strategy, bets, shipped.

Prompt 9 - The “OKR / KPI” bullet

Purpose: OKRs are the connective tissue of PM work. This prompt forces your OKR into a bullet that actually tells the reader what you delivered.

Prompt text:

You are a PM resume editor. I will give you 1 OKR (objective + key results) I owned. Produce exactly 1 achievement-based bullet for a PM resume that an ATS and a human will both reward.

Frame:
[Action verb] [the objective] by [shipping / leading / orchestrating] [N initiatives across M teams], moving KR1 from [baseline] → [result] ([% improvement]) and KR2 from [baseline] → [result] within [time window].

Rules:
- 1 sentence, 25–32 words.
- Include the % improvement on at least one KR.
- Mention the artifact: dashboard in Looker, Mixpanel, Amplitude, Mode, Hex, Tableau; OKR doc in Notion, Confluence, Coda, Asana, Linear.
- If you exceeded the OKR (e.g., target was 10% and you hit 18%), say so - overachievement is a strong senior signal.
- Output a "KPI selection note" explaining whether KR1 and KR2 were the right metrics to pick, and a better choice if not.

Inputs:
- Objective: [INSERT]
- KR1 baseline / result / target: [INSERT]
- KR2 baseline / result / target: [INSERT]
- Time window: [INSERT]
- Initiatives shipped: [INSERT]

Example output:

Cut p95 checkout latency from 2.1s to 0.8s by orchestrating 3 infra and 2 frontend initiatives, beating the 2025 OKR by 2x and unlocking the EU expansion that shipped in Q1 2026. (KPI selection note: p95 latency is the right KR for a checkout perf OKR; you may also want to add a “revenue per session” KR so the business side of the OKR is also visible.)

Pro tips for use:

”% improvement” and “vs target” are the two phrases that turn an OKR into a story.
If your OKR was a leading indicator (e.g., “experiments shipped per month”), pair it with a lagging indicator in the same bullet. Hiring managers want both.
For Director of Product resumes, you can stack 2–3 OKRs in a single bullet and label them as a portfolio.

SECTION 3 - Launch & GTM prompts (prompts 10–13)

Launches are the most over-claimed part of any PM resume. “Led the launch of X” is the second-most common PM bullet on earth. The four prompts below force your launch bullets to show real coordination, real go-to-market craft, and real outcome.

Prompt 10 - The “launch from 0 to 1” bullet

Purpose: 0-to-1 launches are how early-stage and growth-stage PMs differentiate. This prompt forces a clean before/after.

Prompt text:

You are a launch resume editor. I will describe a 0-to-1 product or feature launch I led. Produce 1 achievement-based bullet for a PM resume.

Frame:
[Action verb] the launch of [product / feature] from concept to GA in [time window], coordinating [N] cross-functional teams (eng, design, marketing, sales, CS, support), acquiring [N] users or [N] customers in [time window], and moving [metric: activation, retention, NRR, revenue] by [% or $].

Rules:
- 1 sentence, 25–32 words.
- "From concept to GA" is optional. If it was a 0-to-1 inside a larger product, write "from discovery to GA" instead.
- Quantify both speed (time window) and outcome (metric).
- Mention at least one launch artifact: GTM doc in Notion, launch checklist in Asana, launch comms in Slack + Loom, sales enablement deck in Pitch or Slides, in-product launch modal in Pendo or Appcues.
- Output a "Launch checklist" of 5 things an experienced PM interviewer will ask you about your launch (positioning, pricing, GTM motion, success metric, retrospective).

Inputs:
- Product / feature: [INSERT]
- Time window: [INSERT]
- Teams coordinated: [INSERT]
- Users / customers acquired: [INSERT]
- Outcome metric: [INSERT]

Example output:

Shipped the AI summarization feature from concept to GA in 14 weeks, coordinating 4 squads and a GTM pod, acquiring 38,000 activated users in 60 days, and lifting weekly retention from 41% to 53%. (Launch checklist: 1) Positioning and who-it-is-for, 2) Pricing model and why, 3) GTM motion (PLG, sales-led, hybrid), 4) Success metric and dashboard, 5) Retro and what you would change next time.)

Pro tips for use:

If you do not have the exact “users acquired” number, use “weekly active users,” “paying teams,” or “qualified pipeline.”
For consumer products, “weekly retention” or “D30 retention” is more honest than “downloads.”
For B2B, name the ICP (ideal customer profile), not the company size bucket. “Mid-market RevOps leaders” beats “enterprise” every time.

Prompt 11 - The “growth / activation” bullet

Purpose: Growth PMs live and die by activation. This prompt turns a “grew the funnel” claim into a real bullet.

Prompt text:

You are a growth PM resume writer. I will describe a growth or activation experiment I ran. Produce 1 achievement-based bullet that uses the AAARRR (or AARRR) pirate metrics framework by Dave McClure, or the North Star Metric framework by Sean Ellis / Lean Analytics, depending on which fits the work.

Frame:
[Action verb] the [activation / acquisition / retention / revenue] funnel by [N experiments] across [surface area], shipping [N] winners that moved [primary metric: activation rate, sign-up conversion, NRR, etc.] from [baseline] → [result] within [time window].

Rules:
- 1 sentence, 25–32 words.
- Always include both the baseline and the result. A 2x improvement from 1% to 2% is a great bullet; a 2x improvement without context is not.
- Use the actual funnel stage you worked on: awareness, acquisition, activation, retention, revenue, referral.
- Mention the experimentation tool, e.g., GrowthBook, Statsig, Optimizely, VWO, LaunchDarkly, or an in-house framework.
- Output an "Activation metric sanity check" - is your chosen metric the right one for this funnel stage, or would a leading indicator serve you better?

Inputs:
- Funnel stage: [INSERT]
- Number of experiments: [INSERT]
- Surface area: [INSERT]
- Tooling: [INSERT]
- Baseline: [INSERT]
- Result: [INSERT]
- Time window: [INSERT]

Example output:

Drove the activation funnel through 19 experiments on the new-user first-run experience in Statsig, lifting D1 activation from 34% to 49% and contributing 6 points to D30 retention over a single quarter. (Activation metric sanity check: D1 activation is the right leading indicator for a first-run-experience program; consider pairing it with a “first valuable action” event so you are measuring activation, not just sign-in.)

Pro tips for use:

The most over-used growth bullet is “grew sign-ups by X%.” That is acquisition, not activation. Senior PMs and growth leads can tell the difference.
If you are applying to a growth pod, mention the experimentation tool. It signals you have actually shipped, not just theorized.
“Contributing 6 points to D30 retention” is a great line because it shows you understand the lagging-indicator story.

Prompt 12 - The “monetization / pricing” bullet

Purpose: Pricing is the highest-leverage thing a PM can ship. Most PMs avoid writing about it on their resume because the numbers are sensitive. This prompt helps you say it without leaking.

Prompt text:

You are a monetization-focused PM resume writer. I will describe a pricing, packaging, or monetization change I led. Produce 1 achievement-based bullet that is honest about the magnitude without disclosing confidential figures.

Frame:
[Action verb] the [pricing model / packaging / monetization] for [product / segment], moving [leading metric: ARPU, ACV, expansion, NRR, take-rate] by [% in a defined band] and contributing to [lagging business outcome: ARR, gross margin, win rate, sales cycle length] without disclosing confidential numbers.

Rules:
- 1 sentence, 25–32 words.
- Never invent a specific dollar figure. Use ranges, percentages, or banded language ("in the high single digits," "low double digits").
- Reference the framework: price elasticity, willingness-to-pay (WTP) analysis, van Westendorp PSM, value-based pricing, usage-based pricing, hybrid, or good-better-best.
- Output a "Confidentiality note" explaining what to redact before sending the resume to a competitor.

Inputs:
- Change: [INSERT]
- Leading metric: [INSERT]
- Lagging outcome: [INSERT]
- Framework: [INSERT]

Example output:

Migrated the platform from seat-based to usage-based pricing using a van Westendorp PSM analysis, lifting blended ARPU in the low double digits and shortening median sales cycle by 9 days within one quarter. (Confidentiality note: redact the exact ARPU band, the specific PSM price points, and any customer name from the case study. Keep the directional language.)

Pro tips for use:

If you cannot share a number, that is fine. Hiring managers for monetization roles know the work is sensitive and will respect a clean, range-only bullet.
“Shortened sales cycle” is a real monetization signal. Pricing that the sales team has to apologize for is bad pricing.
For marketplace PMs, “take-rate” is the right leading metric. For SaaS PMs, “ARPU” or “ACV.” Pick the one your CFO actually uses.

Prompt 13 - The “retention / churn” bullet

Purpose: Retention is the metric that matters most after PMF. This prompt forces a defensible retention bullet.

Prompt text:

You are a retention-focused PM resume editor. I will describe a churn or retention project I led. Produce 1 achievement-based bullet that names the cohort, the intervention, and the result.

Frame:
[Action verb] [the intervention: save flow, re-engagement campaign, onboarding fix, pricing change, customer success motion] for [cohort: enterprise, self-serve, new sign-ups, at-risk accounts], moving [metric: NRR, gross retention, logo churn, D30, D90, resurrection rate] from [baseline] → [result] within [time window].

Rules:
- 1 sentence, 25–32 words.
- Name the cohort. "All customers" is not a cohort.
- Pick the right retention metric for the cohort: gross retention for logo churn, NRR for expansion, D30/D90 for new-user retention, resurrection rate for win-back.
- Mention the tooling: Vitally, ChurnZero, Gainsight, Planhat, Totango, Mixpanel, Amplitude, Heap.
- Output a "Retention math check" so you do not accidentally overstate.

Inputs:
- Intervention: [INSERT]
- Cohort: [INSERT]
- Metric: [INSERT]
- Baseline: [INSERT]
- Result: [INSERT]
- Time window: [INSERT]

Example output:

Shipped a 3-email win-back sequence and a CS-led save flow for self-serve accounts inactive 30+ days, lifting the 90-day resurrection rate from 4% to 11% and protecting an estimated $640k in at-risk ARR. (Retention math check: verify the cohort definition (“inactive 30+ days” is good), the baseline window, and that the ARR figure uses gross retention math, not net retention math.)

Pro tips for use:

If you work in B2B SaaS, name the CS tool. Recruiters for Series B+ companies read for Vitally, Gainsight, Planhat, and ChurnZero specifically.
“Protecting ARR” is a phrase senior finance partners love. It frames retention as defensive revenue, not just engagement.
If you do not have a dollar number, you can use a “logos saved” or “accounts re-engaged” count instead.

SECTION 4 - Cross-functional & stakeholder prompts (prompts 14–17)

Senior PM roles are 50% stakeholder management. The four prompts in this section turn the meeting-heavy, Slack-heavy, doc-heavy work of influencing a roadmap into resume lines that hiring managers actually want to see.

Prompt 14 - The “exec alignment” bullet

Purpose: Exec alignment is invisible until you write it down. This prompt forces a clean bullet that shows the cost of misalignment and the value of alignment.

Prompt text:

You are a senior PM resume writer. I will describe a time I aligned executives (CPO, CTO, CEO, CFO, GM) on a hard product decision. Produce 1 achievement-based bullet for a PM resume.

Frame:
[Action verb] cross-functional alignment on [the decision: kill, re-org, bet, pricing change, platform investment] across [N execs / N teams] by [the artifact: 1-pager in Notion, model in Coda, memo in Confluence, deck in Pitch or Slides, working session in FigJam], compressing decision time from [before] to [after] and unlocking [N launches / $X in pipeline / Y% in cost].

Rules:
- 1 sentence, 25–32 words.
- Always quantify the time saved. "Aligned the team" without a number is not a bullet.
- Mention the artifact. Hiring managers for Director+ roles specifically screen for "did this person write things down."
- Output a "How to talk about this in a VP interview" coaching note.

Inputs:
- Decision: [INSERT]
- Stakeholders: [INSERT]
- Artifact: [INSERT]
- Time saved: [INSERT]
- Outcome: [INSERT]

Example output:

Aligned CPO, CTO, and CFO on sunsetting the legacy mobile app by writing a 2-page memo in Notion and a FigJam cost model, cutting the decision cycle from 6 weeks to 9 days and freeing 3 engineers for the new AI roadmap. (How to talk about this in a VP interview: open with the trade-off (sunset vs. maintain), name the political risk, walk through how you de-risked it, and close with the metric.)

Pro tips for use:

“Memo” is one of the most underrated words in a senior PM resume. A one-page memo is the most common artifact for exec alignment.
If you used a template, mention the framework: Stratechery-style memo, Amazon-style 6-pager, YC-style 1-pager, or a Marty Cagan-style product brief (SVPG has a great template).
“Cutting the decision cycle from 6 weeks to 9 days” is the kind of line that gets you the second interview.

Prompt 15 - The “engineering partnership” bullet

Purpose: Strong PMs ship because they have great engineering partnerships. This prompt makes that partnership visible on the resume.

Prompt text:

You are a PM resume editor with a deep respect for engineering. I will describe a way I partnered with engineering (EMs, Staff+, ICs). Produce 1 achievement-based bullet that honors the engineering craft while making the PM's contribution clear.

Frame:
[Action verb] [the engineering outcome: shipped a re-architecture, reduced incident rate, lifted test coverage, cut p95 latency, improved release cadence] by [the PM move: discovery, prioritization, RFC, unblocking, scoping, de-risking, working in Linear or Jira], partnering with [N] engineers across [N] squads, moving [metric] from [baseline] → [result] within [time window].

Rules:
- 1 sentence, 25–32 words.
- Do not take credit for engineering work. The PM move must be a real PM move.
- Mention the engineering artifact: tech spec in Notion, RFC in Confluence, ADRs in the repo, design doc in Google Docs, sequencing in Linear, Jira, Shortcut, Height, or Asana.
- Output an "Engineering interview prep" note - what an EM will most likely grill you on for this kind of bullet.

Inputs:
- Engineering outcome: [INSERT]
- PM move: [INSERT]
- Engineering partners: [INSERT]
- Tooling: [INSERT]
- Metric: [INSERT]
- Time window: [INSERT]

Example output:

Cut p95 checkout latency from 2.1s to 0.8s by writing the RFC and discovery brief that let 3 squads de-risk the rewrite, partnering with 11 engineers across Platform, Web, and Payments over a 9-week rebuild. (Engineering interview prep: the EM will ask about your discovery rigor, your trade-off conversation, and what you cut from the scope to ship on time. Be ready with a clear “cut list.”)

Pro tips for use:

“RFC” and “tech spec” are senior PM signals. If you wrote one, name it.
Naming the squads (Platform, Web, Payments) is more credible than “cross-functional team.”
For platform PM roles, the engineering partnership bullet is non-negotiable. Make it specific.

Prompt 16 - The “design partnership” bullet

Purpose: Design and PM tension is real. This prompt makes your design partnership look like a force multiplier.

Prompt text:

You are a PM resume editor who has shipped with great designers. I will describe a design-led project I partnered on. Produce 1 achievement-based bullet.

Frame:
[Action verb] [the design outcome: new design system, redesigned surface, accessible product, mobile app refresh, motion system, brand refresh] by [the PM move: research, sequencing, prioritization, instrumentation], partnering with [N] designers, moving [metric: task completion, time-on-task, NPS, conversion, DAU/MAU] from [baseline] → [result] within [time window].

Rules:
- 1 sentence, 25–32 words.
- Name the design artifact: Figma file, FigJam jam, design system in Zeroheight or Storybook, motion principles in Lottie or Rive, brand book in Figma, design tokens in Style Dictionary.
- For accessibility, name the WCAG level: WCAG 2.2 AA, AAA, or section 508.
- Output a "Design partnership interview prep" note.

Inputs:
- Design outcome: [INSERT]
- PM move: [INSERT]
- Designers partnered with: [INSERT]
- Metric: [INSERT]
- Time window: [INSERT]

Example output:

Redesigned the new-user onboarding in Figma and shipped a WCAG 2.2 AA-compliant experience, partnering with 2 product designers and 1 motion designer, cutting time-to-first-value from 12 minutes to 3 minutes and lifting D7 retention 8 points. (Design partnership prep: the design lead will ask how you balanced research velocity with design exploration, and how you decided what to ship vs. what to defer to v2.)

Pro tips for use:

“WCAG 2.2 AA” is a magic phrase for accessibility-conscious companies (Atlassian, Shopify, Microsoft, government-adjacent).
Naming a Figma file or a FigJam jam is fine. The point is to signal you actually opened the file, not just attended the review.
For design-system PMs, replace “designer” with “design systems team” and mention tokens, primitives, and adoption metrics.

Prompt 17 - The “data and analytics partnership” bullet

Purpose: Modern PMs ship with data. This prompt makes your data partnership a real, visible asset on the resume.

Prompt text:

You are a data-literate PM resume editor. I will describe how I partnered with data science, analytics, or ML teams. Produce 1 achievement-based bullet.

Frame:
[Action verb] [the data outcome: a dashboard, a model, an A/B framework, an ML feature, a metrics taxonomy, a North Star framework] by [the PM move: defining the question, instrumenting events, running a spike, scoping the model], partnering with [N] data scientists or analysts, and moving [product metric] by [% or $] within [time window].

Rules:
- 1 sentence, 25–32 words.
- Name the data tool: Looker, Mode, Hex, Tableau, BigQuery, Snowflake, dbt, Amplitude, Mixpanel, Heap, PostHog, Segment, mParticle, RudderStack, Hightouch, Census.
- For ML features, name the model type lightly: LLM, classifier, recommender, embedding, RAG, fine-tune. Do not go deeper than the resume should.
- Output a "Data partnership interview prep" note.

Inputs:
- Data outcome: [INSERT]
- PM move: [INSERT]
- Data partners: [INSERT]
- Product metric: [INSERT]
- Time window: [INSERT]

Example output:

Stood up a North Star dashboard in Looker and instrumented 14 new events in Segment, partnering with 2 analysts, that gave the org a single source of truth for activation and unlocked 3 reprioritizations in the next planning cycle. (Data partnership prep: the data lead will ask what you instrumented, what you decided NOT to instrument, and how you avoided “dashboard sprawl.”)

Pro tips for use:

“Single source of truth” is a phrase that resonates with ops-minded PMs. Use sparingly.
For AI PM roles, name the model class: “shipped a RAG-based assistant,” “fine-tuned a small LLM,” “evaluated 3 embedding models for retrieval.” These are keywords your interviewers will scan for.
For growth PMs, name the experimentation tool again. It signals you can self-serve analysis.

SECTION 5 - Metric & KPI prompts (prompts 18–22)

The last section is the most senior. The five prompts in this section turn a year of metrics into a story arc the reader can follow. They are designed to make a Director of Product, VP of Product, or Head of Product stop and pay attention.

Prompt 18 - The “single number that mattered” bullet

Purpose: Every great PM has a single number that defined a year. This prompt turns that number into a bullet.

Prompt text:

You are a senior PM resume editor. I will give you a single metric that defined my year (e.g., NRR, retention, ARPU, latency, MAU, win rate, sales cycle length, NPS). Produce 1 achievement-based bullet that frames the metric, the year, the work, and the impact.

Frame:
[Action verb] [N initiatives or N bets] in [year / quarter] that moved [the number] from [baseline] → [result] for [product / surface area], with [secondary metric] moving from [baseline] → [result] as a downstream effect.

Rules:
- 1 sentence, 25–32 words.
- The number is the star. Build the bullet around it.
- Always include the secondary metric. Single-metric bullets can mislead.
- Output an "If asked in the loop" interview prep: the 3 most likely follow-up questions and how to answer them.

Inputs:
- The number: [INSERT, e.g., NRR]
- Year / quarter: [INSERT]
- Initiatives: [INSERT]
- Surface area: [INSERT]
- Secondary metric: [INSERT]
- Baselines and results: [INSERT]

Example output:

Drove 7 cross-functional initiatives in 2025 that moved net revenue retention from 104% to 118% for the mid-market segment, with gross logo churn falling from 7.2% to 4.1% as a downstream effect. (If asked in the loop: 1) What was the largest single driver? 2) How did you split credit with CS? 3) What is the next 12-month target?)

Pro tips for use:

For Director+ roles, this is the bullet. Save it for the top of the experience section.
Always pair the metric with a denominator and a time window. “NRR 118% in mid-market, FY2025” beats “improved NRR.”
If you have to choose between NRR and gross retention, choose gross retention - it is harder to game and more respected.

Prompt 19 - The “business model shift” bullet

Purpose: When a PM changes the business model, that is a career-defining bullet. This prompt is built for those rare projects.

Prompt text:

You are a PM resume writer for Director, VP, and C-suite-adjacent PMs. I will describe a business model shift I led or co-led (e.g., seat → usage, one-time → subscription, free → paid, acquisition → expansion-led). Produce 1 achievement-based bullet that shows the magnitude without leaking confidential numbers.

Frame:
[Action verb] the [shift: pricing model, GTM motion, business model, packaging] for [product / company / segment], moving [primary KPI: ARR, NRR, take-rate, gross margin, payback period] in [directional band] and reshaping [secondary effect: sales cycle, win rate, support cost, CAC payback, expansion velocity] within [time window].

Rules:
- 1 sentence, 25–32 words.
- Use banded language for revenue. "Low double digits" or "in the high single digits" is honest and senior.
- Name the framework: usage-based pricing, value-based pricing, land-and-expand, product-led growth (PLG), sales-led, hybrid, open-core.
- Output a "Board-level prep" note - the 2 or 3 questions a board member would ask about this kind of shift.

Inputs:
- Shift: [INSERT]
- Primary KPI: [INSERT]
- Secondary effect: [INSERT]
- Time window: [INSERT]
- Framework: [INSERT]

Example output:

Co-led the shift from seat-based pricing to a usage-based hybrid across 3 product lines, lifting blended ARR in the low double digits and shortening median sales cycle by 11 days within 2 quarters. (Board-level prep: 1) What was the impact on existing contracts? 2) Did churn change? 3) What was the pricing-page experiment plan?)

Pro tips for use:

“Co-led” is a great word when you shared the work with a CFO, Head of Sales, or Head of CX. Be honest about it.
If the shift was tied to PLG, mention the self-serve funnel conversion. That is the number the board actually cares about.
For C-suite-adjacent PMs, you can stack two shifts into a single bullet to show a 2-year arc.

Prompt 20 - The “team / org impact” bullet

Purpose: Senior PMs build teams and shape orgs, not just products. This prompt makes that visible.

Prompt text:

You are a senior PM resume editor. I will describe a way I shaped the PM team, the product org, or a cross-functional team. Produce 1 achievement-based bullet.

Frame:
[Action verb] [the team or org change: hiring, onboarding, leveling framework, ritual, review process, planning cadence, offsite, charter, OKR rollout] for [N PMs / N cross-functional partners], moving [team-level metric: cycle time, decision quality, retention, hiring bar, planning predictability] from [baseline] → [result] within [time window].

Rules:
- 1 sentence, 25–32 words.
- "Improved team velocity" without a number is not a bullet. Pick a real team-level metric.
- Mention the artifact: leveling doc in Notion, planning template in Coda or Productboard, hiring rubric in Greenhouse or Ashby, retro doc in Confluence.
- Output a "Director interview prep" note.

Inputs:
- Team / org change: [INSERT]
- Scope: [INSERT]
- Artifact: [INSERT]
- Team-level metric: [INSERT]
- Baseline: [INSERT]
- Result: [INSERT]
- Time window: [INSERT]

Example output:

Rolled out a quarterly OKR + planning ritual using Productboard and Coda across 6 PMs and 4 cross-functional partners, cutting planning time from 4 weeks to 5 days and lifting the percentage of committed OKRs shipped from 58% to 81% in 2 quarters. (Director interview prep: be ready to talk about what you cut, what you added, and what you would change in the next iteration of the ritual.)

Pro tips for use:

“OKRs shipped” is a stronger team-level metric than “team velocity.” It implies you actually finished the work.
For Director of Product resumes, this bullet is non-negotiable. For Group PM, it is a strong differentiator.
If you do not have a team-level metric, “time saved” is your friend. “Cut planning time from 4 weeks to 5 days” is a credible win.

Prompt 21 - The “cross-company initiative” bullet

Purpose: Some PMs shape the whole company. This prompt makes those projects visible.

Prompt text:

You are a PM resume editor for Group PM, Director, and VP-level PMs. I will describe a cross-company initiative I co-led (e.g., AI transformation, platform consolidation, security revamp, pricing reset, brand refresh, support-to-self-serve pivot). Produce 1 achievement-based bullet that shows the company-level impact.

Frame:
[Action verb] [the company-level initiative] by [the PM move: authoring the strategy doc, running the pilot, sequencing the rollout, instrumenting the migration, defining the success metric], partnering with [N] teams across [functions], and moving [company-level metric] by [% or $] within [time window].

Rules:
- 1 sentence, 25–32 words.
- "Company-level metric" means revenue, cost, NRR, gross margin, employee NPS, customer NPS, security posture, or a regulator-facing SLA. Not a feature-level metric.
- Name the artifact: company memo, board deck, planning ritual, governance model, RACI.
- Output a "VP interview prep" note.

Inputs:
- Initiative: [INSERT]
- PM move: [INSERT]
- Teams: [INSERT]
- Company-level metric: [INSERT]
- Time window: [INSERT]

Example output:

Co-led the company-wide AI productivity initiative by authoring the strategy doc and running the 3-team pilot, partnering with Eng, GTM, and Finance, lifting qualified pipeline by 14% and reducing average handle time by 22% in the first 6 months. (VP interview prep: the VP will ask how you set the success metric, what you cut from the scope, and how you handled the org change.)

Pro tips for use:

For VP Product resumes, this is the bullet. Pick the initiative that was the biggest lift.
“Co-led” is your friend. Real cross-company work is almost always co-led.
If the company metric is sensitive, use a directional phrase and flag it in a sidebar.

Prompt 22 - The “year-in-review” composite bullet

Purpose: Save the most ambitious prompt for last. This one turns a full year of work into a single, dense bullet that reads like a press release for your PM career.

Prompt text:

You are a senior PM resume editor. I will give you a list of 4–6 wins from a single year or quarter. Compress them into 1 achievement-based bullet for the top of a PM resume experience section.

Frame:
[Action verb] [N] initiatives across [M] cross-functional teams in [year / quarter], shipping [N launches] that moved [primary metric: NRR, ARR, retention, activation] from [baseline] → [result], [secondary metric] from [baseline] → [result], and [tertiary metric: e.g., team velocity, customer NPS, latency] from [baseline] → [result], while [1 cost-savings or org-level move].

Rules:
- 1 sentence, 30–40 words. This is the longest bullet allowed on a PM resume.
- 3 metrics is the sweet spot. More is a wall of numbers; fewer is thin.
- The "while [org-level move]" clause is the senior signal. Examples: "while leveling up the PM team from 3 to 6," "while onboarding a new VP Product," "while cutting tech debt by 30%."
- Output a "If asked, walk me through this year" prep note - the 5-minute narrative arc for an interview.

Inputs:
- Year / quarter: [INSERT]
- Initiatives: [INSERT]
- Launches: [INSERT]
- Primary metric: [INSERT]
- Secondary metric: [INSERT]
- Tertiary metric: [INSERT]
- Org-level move: [INSERT]

Example output:

Led 9 initiatives across 4 squads in 2025, shipping 4 product launches that moved NRR from 104% to 118%, lifted activation 8 points, and cut p95 latency 60%, while leveling up the PM team from 3 to 6 and rolling out a new OKR ritual across the org. (If asked, walk me through this year: open with the highest-leverage launch, name the deprioritization, walk through the OKR ritual rollout, close with the PM team build-out.)

Pro tips for use:

This bullet belongs at the very top of your most recent role, above all other bullets. The reader sees it first.
Keep it to 30–40 words. Past 40, the eye gives up.
The “while [org-level move]” clause is the differentiator. Without it, the bullet reads like a Senior PM, not a Director.

Comparison table: prompt categories vs. PM competency vs. output

This table maps each of the 5 prompt categories in this article to the PM competency it strengthens, the kind of output you should expect, and a few tool names you can use to actually build the bullet. Use it to pick the right prompt for the right gap in your resume.

Category (Prompt #)	PM competency it strengthens	Typical output you get	Tools to verify the numbers	Best for resume section
Discovery & outcome (1–5)	Customer insight, JTBD, opportunity sizing	Quantified insight-to-action bullets	Dovetail, Maze, UserTesting, Hotjar, FullStory, Pendo, Amplitude, Mixpanel	”Experience” - first 2 bullets of each role
Strategy & roadmap (6–9)	Strategic thinking, prioritization, trade-offs	Bets shipped, OKRs, kill decisions	Productboard, Aha!, Roadmunk, Height, Notion, Coda, Asana, Linear, Confluence	”Experience” - strategy line per role
Launch & GTM (10–13)	Launch rigor, GTM craft, growth mechanics	From 0-to-1, activation, monetization, retention bullets	Statsig, GrowthBook, Optimizely, LaunchDarkly, Pendo, Appcues, Vitally, Gainsight, Planhat, ChurnZero	”Experience” - flagship launch bullets
Cross-functional & stakeholder (14–17)	Influence, alignment, partnership	Exec alignment, eng / design / data partnership bullets	Figma, FigJam, Pitch, Notion, Coda, Confluence, Linear, Jira, Shortcut	”Experience” - middle bullets per role
Metric & KPI (18–22)	Business judgment, senior signal	Single-number, business model, team, company, year-in-review bullets	Looker, Mode, Hex, Tableau, Snowflake, BigQuery, dbt, Amplitude, Mixpanel, Heap, PostHog	”Experience” - top bullet of current role, plus “Summary”

A quick note on how to read the table: if your resume is heavy on discovery and thin on launch, start with prompts 10 and 11. If it is heavy on launch and thin on strategy, run prompts 6 and 7 first. Senior PM loops almost always ask about deprioritization (Prompt 7) and exec alignment (Prompt 14). Director+ loops almost always ask about team and org impact (Prompts 20 and 21) and the year-in-review composite (Prompt 22).

A 14-day “resume bullet refresh” workflow

I will be honest: I do not rewrite a resume in one sitting. I rewrite it in waves. Below is the 14-day workflow I have used for the last two job searches and that I have watched several PM friends use. You can collapse it to a weekend, but the 14-day version is the one that actually sticks.

Day 1 - Inventory the wins. Open a Notion or Coda doc. List every project you shipped in the last 24 months. For each, write 1 line on the problem, 1 line on what you did, and 1 line on what changed. Do not write bullets yet. Mine the data.

Day 2 - Pull the numbers. For each project, open Looker, Mixpanel, Amplitude, Mode, Hex, or your data tool of choice. Find at least one number for each: a percentage, a dollar figure, a time saved, a count of users, a count of teams. If you cannot find a number, talk to your EM, your designer, your CSM, or your finance partner. 80% of the time, the number exists somewhere.

Day 3 - Run discovery prompts. Use Prompts 1, 2, 4, and 5. These are your discovery-to-bullet translators. Draft 3 bullets per recent project.

Day 4 - Run strategy prompts. Use Prompts 6, 7, 8, and 9. Pick 1 strategy bullet, 1 deprioritization bullet, and 1 platform or OKR bullet per recent role.

Day 5 - Run launch prompts. Use Prompts 10, 11, 12, and 13. Pick the single biggest launch and the single biggest monetization or retention move. Draft 2 bullets per launch.

Day 6 - Run stakeholder prompts. Use Prompts 14, 15, 16, and 17. Pick 1 exec alignment bullet, 1 engineering partnership bullet, and 1 design or data partnership bullet per recent role.

Day 7 - Run metric prompts. Use Prompts 18, 19, 20, 21, and 22. The composite year-in-review bullet (Prompt 22) goes at the very top of your most recent role. The single-number bullet (Prompt 18) goes second.

Day 8 - Score with tools. Upload your draft to Resume Worded, Jobscan, and Simplify. They will flag weak verbs, missing keywords, and ATS issues in under a minute. Fix the top 5 issues.

Day 9 - First human pass. Send the resume to 2 PM friends and 1 EM friend. Ask them to read only the first 2 bullets of your most recent role. If they cannot tell what you shipped in 7 seconds, those bullets are not sharp enough.

Day 10 - Tailor to a real job ad. Pick one target job ad. Use Prompts 1, 6, 10, 14, 18, and 22 again, but with the job ad’s keywords substituted in. Save this as your “primary tailored version.”

Day 11 - Tailor to 2 more job ads. Repeat Day 10 for 2 more roles. You now have 3 tailored versions. Never mass-send the same resume.

Day 12 - Practice the deprioritization story. Take Prompt 7 and turn it into a 2-minute STAR story. This is the single most common senior PM interview question.

Day 13 - Practice the year-in-review story. Take Prompt 22 and turn it into a 5-minute narrative. This is the most common Director+ opening question.

Day 14 - Final polish. Update your LinkedIn “About” section using the same prompts. Update your “Experience” section. Send a 1-line Loom to your 3 friends thanking them and asking for referrals if they know anyone at your target companies.

A quick note on ChatGPT model choice: the prompts above are model-agnostic. ChatGPT (GPT-4o or GPT-5 class), Claude, and Gemini all work. I have tested these prompts on all three. The model that gives me the most consistent PM-bullet output is whichever model I am also using for my day job - context-switching costs add up.

Common mistakes to avoid

I have made most of these mistakes myself. Here is the full list, in order of how often they tank otherwise strong PM resumes.

Starting bullets with “Responsible for.” This is the #1 resume sin in any role, and it is rampant on PM resumes. Swap it for a past-tense action verb every time.
Using “Managed” or “Led” as the only verb. These are fine as one of many verbs, but a resume full of “Managed the X team, led the Y launch, managed the Z roadmap” reads like a job description, not a track record.
Listing responsibilities instead of outcomes. “Owned the checkout roadmap” is a responsibility. “Redefined the checkout roadmap to a single-step guest flow, lifting paid conversion 18%” is an outcome.
Inventing numbers. A confident-sounding 18% that you cannot defend in an interview will end your loop fast. If you do not know the number, write “[INSERT]” and come back to it.
Stuffing keywords. Yes, you need keywords. No, you should not write “Agile, Scrum, JIRA, Confluence, Notion, Asana, Linear, Productboard, Aha!, Mixpanel, Amplitude, Looker, Tableau, SQL, Python, Figma, Miro” in a comma cloud. Use the tools in the bullets, in context.
Burying the lede. The first 2 bullets of your most recent role are the only ones a recruiter will read in the 7-second scan. Put your biggest, most quantified wins there.
Writing a one-page resume when you have 7+ years of experience. This signals you are either junior or hiding something. 77% of employers say seasoned workers should not use a single-page resume (Zety, Nov 12, 2025).
Tailoring the bullets but not the summary. The summary is the second thing the recruiter reads. It has to mention the company and the focus area of the role.
Forgetting the deprioritization story. “What did you kill and why?” is the senior PM question. If you cannot answer it, the resume is not ready for senior loops.
Skipping the AI guardrails. Always review what ChatGPT produced. Always correct the hallucinations. Always make sure the final bullet sounds like you, not like a corporate template.

Final word

A PM resume is not a list of what you did. It is a list of what changed because of what you did. The 22 ChatGPT prompts for product manager achievement-based bullets above are designed to force that reframe, one section at a time. Use the discovery prompts to surface your insight. Use the strategy prompts to show your judgment. Use the launch prompts to show your execution. Use the stakeholder prompts to show your influence. Use the metric prompts to show your business sense. Then compress it all into a 2-page PDF, run it through Resume Worded and Jobscan, send it to 3 friends, and start applying.

One last thing: Lenny Rachitsky’s March 24, 2026 newsletter on the state of the product job market in early 2026 made it clear that PM and eng job openings are the highest they have been in years, and AI roles are exploding. The demand is real, the competition is real, and the bar is real. The PMs who win this cycle will be the ones whose resumes read like a track record of shipped outcomes, not a recap of job descriptions. Go make yours one of them.

If you use these prompts, send me a Loom or a DM with the before-and-after. I read every one.

Reader disclosure & educational-purpose notice

This page is published by SuperFreshAI for general informational and educational purposes only. By reading it, you agree to the points below.

Editorial independence. All reviews, guides, and recommendations are written by our editorial team based on hands-on use. Some links on this site are affiliate links, and some articles are produced as partner content — both are always clearly labeled. Our editorial conclusions are never shaped by partners or affiliates.
Not professional advice. Nothing on this page constitutes legal, financial, medical, tax, or other professional advice. AI tools, pricing, and capabilities change quickly — always verify current information with the tool's official documentation before making a decision.
Educational purpose only. The content here is intended to help you learn about AI tools and workflows. It is not a guarantee of results, performance, fitness for a particular purpose, or suitability for your specific situation. Your results may vary.
No warranties. The site and its content are provided on an "as is" and "as available" basis. We make no warranties, express or implied, about accuracy, completeness, reliability, or availability. See our Terms and Privacy for the full legal terms.
Your responsibility. You are responsible for how you use the information on this page, including any decisions you make based on it. Always do your own research and consult a qualified professional when appropriate.
Affiliate & partner disclosure. When you click certain outbound links, we may earn a commission at no extra cost to you. When a piece of content is produced as partner content, it is labeled at the top of the page. See our Editorial Policy for the full standards we follow.

By continuing to read, you acknowledge that you have read and understood this notice.

22 ChatGPT prompts for product managers to write achievement-based bullet points

Why 9 in 10 PM bullets still say “owned roadmap” (with 2026 data)

The 4-part PM achievement-bullet anatomy

SECTION 1 - Discovery & outcome prompts (prompts 1–5)

Prompt 1 - The “discovery to dollars” translator

Prompt 2 - The “user research to shipped feature” bridge

Prompt 3 - The “experimentation engine” bullet

Prompt 4 - The “NPS / CSAT / support deflection” bullet

Prompt 5 - The “insight to roadmap” bullet

SECTION 2 - Strategy & roadmap prompts (prompts 6–9)

Prompt 6 - The “vision to roadmap” bullet

Prompt 7 - The “deprioritization” bullet (yes, really)

Prompt 8 - The “platform / internal tool” bullet

Prompt 9 - The “OKR / KPI” bullet

SECTION 3 - Launch & GTM prompts (prompts 10–13)

Prompt 10 - The “launch from 0 to 1” bullet

Prompt 11 - The “growth / activation” bullet

Prompt 12 - The “monetization / pricing” bullet

Prompt 13 - The “retention / churn” bullet

SECTION 4 - Cross-functional & stakeholder prompts (prompts 14–17)

Prompt 14 - The “exec alignment” bullet

Prompt 15 - The “engineering partnership” bullet

Prompt 16 - The “design partnership” bullet

Prompt 17 - The “data and analytics partnership” bullet

SECTION 5 - Metric & KPI prompts (prompts 18–22)

Prompt 18 - The “single number that mattered” bullet

Prompt 19 - The “business model shift” bullet

Prompt 20 - The “team / org impact” bullet

Prompt 21 - The “cross-company initiative” bullet

Prompt 22 - The “year-in-review” composite bullet

Comparison table: prompt categories vs. PM competency vs. output

People Also Ask: 10 PM resume questions, answered fast

A 14-day “resume bullet refresh” workflow

Common mistakes to avoid

Final word

SuperFresh AI

43 ChatGPT prompts for non-native English speakers to polish interview answers

41 ChatGPT prompts for SaaS founders in San Francisco to map local partnership opportunities

How to Detect AI-Generated Content

What Is the Best AI Tool for Writing?

AI Newsletter Writing Guide

Get practical AI insights in your inbox