Resume gaps vs questions: why the counts do not always match

The short answer

You are seeing different stages of the same system. Gap detection happens first. Prompt selection happens second. Final coverage happens after answers and rewrite.

Because each stage has a different goal, counts can change without indicating a product error.

Stage 1: requirement gaps

The job analyzer extracts requirements and marks areas where your current resume appears weak or missing.

This stage is intentionally broad. It surfaces potential issues before deciding which ones need user prompts.

Stage 2: question selection

The question generator prioritizes high-impact gaps and combines related requirements to avoid repetitive prompts.

• One question can close multiple related gaps.
• Low-confidence requirements can be deprioritized.
• Prompt count is constrained so the workflow stays practical.

Stage 3: final coverage after tailoring

After answers are applied, the resume is re-evaluated. Some earlier gaps disappear because your evidence now covers them directly.

This is why job-level gap counts and export-page keyword coverage are related, but not expected to be identical line-by-line.

What to do when mismatch feels suspicious

Audit by priority, not by total count.

• Check whether top requirements now appear in summary, bullets, or skills.
• Review the What Changed panel for concrete edits.
• Re-tailor only if high-priority requirements remain unaddressed.

CTA: run a fresh role-fit check

If in doubt, run match analysis first, then tailor with stronger examples for the unresolved areas.