“Why am I not getting interviews?” is usually a gap problem: the roles you want ask for things your résumé doesn’t show. Instead of guessing, have your Claude Code agent measure it — score your résumé against a stack of real postings for your target role and tell you exactly which skills keep coming up missing.
analyze_job_match on each, aggregates the missing keywords, and ranks them by how often they appear — turning a vague worry into a concrete "learn these three, surface these two" list. Runs on your own model, so it’s $0.Scoring against a single posting tells you about that posting. Scoring against many tells you about the market: the skills that show up in 15 of 20 “senior platform engineer” jobs are the ones actually gating the role. A one-off match can mislead; the aggregate doesn’t.
Here are 18 job links for "senior platform engineer" roles I want.
For each, score my résumé with analyze_job_match and collect the
missing keywords. Then:
- Rank the missing skills by how many postings want them.
- Split into "I have this but it's not on my résumé" vs
"I'd need to learn/build this."
- Recommend the 3 highest-leverage things to fix first.
The agent calls ResumeAlign for the scrape + score on each job, then applies its own judgment to cluster and prioritize. You get a frequency-ranked gap list, not a wall of keywords.
After you update your base résumé, ask the agent to re-score against the same 18 jobs and show the before/after. Watching the average match score climb — and the gap list shrink — tells you the rewrite worked before you send a single application.
Once your résumé matches the market, let the agent tailor and apply to the strong matches — or schedule it. Because the scoring and tailoring run on your Claude Code subscription, analyzing 20 jobs and re-scoring costs you nothing per run.
Why score against many jobs instead of one?
A single posting tells you about that posting; many postings tell you about the role. Skills that appear in most listings for your target role are the ones actually gating it. Aggregating across 15–20 jobs turns a vague worry into a ranked, actionable gap list.
What’s the difference between a surfacing gap and a real gap?
A surfacing gap is experience you have but didn’t put on the page — fix it instantly by rewriting truthfully. A real gap is something you haven’t done yet — that’s a learning target, ideally paired with a build-now project so it lands on your résumé soon.