Skip to content
← All features
Feature / measure

See the keywords you matched, and the ones you missed.

Most resume scoring tools hand you a single number and a cheerful "improve your score" button. We give you the list. Here are the keywords that came out of the JD. Here are the ones your resume already matches. Here are the ones it does not. What you do next is up to you.

resimay.ai/features/keyword-match

How to use keyword match breakdown.

3 steps. Each one runs in seconds. Scroll in order.

  1. 01

    Parse the JD into keywords

    The parser already pulls key_skills and ats_keywords from the posting. Both lists feed the match step.

  2. 02

    Cross-check your resume

    The tailored resume (or your master, if you just want a quick read) is tokenized and compared against the JD keyword set. Variants are normalized so "React" and "ReactJS" count as the same match.

  3. 03

    See matched, missing, and the gap you care about

    The breakdown lists every keyword by name, bucketed matched or missing. You decide whether a missing skill is a real gap to learn, something to surface on your resume because you have used it, or noise to leave off.

In action

A real breakdown on a senior frontend role

Now you can make an informed call. GraphQL is worth adding if you have used it anywhere. Micro-frontends might be a real gap worth flagging in your cover note. Storybook you probably just forgot to list. The list is the advice.

Opaque score (how most tools show it)
Your resume matches this job 82%.

Improve your score: add more keywords.
Named breakdown (how we show it)
Matched:
  React · Next.js · TypeScript · Jest · Playwright
  Figma · Core Web Vitals · WCAG 2.1 AA · design system

Missing:
  GraphQL
  Storybook
  micro-frontends
  A/B testing
Under the hood

The mechanics nobody hides.

You should be able to tell how a feature works before you trust it with your job search.

01

Exact match plus controlled variants

We do literal string matching because that is how most ATS parsers work. On top of that we normalize a small controlled set of variants (React/ReactJS, JavaScript/JS, k8s/Kubernetes) so you do not get dinged for casing or abbreviation.

02

Required-skills prioritised

The JD parser prioritises required skills and ATS keywords from the body of the posting. The match list focuses on what the role actually needs, not on incidental phrasing that happens to appear in the surrounding copy.

03

Free vs Pro

Free accounts see the match percentage, the full matched list, and the top five missing keywords with a "+ N more (Pro)" indicator showing how many more exist. Pro Weekly, Pro, and Pro Quarterly see the full missing list. The trim happens server-side so opening devtools cannot bypass it.

04

Updates live with each tailor

Every time you regenerate a tailored resume, the breakdown recomputes. Watch the number climb as you add real skills. If it does not move, the gap is real.

Guardrails

What it deliberately does not do.

Honest limits read as trust signals. Hiding them does the opposite.

  • Match is string-based, not semantic. If the JD says "container orchestration" and your resume says "Kubernetes," we do not auto-link those unless the JD also lists Kubernetes.
  • We do not publish a proprietary score. The list is the truth. A percent on top of it is a rounding step.
  • We do not advise adding keywords you have not earned. The list shows gaps. Filling a gap is your call.
Questions

Common questions.

If your question isn't here, email support and you'll hear back from the founder.

Why not give me a 0 to 100 score?

We can report a match percent if you want it. The list is what actually tells you what to do, and a percent alone does not. The point is fixing the resume, not improving the score.

How does this compare to Jobscan?

Jobscan scores a resume against a JD. We do that plus generate a tailored resume, track the application, and analyze rejections when they come in. See the full comparison at /compare/jobscan.

Does a perfect match mean I will get an interview?

No. Keyword match gets your resume past the first filter. After that a human reads it. The breakdown handles the part of the funnel you can measure. The rest is story, timing, and luck.

Will this work with my existing resume, without tailoring?

Yes. You can run a keyword match on a master resume against any pasted JD. You will see what is already there and what is missing before you decide whether to tailor.

Pairs with

AI resume tailor

Every saved job gets its own resume, rewritten to mirror the posting. Validator catches dropped roles. Keyword matches verified server-side. Zero fabrication.

Rejection analysis

Mark a job as denied. Get an AI read on the likely gap, what the resume missed, and what to do differently next time.

Job description parser

Drop a raw job posting. Get structured company, role, skills, and ATS keywords back in under two seconds.

Stop reading about it. Run it on a real job.

Create a free account in under a minute. First job tracked, first tailored resume, and first keyword breakdown all happen inside the onboarding flow.

Create a free account →Try the demo firstAll features

No credit card · 2-minute setup · Cancel anytime