Can AI replace CVMatchScore?
The core loop, resume plus job posting into an LLM holding a scoring rubric, is one prompt and an afternoon, and for improving one resume against one posting it genuinely works. The honest gap is calibration: a rubric you wrote today measures today's mood, two runs of the same resume can disagree, and a 72 means nothing without a baseline of scored applications behind it. Fine as a mirror, thin as a measuring stick.
01What it costs
Checked Aug 10, 2026 · source: cvmatchscore.com. 3 full reports in the first 7 days, all 19 parameters, no credit card.
02Could AI build it for you?
The core job: Extract text from the resume PDF, send it with the job description to an LLM holding a fixed scoring rubric, get structured JSON scores per criterion with quoted evidence, render a Markdown report.
What a working version needs:
- OpenAI or Anthropic API key
- pdf-parse or pdfplumber for resume text extraction
- a written rubric with a 0-10 definition per criterion
- a few real resume and posting pairs to sanity-check the scores
One prompt gets you the score. What it does not get you is the same score tomorrow.
03What you'd give up
- a calibrated rubric that scores the same resume the same way twice
- 50+ language support tested per parameter
- DOC, DOCX, and RTF parsing beyond PDF
- improvement plans and tailored cover letters built from the same analysis
- scores comparable across weeks of applications
At 49 USD a year it is priced below the hassle of maintaining your own: job seekers pay for stable scores they can track across applications, cover letters generated from the same pass, and not burning API credits mid job hunt.
04Free and cheaper alternatives
A local resume-vs-posting matcher that runs against Ollama, so the scoring stays on your machine; you install it, it does the job, and nobody bills you.
resumematcher.fyi →05The build prompt
Paste this into an AI coding tool (such as Claude, ChatGPT, Lovable or Replit) to build your own version.
Build me a local resume match scorer to replace CVMatchScore. Requirements: - A Node 22 CLI: `match score resume.pdf job.txt` prints a score table and writes a Markdown report to reports/YYYY-MM-DD-<company>.md. - Extract resume text with pdf-parse; accept .txt and .md for the job posting. - Keep the rubric in rubric.json: 10 criteria (skills overlap, seniority fit, domain experience, quantified achievements, education, keyword coverage, employment gaps, clarity, length, ATS-safety), each with a 0-10 definition and a weight. - One Anthropic structured-outputs call scores all criteria at once and must quote the resume line that justifies each score, no unquoted claims. - A second cheap pass lists the 10 most important posting keywords missing from the resume and where each could honestly fit. - Weighted total out of 100, computed in code from rubric.json, not by the model. - Store every run in SQLite via better-sqlite3: date, company, total, and the per-criterion JSON, so `match history` shows my scores over time. - API key from .env. No accounts, no telemetry, the resume never leaves my machine except the API call. - Out of scope: cover letter generation, DOC/DOCX parsing, multi-language support, and recruiter-style bulk ranking. - README: setup, cost per run, and a warning that scores are only comparable within one rubric version, so bump a version field in rubric.json when I edit it.
06Open-source starting points
- pdfplumber: reliable PDF text extraction, the unglamorous half of every resume tool
- Resume-Matcher (repo): open-source resume vs job description matcher, a working reference for the whole loop
App prices, verdicts, alternatives and build prompts are adapted from Can I Vibecode It? (MIT License, © 2026 Rob Hallam). Each price shows the date it was checked and its source. Prices change; confirm on the vendor's site before you decide.
Get new verdicts in your inbox.
One short email when new verdicts land: what AI can now do for you, and what it still gets wrong. No spam. Unsubscribe anytime.