The Resume Gap Analyzer: Turn a Job Description Into a Prioritized List of Resume Fixes
Why this prompt matters
Applicant tracking systems and the recruiters using them reject unclear or keyword-mismatched resumes before a human ever reads the actual experience behind them. A resume that could pass with two rewritten bullets and one added line often gets silently filtered instead — not because the candidate lacks the experience, but because it was never legible on the page.
What we use it for
You found a job posting for a role that's a stretch — one level above your current title — and you have 45 minutes before the application closes tonight. You need to know fast whether your resume as-is will get filtered out, and what to fix first if it will.
Prompt
Role: Act as a skeptical hiring manager and resume editor who has screened thousands of resumes for this type of role. Context: - Job description: [PASTE FULL JOB DESCRIPTION] - My current resume: [PASTE CURRENT RESUME TEXT] - Years of experience: [YOUR YEARS OF EXPERIENCE] - Target seniority level: [e.g., MID-LEVEL, SENIOR, STAFF] Task: Compare my resume against the job description line by line. Identify every requirement or preferred qualification in the job description that my resume does not clearly address, and rank these gaps by how likely they are to get my resume rejected in an initial screen. For each of my 5 weakest existing bullet points (weak = vague, no numbers, no clear outcome), rewrite it using the XYZ formula: "Accomplished [X] as measured by [Y], by doing [Z]." Flag any claim in my resume that sounds inflated or unverifiable given the rest of my background. Constraints: - Do not invent metrics or achievements I haven't provided — if a bullet lacks a number, note "needs a real metric" rather than making one up. - Distinguish between "must-have" gaps (will likely cause rejection) and "nice-to-have" gaps (minor scoring impact). - Keep rewritten bullets under 25 words each. - If my resume is actually a strong match, say so explicitly rather than inventing problems to seem thorough. Output Format: ## Resume vs. Job Description Gap Analysis **Must-have gaps** (ranked by rejection risk, one line each with why it matters) **Nice-to-have gaps** (lower priority, one line each) **5 rewritten bullets** (XYZ formula, original vs. rewritten side by side) **Inflated or unverifiable claims** (if any — otherwise state "none flagged") **Overall match verdict** (strong / moderate / weak fit, one sentence why)
Result
Resume vs. Job Description Gap Analysis: Senior Product Manager, Growth
Must-have gaps
1. The posting requires "experience owning a P&L or revenue target directly" — your resume shows feature ownership but no revenue or budget accountability language. High rejection risk; this is typically a hard screening filter for "Senior" titles.
2. Requires "experience managing or mentoring junior PMs" — not mentioned anywhere in your resume, even though you noted mentoring two associate PMs informally. This needs to be added explicitly, not assumed.
3. Requires "A/B testing and experimentation at scale" — you have one bullet about a redesign but no mention of experimentation frameworks or statistical significance, which growth PM screeners specifically scan for.
Nice-to-have gaps
1. SQL proficiency is listed as preferred — not mentioned in your resume even though your analytics bullet implies some familiarity.
2. A named growth framework (e.g., AARRR) isn't mentioned; minor scoring impact only.
5 rewritten bullets
1. Original: "Worked on onboarding flow redesign." → Rewritten: "Increased onboarding completion 18% as measured by 30-day activation rate, by redesigning the signup flow's first three screens."
2. Original: "Collaborated with engineering on feature launches." → Rewritten: "Shipped 6 features in 2 quarters as measured by on-time delivery rate, by running weekly cross-functional prioritization syncs."
3. Original: "Helped improve retention." → Rewritten: "Needs a real metric — quantify the retention change and timeframe before using this bullet."
4. Original: "Managed roadmap for core product." → Rewritten: "Prioritized a 12-item roadmap as measured by stakeholder sign-off time (cut from 3 weeks to 1), by introducing a weighted scoring rubric."
5. Original: "Led company-wide growth strategy." → Rewritten: "Needs scope correction — see inflated claim below before rewriting."
Inflated or unverifiable claims
"Led company-wide growth strategy" may not hold up under interview scrutiny given your title was individual-contributor PM. Consider "contributed to" or naming the actual scope (e.g., one product line) unless you can defend "led" under direct questioning.
Overall match verdict
Moderate fit. Your day-to-day PM experience is solid, but the resume as written reads one level below "Senior" because it's missing the P&L ownership and mentorship language this posting explicitly screens for. Fixing gaps 1 and 2 before you submit will meaningfully change how this resume screens.
Most resume advice tells you to "quantify your achievements" without telling you which achievements the employer is actually screening for. This prompt fixes that by forcing a direct, line-by-line comparison between your resume and the specific job description in front of you — not generic resume best practices, but what this particular posting will filter on.
Why this structure works
The gap analysis is split into must-have and nice-to-have, because not all missing keywords carry equal weight — a missing P&L requirement can silently disqualify a "Senior" application while a missing nice-to-have barely moves the needle. Treating them the same wastes your limited editing time on low-impact fixes.
The XYZ rewrite is capped at your 5 weakest bullets rather than the whole resume, because a wall of rewrites is harder to actually implement than five sharp, prioritized ones — and the instruction to write "needs a real metric" instead of inventing one is deliberate. A fabricated number that falls apart in an interview is worse than an honest gap.
The inflated-claims check exists because resumes optimized purely for keyword density tend to drift into language a candidate can't defend under questioning — "led" when you contributed, "managed" when you coordinated. Catching that before submission is cheaper than catching it in an interview.
Use case
You found a job posting for a role that's a stretch — one level above your current title — and you have 45 minutes before the application closes tonight. You need to know fast whether your resume as-is will get filtered out, and what to fix first if it will.
Why it matters
Applicant tracking systems and the recruiters using them reject unclear or keyword-mismatched resumes before a human ever reads the actual experience behind them. A resume that could pass with two rewritten bullets and one added line often gets silently filtered instead — not because the candidate lacks the experience, but because it was never legible on the page.