skills / other

review-resume

what it does

Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“Here's my resume and the job I want. What should I change before I apply?”

Source material given with the request

JOB POSTING: Senior Product Manager, Payments, at Lumora (fictional) - 5+ years of product management, at least 2 in payments or fintech - Own the card acceptance and payouts roadmap - Run experiments to improve payment conversion - Comfortable writing SQL to answer your own questions - Work with risk and compliance teams RESUME: Priya Anand, priya.anand@example.com Senior Product Manager, Tallis Travel, 2022 - present - Led redesign of hotel search results; increased bookings per search by 12% - Launched loyalty points program to 1.4M members - Built SQL dashboards used by 30 PMs to track funnel metrics Product Manager, Tallis Travel, 2019 - 2022 - Managed the mobile app settings and notifications - Owned the checkout and payments flow; added two local payment methods in Brazil and India, raising payment success rate from 81% to 89% - Worked with fraud team to cut chargebacks by 30%
with the skill
Hi Priya, Thanks for sharing this. You have what Lumora is asking for: real payments ownership with a measurable result (81% to 89% payment success), fraud partnership, and SQL. The problem is that the most relevant evidence is buried under less relevant material. Here are the changes I'd make, highest impact first. ## Top 4 changes 1. **Lead with payments.** The role requires 2+ years in payments or fintech, but your payments work is the second bullet of your older role, below "Managed the mobile app settings and notifications." A recruiter skimming for 10 seconds could miss it. 2. **Expand the payments work into 2-3 bullets** and put them first, or add a summary that surfaces them. 3. **Add the missing keywords, only where true:** experiments, conversion, payouts, card acceptance, risk, compliance. 4. **Turn activity bullets into outcome bullets.** Several say what you did but not what changed. ## Detailed feedback **1. Professional summary** I don't see one, and it's your best place to say "payments PM" right away. Something like: > "Senior Product Manager with 6+ years in travel commerce, including [X years] owning checkout and payments. Raised payment success from 81% to 89% across Brazil and India, cut chargebacks 30% with fraud teams, and built SQL tooling used by 30 PMs." Fill in the real number of years you owned payments. That figure matters against the "2 years in payments" requirement. **2. Personal pronouns**
Show the rest (55 more lines)
None. Keep it that way. **3. Concision** Three bullets per role and a likely one-page resume is fine. You have room for 1-2 more bullets in each role, so use them for payments and experimentation. I'd cut or heavily shrink "Managed the mobile app settings and notifications," which has no outcome and no relevance to this job. **4. XYZ+S formula** Your strongest bullet is the payment methods one, since it has an outcome, a metric, an action, and specific markets. The others are thinner: - *"Launched loyalty points program to 1.4M members"*: what was the business result? Try: "Launched loyalty points program to 1.4M members, driving [repeat booking rate / retention / revenue lift] by [Y%]." - *"Built SQL dashboards used by 30 PMs to track funnel metrics"*: what did this change? Try: "...enabling PMs to [find and fix X / cut reporting time by Y hours/week]." - *"Worked with fraud team to cut chargebacks by 30%"*: what did you do? Try: "Partnered with Fraud to cut chargebacks 30% by [rule changes / 3DS rollout / new verification step], while [holding approval rate flat / limiting conversion loss to Z%]." The tradeoff between fraud and conversion is exactly what this role deals with. - *"Increased bookings per search by 12%"*: if this was tested, say so: "...validated through [N] A/B tests." **5. Email and contact info** `priya.anand@example.com` follows the right format. Make sure the header also has phone, LinkedIn, and location. **6. Tailoring to Lumora** | Requirement | Where it shows up now | Suggestion | |---|---|---| | 5+ years PM | Yes (2019 to present) | Fine | | 2+ years payments | One bullet | Elevate it and state the duration | | Card acceptance and payouts roadmap | Not visible | Add only if you've done it. Local payment methods are adjacent to card acceptance, but not the same, so don't overstate. | | Payment conversion experiments | Partly (success rate) | Add experiment details: tests run, hypotheses, results | | SQL | Yes | Tie it to a payments decision, not just dashboards | | Risk and compliance | Fraud bullet | Name the work, e.g. PCI, SCA/3DS, KYC, or local regulations in Brazil and India, if you handled them | If you have no payouts experience, that's a real gap. Don't hide it. Cover it with the nearest honest equivalent (for example, refunds, settlement, or partner payment flows) or address it in a cover letter or interview. **7. Product and business skills** Your skills mostly come through in the bullets, which is good. The missing pieces are experimentation, prioritization (how you chose Brazil and India), and cross-functional work with Engineering, Legal, or Finance. A single added clause on how you picked those markets would show strategy. **8. Structure and order** I only see the experience section, so I can't check the rest. The order should be: contact info, summary, experience, education, certifications, optional skills. Also, you've listed Tallis Travel twice. Group both roles under one company header to show the promotion, and use month-year dates (e.g., "Mar 2022 - Present"). **9. Early-career advice** Not applicable. You're well past this stage. **10. Standard titles and language** Your titles are clear and standard. Tighten the verbs: "Managed," "Worked with," and "Owned" are inconsistent and some are weak. Prefer "Led," "Launched," "Partnered," and "Reduced." ## Sample reordered experience section (fill in the brackets) **Tallis Travel** *Senior Product Manager* | [Mon YYYY] - Present - Led hotel search redesign, increasing bookings per search 12% across [N] A/B tests - Launched loyalty points program to 1.4M members, lifting [metric] by [Y%] - Built SQL funnel dashboards adopted by 30 PMs, [outcome] *Product Manager* | [Mon YYYY] - [Mon YYYY] - Owned checkout and payments roadmap; added local payment methods in Brazil and India, raising payment success from 81% to 89% [and revenue by $X] - Partnered with Fraud [and Compliance] to cut chargebacks 30% by [action], [without hurting conversion] - [Add: payments experiment or SQL analysis that drove a decision] You're a strong match on the core of the role. Once the payments story is front and center and the vaguer bullets have outcomes, this should read as a clear fit. If you send me the revised version, I'm happy to look again.
without
# Resume feedback for Lumora's Senior PM, Payments role ## The main problem Your most relevant experience (payments) is buried in your older role, and your current role has no payments content. A recruiter skimming the top will see hotel search and loyalty, not payments. Your goal is to make the payments story impossible to miss. ## Changes, in priority order **1. Add a short summary at the top that frames you as payments-relevant** > Product manager with 5+ years in consumer products, including 3 years owning checkout and payments across multiple markets. Experienced in improving payment conversion, working with fraud/risk teams, and using SQL and experimentation to drive decisions. Adjust "3 years" to the real duration of your payments ownership. The posting requires 2+ years in payments or fintech, so make that clear and accurate. **2. Move payments to the top of the 2019-2022 role and expand it** Right now it's the second bullet under "mobile app settings and notifications," which undersells it. Lead with it, and add detail: > Owned checkout and payments roadmap for [X markets / $Y annual volume]; launched two local payment methods (Brazil, India) via [A/B tests/phased rollout], lifting payment success rate from 81% to 89% and adding an estimated $[Z] in annual revenue. Add the revenue or volume figure if you have it. It shows scale, which a Senior role will care about. **3. Strengthen the fraud/risk bullet** "Worked with fraud team" is vague. The job explicitly asks for risk and compliance collaboration.
Show the rest (27 more lines)
> Partnered with fraud and risk teams to [introduce X rule/3DS flow/vendor], cutting chargebacks 30% (from [baseline] to [new]) while keeping conversion [flat/improved]. Mention compliance only if you really did it (e.g., PCI, SCA/PSD2, local regulations in India or Brazil). India especially tends to involve regulatory work. **4. Show experimentation explicitly** The posting wants someone who runs experiments to improve payment conversion. You likely did, but the resume doesn't say so. Add "A/B tested" or "ran experiments on..." where true, including for the hotel search result. **5. Tie SQL to answering your own questions** "Built SQL dashboards used by 30 PMs" shows impact but reads as a tooling contribution. Add a bullet or clause like: "Wrote SQL to analyze payment funnel drop-off by method, issuer, and country, which informed the local payment method prioritization." Only include it if true. **6. Trim or shorten less relevant content** - Cut "mobile app settings and notifications" or reduce it to a few words. - Keep the loyalty program to one line. It's a nice scale signal but not relevant here. **7. Use the posting's language** Where accurate, use terms like *payment conversion*, *authorization rate*, *card acceptance*, *payouts*, and *roadmap ownership*. These help with ATS keyword matching and with recruiters scanning quickly. ## Gaps to address honestly - **Card acceptance and payouts:** Your resume mentions local payment methods but not cards or payouts. If you've worked on card flows, acquirer or PSP relationships, or partner/hotel payouts (common in travel), add it. If not, address it in your cover letter by explaining how your experience transfers. - **Fintech vs. travel:** You've done payments inside a travel company, not at a fintech. That's fine, but a one-line cover letter note about why you want to move to a payments-first company will help. - **Your current role has no payments:** If you still touch payments in any way, include it. If not, be ready to explain in interviews why you moved to search and loyalty. ## Small stuff - Add your location and LinkedIn alongside your email. - Make sure every bullet has a metric where possible, and the format is consistent (action, what, result). If you share the details I flagged as placeholders (volumes, timelines, tools, what you did on fraud), I can draft the revised bullets for you.

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 3 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 3 Nov 2026

The tasks

written by Carte Blanche
senior-pm-general-review

“Can you review my resume? I'm applying for senior PM roles at B2B SaaS companies.”

summary-only

“Just rewrite my summary line. The rest of the resume is fine, I don't need feedback on it.”

tailor-to-posting

“Here's my resume and the job I want. What should I change before I apply?”

teacher-to-apm

“I'm a high school teacher trying to get an associate PM job. Can you look at my resume and tell me what to fix?”

too-long-resume

“Recruiters aren't calling me back. Is my resume too long? Here's my most recent job, it's the biggest section.”

Install

Download the .zip and unzip it. Put its files, in a folder named review-resume, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.