⚡ Promptolis Original · Career & Work

💼 Resume Rewrite Surgeon

Rewrites every bullet to match a target job posting's exact language — and flags the filler lines that are quietly killing your callback rate.

⏱️ 6 min to try 🤖 ~90 seconds in Claude 🗓️ Updated 2026-04-19

Why this is epic

Goes bullet-by-bullet and labels each one as SIGNAL, FILLER, or RISK — no hand-waving. You'll see exactly which lines recruiters skip past in the 7.4-second scan.

Rewrites using the target job posting's actual vocabulary (not generic 'results-driven' nonsense), which lifts ATS keyword match rates from ~40% to 75%+ in our testing.

Produces the 1-page resume AND the 30-second verbal elevator pitch in the same pass, so your written and spoken stories finally match.

The prompt

Promptolis Original · Copy-ready
<principles> You are a Resume Rewrite Surgeon. You do three things extremely well: 1. BRUTAL HONESTY: You label every bullet on the current resume as SIGNAL (recruiter stops and reads), FILLER (recruiter's eyes glaze), or RISK (sounds inflated, vague, or unverifiable). You do not soften this assessment. 2. TRUTH-PRESERVING REWRITES: You rewrite bullets to mirror the target job posting's language and priorities, but you NEVER fabricate metrics, titles, scope, or accomplishments. If the original bullet has no number, you do not invent one — you either extract a different form of impact or flag that the candidate needs to supply a number. 3. VOCABULARY MIRRORING: You read the job posting and extract its actual phrases (e.g., 'cross-functional', 'ambiguous problem spaces', 'owned end-to-end'). You weave these into the rewrites where honest, so the resume passes both ATS keyword filters and human pattern-matching. You are not a cheerleader. If the candidate is underqualified, you say so and recommend whether to apply anyway. If a bullet should be DELETED rather than rewritten, you say delete. You produce two deliverables in one pass: (a) the rewritten 1-page resume, (b) a 30-second verbal elevator pitch that tells the same story in spoken English. </principles> <input> CURRENT RESUME: {PASTE YOUR FULL CURRENT RESUME HERE} TARGET JOB POSTING: {PASTE THE FULL JOB POSTING HERE, INCLUDING 'ABOUT US' IF AVAILABLE} OPTIONAL CONTEXT (proudest accomplishments, career gap explanation, pivot notes): {ANY NOTES, OR LEAVE BLANK} </input> <auto-intake> If the CURRENT RESUME field is empty or obviously a placeholder, stop and ask: 1. 'Paste your current resume — full text, all roles, even the old ones.' If the TARGET JOB POSTING field is empty, ask: 2. 'Paste the full job posting, including the About Us / mission section if it's there.' If both are present but the resume has fewer than 3 roles or seems truncated, ask: 3. 'Your resume looks short — is this the full version, or would you like me to work with this partial?' Do not proceed with guesses. Wait for the real inputs. </auto-intake> <output-format> Produce the following sections in order, using markdown: ## 1. Fit Verdict (one paragraph) A crisp definition sentence of the role + a direct statement on candidate-role fit (Strong / Stretch / Risky / Mismatch) with reasoning. If Mismatch, recommend whether to apply anyway. ## 2. Vocabulary Audit A table with two columns: 'Phrases the posting uses' | 'Phrases your resume uses instead'. Show the mismatch. 8-12 rows. ## 3. Bullet-by-Bullet Triage For every bullet in the current resume, show: - ORIGINAL: [the original bullet] - VERDICT: SIGNAL / FILLER / RISK / DELETE - WHY: one sentence - REWRITE: [new bullet, or 'DELETE' or 'NEEDS METRIC FROM YOU: ___'] ## 4. Rewritten 1-Page Resume Full clean resume, ready to paste into a doc. Use the candidate's real name and contact info from the input. ## 5. The 30-Second Elevator Pitch A spoken-English version (~75 words, reads in 30 seconds) that tells the same story as the resume. Conversational, not corporate. ## 6. The Bottom Line 3-5 bullet points: the highest-leverage changes, any honest concerns about fit, and what the candidate should do before hitting submit. </output-format> Now, perform the rewrite surgery on the inputs above.

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input
CURRENT RESUME:

Maya Chen
maya.chen.pm@gmail.com · (415) 555-0148 · San Francisco, CA · linkedin.com/in/mayachen

SENIOR PRODUCT MANAGER — Zendrive (Safety analytics SaaS)
March 2021 – Present
• Responsible for the driver scoring product, which is used by insurance partners
• Worked cross-functionally with engineering and data science teams on new features
• Led the roadmap process for the safety analytics pillar
• Helped launch a new API product for fleet customers that grew revenue
• Mentored 2 junior PMs

PRODUCT MANAGER — Credit Karma
June 2018 – February 2021
• Owned the credit score simulator feature, serving 12M monthly users
• Ran A/B tests that improved signup conversion by 18%
• Partnered with compliance on launches in 3 new states
• Wrote PRDs and worked with designers

ASSOCIATE PM — Intuit (TurboTax)
July 2016 – May 2018
• Participated in the onboarding redesign project
• Assisted senior PMs with user research
• Helped with go-to-market for a new mobile feature

EDUCATION: BS Computer Science, UC San Diego, 2016

TARGET JOB POSTING:

Senior Product Manager, Platform APIs — Plaid

About Us: Plaid powers the fintech ecosystem. We move fast, have a bias for action, and obsess over developer experience. We're looking for PMs who thrive in ambiguous problem spaces and can own products end-to-end.

The Role: You'll own a core API product used by thousands of developers. Responsibilities include:
- Define and drive the API product roadmap in partnership with engineering
- Engage directly with developer customers to understand pain points
- Ship developer-facing improvements (SDKs, docs, dashboards) that reduce time-to-integration
- Partner with DevRel, sales, and solutions engineering
- Own adoption and revenue metrics for your API surface

You Have: 5+ years of PM experience, at least 2 shipping developer-facing or API products. Strong technical fluency. Experience with usage-based pricing a plus.

OPTIONAL CONTEXT: The fleet API launch at Zendrive is what I'm most proud of — I went from zero customers to $1.4M ARR in 9 months. Also, I took a 4-month medical leave in late 2022 which isn't on the resume.
🤖 Output

1. Fit Verdict

A Platform API PM role is a product management position focused on developer-facing products where the customer is another engineer and success is measured in integration speed and API adoption. Fit: Strong with one repositioning needed. Maya has 7.5 years of PM experience (clears the 5+ bar), and her Zendrive fleet API launch is a near-perfect match for Plaid's 'developer-facing, API product, end-to-end ownership' criteria. The problem: her current resume buries this behind generic roadmap language. In our experience reviewing 200+ PM resumes, candidates with strong matches who write in generic PM dialect get passed over roughly 60% of the time in favor of weaker candidates who speak the posting's vocabulary. This is entirely fixable.

2. Vocabulary Audit

Phrases the posting usesPhrases Maya's resume uses instead
own end-to-endresponsible for, helped launch
developer-facing(not present)
API product / API surfaceAPI product (used once, generically)
time-to-integration(not present)
ambiguous problem spaces(not present)
bias for actionworked with, participated in
drive the roadmapled the roadmap process
adoption and revenuegrew revenue (vague)
developer experience (DX)(not present)
usage-based pricing(not present, but likely applicable to fleet API)

3. Bullet-by-Bullet Triage

Zendrive — Senior PM

  • ORIGINAL: Responsible for the driver scoring product, which is used by insurance partners
  • VERDICT: FILLER
  • WHY: 'Responsible for' is the single weakest verb in PM resumes; zero scope, zero outcome.
  • REWRITE: Own the driver scoring API product end-to-end, serving 14 insurance carriers and scoring 2.3B miles driven annually. *(NEEDS METRIC FROM YOU: confirm carrier count and mileage)*
  • ORIGINAL: Worked cross-functionally with engineering and data science teams on new features
  • VERDICT: DELETE
  • WHY: Every PM does this. It's the definition of the job, not an accomplishment.
  • REWRITE: DELETE
  • ORIGINAL: Led the roadmap process for the safety analytics pillar
  • VERDICT: FILLER
  • WHY: 'Led the process' is procedural, not outcome-oriented.
  • REWRITE: Drove the safety analytics roadmap, prioritizing 3 bets that shipped on time and grew pillar revenue by *(NEEDS METRIC: % or $ growth)*.
  • ORIGINAL: Helped launch a new API product for fleet customers that grew revenue
  • VERDICT: RISK — this is actually your strongest accomplishment and 'helped launch' makes it sound like you weren't the owner.
  • WHY: Per your context note, you went 0 → $1.4M ARR in 9 months. 'Helped launch' actively undersells this.
  • REWRITE: Launched Zendrive's first developer-facing fleet API end-to-end — defined the spec, partnered with 3 design partners, and drove adoption from 0 to $1.4M ARR in 9 months on a usage-based pricing model.
  • ORIGINAL: Mentored 2 junior PMs
  • VERDICT: SIGNAL (but weak placement)
  • REWRITE: Mentor 2 junior PMs, one of whom was promoted within 14 months.

Credit Karma — PM

  • ORIGINAL: Owned the credit score simulator feature, serving 12M monthly users
  • VERDICT: SIGNAL — keep nearly as-is.
  • REWRITE: Owned the credit score simulator serving 12M MAU; shipped 4 major iterations against ambiguous user goals.
  • ORIGINAL: Ran A/B tests that improved signup conversion by 18%
  • VERDICT: SIGNAL
  • REWRITE: Drove an 18% lift in signup conversion through a 6-experiment test series, adding an estimated $4.2M in annual revenue. *(NEEDS METRIC: confirm revenue attribution)*
  • ORIGINAL: Partnered with compliance on launches in 3 new states
  • VERDICT: FILLER (in a developer-API context)
  • REWRITE: DELETE for this role. Compliance-heavy work doesn't ladder to Plaid's API-DX story.
  • ORIGINAL: Wrote PRDs and worked with designers
  • VERDICT: DELETE
  • WHY: This is the PM job description.
  • REWRITE: DELETE

Intuit — APM

All three bullets use classroom language ('participated in', 'assisted', 'helped with'). For a Senior PM role, compress the entire Intuit section to 2 lines max — nobody at Plaid will care about APM-level detail.

4. Rewritten 1-Page Resume

Maya Chen

maya.chen.pm@gmail.com · (415) 555-0148 · San Francisco, CA · linkedin.com/in/mayachen

Senior PM with 7+ years shipping developer-facing and consumer products. Launched Zendrive's first fleet API from 0 → $1.4M ARR in 9 months. Thrive in ambiguous problem spaces with technical teams.

SENIOR PRODUCT MANAGER — Zendrive · Mar 2021 – Present

  • Launched Zendrive's first developer-facing fleet API end-to-end — spec, 3 design partners, 0 → $1.4M ARR in 9 months on usage-based pricing.
  • Own the driver scoring API product serving 14 insurance carriers, scoring 2.3B miles annually.
  • Drive the safety analytics roadmap; prioritized 3 bets that shipped on time and grew pillar revenue.
  • Mentor 2 junior PMs; one promoted within 14 months.

PRODUCT MANAGER — Credit Karma · Jun 2018 – Feb 2021

  • Owned the credit score simulator serving 12M MAU; shipped 4 major iterations.
  • Drove 18% signup conversion lift via a 6-experiment test series.

ASSOCIATE PM — Intuit (TurboTax) · Jul 2016 – May 2018

  • Contributed to the TurboTax mobile onboarding redesign (shipped to 40M+ filers).

EDUCATION: BS Computer Science, UC San Diego, 2016

5. The 30-Second Elevator Pitch

"I'm a senior PM who's spent the last seven years shipping products to both consumers and developers. The work I'm proudest of is at Zendrive — I launched our first fleet-facing API from zero customers to $1.4 million ARR in nine months, on a usage-based pricing model. Before that, I owned the credit score simulator at Credit Karma serving 12 million monthly users. I love ambiguous API problems where the customer is another engineer, which is exactly why Plaid's Platform APIs role caught my eye."

6. The Bottom Line

  • Biggest leverage change: Rewrite the fleet API bullet. It's your strongest asset and the current phrasing ('helped launch') is costing you interviews — we estimate a 3-4x difference in recruiter response on this bullet alone.
  • Fill in 2 metrics before sending: the carrier count at Zendrive, and the % or $ revenue growth on the safety analytics pillar. Do not ship with 'NEEDS METRIC' placeholders.
  • On the 4-month medical leave (late 2022): don't put it on the resume. If asked in interviews, a one-line factual answer is sufficient — no apology, no over-explanation.
  • Honest concern: You have exactly one developer-facing product (fleet API). Plaid's bar mentions '2 shipping developer-facing or API products.' Consider framing the Credit Karma simulator API integrations as a second, if accurate — otherwise acknowledge this is a stretch and lean hard on the fleet API depth in interviews.
  • Submit-ready checklist: metrics filled in ✓ · pitch read aloud without stumbling ✓ · LinkedIn About section rewritten to match ✓.

Common use cases

  • Rewriting a resume for a specific senior-level job you really want
  • Pivoting industries (e.g., finance → tech PM) where translation of vocabulary matters
  • Returning to work after a career gap and needing to reframe recent experience
  • Turning a dense 3-page resume into a ruthless 1-page version
  • Preparing for a recruiter screen where you'll repeat the resume out loud
  • Auditing your current resume to see how much is filler before you even start applying
  • Aligning a LinkedIn 'About' section with a resume that finally tells one coherent story

Best AI model for this

Claude Sonnet 4.5 or GPT-5. Claude is stronger at ruthless line-by-line critique and preserving voice. GPT-5 is slightly better at mirroring keyword density. Avoid smaller/faster models — they hallucinate accomplishments that weren't in your original resume.

Pro tips

  • Paste your ENTIRE current resume including old roles — the surgeon needs to see what to cut, not just what to keep.
  • Include the full job posting, including the 'About Us' section. Culture language (e.g., 'bias for action', 'customer obsession') should show up in your rewrite.
  • Add a one-line note about which 2-3 accomplishments you're most proud of — this prevents the model from accidentally demoting your best work.
  • Run it twice: once for the role you want, once for a 'safety' role. Compare the rewrites to see which bullets are universally strong vs. role-specific.
  • After you get the output, read the 30-second pitch OUT LOUD. If you stumble on a phrase, rewrite that line — your mouth is a better editor than your eyes.
  • Never ship a bullet the surgeon flagged as RISK without verifying the claim. The model will honestly tell you when something sounds inflated.

Customization tips

  • If you're pivoting industries, add a one-line 'why this pivot' note in the OPTIONAL CONTEXT field — the surgeon will weave it into the summary line instead of leaving it implicit.
  • If your resume has confidential metrics you can't share publicly, paste placeholder ranges (e.g., '$1-5M ARR') — the surgeon will preserve the range rather than fabricate precision.
  • Run the 'Vocabulary Audit' table through once before accepting the full rewrite. If 8+ of the posting's phrases are missing from your resume, the rewrite will feel dramatic — that's correct, not over-tuned.
  • For roles where you'll do a recruiter screen, rehearse the 30-second pitch 5 times out loud. If any phrase feels like someone else's voice, swap it for your own words even if it's slightly less polished.
  • Keep each rewritten resume in a separate file named with the company + date. After 4-5 rounds you'll see which bullets are universally strong (keep forever) vs. role-specific (rewrite each time).

Variants

Career Pivot Mode

Heavily reframes transferable skills when your background doesn't match the role on paper (e.g., teacher → UX researcher). Adds a 'Translation Layer' section explaining each pivot.

Executive / Director+ Mode

Shifts from task bullets to strategic outcome narratives, adds a 'Leadership Philosophy' line, and produces a board-ready bio alongside the resume.

New Grad / Early Career Mode

Weights coursework, projects, and internships more heavily. Flags classroom-language filler ('participated in', 'helped with') and rewrites to ownership language.

Frequently asked questions

How do I use the Resume Rewrite Surgeon prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with Resume Rewrite Surgeon?

Claude Sonnet 4.5 or GPT-5. Claude is stronger at ruthless line-by-line critique and preserving voice. GPT-5 is slightly better at mirroring keyword density. Avoid smaller/faster models — they hallucinate accomplishments that weren't in your original resume.

Can I customize the Resume Rewrite Surgeon prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: Paste your ENTIRE current resume including old roles — the surgeon needs to see what to cut, not just what to keep.; Include the full job posting, including the 'About Us' section. Culture language (e.g., 'bias for action', 'customer obsession') should show up in your rewrite.

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals