The Resume Gap Analyzer: Turn a Job Description Into a List of What's Missing From Your Resume

Why this prompt matters
Most qualified candidates get filtered before a human ever reads their resume, not because they lack the experience but because it was never written down in a way that matches the posting's language — recruiters report spending under 10 seconds on an initial resume scan, so an unquantified bullet or a missing exact-phrase keyword can silently cost an interview the candidate was actually qualified for.
What we use it for
A mid-level product manager found a job posting closing in 48 hours and needs to know exactly which resume bullets to rewrite and which requirements are genuine gaps, instead of guessing what to emphasize under deadline pressure.
Prompt
Role: You are a senior technical recruiter who has screened thousands of resumes against job descriptions and knows exactly what makes a candidate get filtered out before a human ever reads their application. Context: Job description: [PASTE THE FULL JOB POSTING] Current resume: [PASTE YOUR CURRENT RESUME TEXT] Years of relevant experience you actually have: [E.G. "6 years, but 2 were in a different industry"] The one requirement in this posting you're most worried about: [E.G. "they want 5 years of Kubernetes and I have 2"] Task: Compare the resume against the job description line by line and identify every meaningful gap — not just missing keywords, but missing evidence, missing quantification, and missing seniority signals. Constraints: - Do not suggest lying or fabricating experience. Every fix must be a reframing or surfacing of experience the candidate actually has, described in [ADDITIONAL CONTEXT FIELD FOR UNLISTED EXPERIENCE, e.g. "I also led a 3-person team informally for 6 months"] if provided. - Distinguish between a "hard gap" (a requirement with zero corresponding experience) and a "visibility gap" (experience exists but isn't on the resume or isn't quantified). - For each hard gap, suggest how to address it in a cover letter or interview rather than inventing resume content. - For each visibility gap, rewrite the specific resume bullet using the XYZ formula (Accomplished X, as measured by Y, by doing Z). - Flag which gaps are likely ATS keyword filters (exact phrase matching) versus human-reviewer judgment calls. Output Format: 1. **Hard Gaps** — a numbered list of requirements with no corresponding experience, each with a one-line suggestion for how to address it outside the resume. 2. **Visibility Gaps** — a numbered list of requirements the candidate likely meets but the resume doesn't show, each with: the original bullet (if one exists), the rewritten XYZ-format bullet, and which job requirement it now addresses. 3. **ATS Keyword Risk** — a short list of exact phrases from the posting that are likely automated filters and are currently missing from the resume verbatim. 4. **Bottom Line** — one paragraph stating whether this is a strong, borderline, or weak match, and the single highest-leverage change to make before submitting.
Result
Input used: Job posting for a Senior Product Manager role requiring "5+ years PM experience," "proven track record leading cross-functional teams," "experience with A/B testing and experimentation frameworks," and "direct experience presenting to executive leadership." Candidate has 4 years as a PM plus 2 years as a senior analyst, led informal project teams but never had direct reports, ran dozens of A/B tests but didn't document them on the resume, and presented to a VP twice but it's not mentioned anywhere.
1. Hard Gaps
- "5+ years PM experience" — you have 4 years as a PM + 2 as a senior analyst in an adjacent function. Address in cover letter: frame the analyst years as "PM-adjacent" experience that directly informed product decisions, and be ready to discuss this directly if asked in a screening call rather than letting the resume imply a gap silently.
2. Visibility Gaps
- Requirement: "proven track record leading cross-functional teams"
Original bullet: "Worked with engineering and design on the checkout redesign project"
Rewritten (XYZ): "Led a cross-functional team of 6 (3 engineers, 2 designers, 1 analyst) to ship a checkout redesign, reducing cart abandonment by 14% over two quarters"
Addresses: directly answers the leadership requirement with a quantified outcome instead of a passive description. - Requirement: "experience with A/B testing and experimentation frameworks"
Original bullet: not present on resume at all
Rewritten (XYZ): "Designed and ran 30+ A/B tests across pricing and onboarding flows using Optimizely, identifying a pricing page variant that lifted conversion by 9%"
Addresses: this experience exists but was never written down — it's the single most fixable gap in this resume. - Requirement: "direct experience presenting to executive leadership"
Original bullet: not present
Rewritten (XYZ): "Presented quarterly roadmap and A/B test results directly to VP of Product twice, securing budget approval for a 3-person team expansion"
Addresses: converts a two-time occurrence most candidates would consider "not enough to mention" into direct proof of the exact requirement.
3. ATS Keyword Risk: "cross-functional," "A/B testing," and "experimentation framework" do not appear verbatim anywhere in the current resume — if this posting runs through an ATS with exact-phrase matching, the application may be filtered before a human sees it, independent of actual qualification.
Bottom Line: This is a borderline-to-strong match on paper once the visibility gaps are fixed — the candidate has real evidence for nearly every requirement, it simply was never written down. The highest-leverage single change is adding the A/B testing bullet, since it's both a hard keyword match and the most concrete, quantifiable evidence available.
Most resume advice focuses on formatting and keywords, which misses the actual failure mode: candidates have the experience a posting asks for, but their resume never says so in a way a recruiter or an ATS can detect in a ten-second scan. This prompt is built around that distinction specifically — separating a "hard gap" (experience that genuinely doesn't exist) from a "visibility gap" (experience that exists but was never written down, quantified, or phrased to match the posting).
The constraint against fabricating experience is deliberate and non-negotiable. The prompt can only reframe or surface experience the candidate already has — it cannot invent a skill, a team size, or a result. That's why the context field for "additional unlisted experience" matters: it gives the model something real to work with instead of incentivizing it to pad bullets with vague superlatives that don't survive a follow-up interview question.
The ATS Keyword Risk section exists because exact-phrase filtering is a real, mechanical failure mode that has nothing to do with qualification. A candidate can be fully qualified and still get filtered out because the posting says "cross-functional" and the resume says "worked with other teams." Catching that mismatch before submission is a five-minute fix with an outsized return.
The XYZ reformatting (Accomplished X, measured by Y, by doing Z) isn't decorative structure — it forces every rewritten bullet to include a number. A bullet without a measurable outcome reads as an activity description; the same bullet with a number reads as a result, and results are what get candidates past the first filter.