Resume Job Description Matcher
Paste any job posting to see your match percentage, the skills and vocabulary you are missing, and specific changes to make. No AI API, no upload, no account.
Nothing to analyze yet
Add your details in the builder, or load the sample resume to see what this tool finds.
How the match percentage works
Three components, weighted by how much each actually predicts a match, and rescaled so a posting that exercises only one of them cannot hand out free points for the others.
- Skills (60%) — canonical skills resolved through an alias table, so "K8s" in the posting matches "Kubernetes" on your resume. Hard skills are weighted more than soft ones.
- Domain terms (30%) — repeated content words outside the skill taxonomy, which is how field-specific vocabulary gets counted without us having to enumerate every profession.
- Job title (10%) — whether the posting's inferred title appears in your resume at all.
Terms in the requirements block count for more
The matcher detects headings like "Requirements", "Qualifications" and "What you'll need", and weights terms appearing under them 1.5x. A skill named once in the company boilerplate is not the same as one named in the requirements list.
What to do with the result
Add missing hard skills you genuinely have. Mirror the employer's exact wording where you use a synonym. Put the job title in your headline. Then rewrite two bullets so the most important missing terms appear in a proven context rather than only in a list.
Do not add skills you cannot discuss. Passing a filter you cannot defend in an interview costs you more than the match gained.
Frequently asked questions
- What match percentage should I be aiming for?
- Around 60-75% is a realistic target, and 100% is a warning sign rather than a goal. A posting lists everything an ideal candidate might have, including items the hiring manager does not actually expect. Matching every one usually means you have pasted the posting back at them, which reads as keyword stuffing to a person and adds skills you may be asked to demonstrate.
- Is adding keywords from the job description the same as keyword stuffing?
- No, as long as each keyword sits inside a claim that is true. "Kubernetes" listed among your skills because you have run clusters is matching; the same word repeated in a hidden block, or added to a role where you never touched it, is stuffing. The difference is whether you could talk about it for two minutes in an interview.
- Does the matcher understand that "K8s" and "Kubernetes" are the same thing?
- Yes. It uses a hand-curated skill taxonomy with an alias table, so common abbreviations, spellings and product names resolve to the same skill. It also filters job-description boilerplate — without that step every posting’s top keyword is "experience" and the report is useless.
- Is the job description I paste sent anywhere?
- No. The matching runs entirely in your browser against a local dictionary, so the posting never leaves your device — which also means it works with no connection. Neither the posting nor your resume is transmitted at any point.