Free tool
Find the keywords your resume is missing for this job.
Paste the job description. Paste your resume. RoleWorth shows you which JD-required terms are absent — and pairs each gap with a proof point from your evidence so you can add it honestly, never invented. Lexical gaps get rewrite suggestions; real gaps get flagged so you know which roles to skip.
FAQ
Is keyword stuffing safe?
No. ATS systems and human reviewers both penalise unsupported claims. The gap checker only suggests adding keywords that are backed by real proof points from your evidence library — if you can't defend the bullet in an interview, it does not go on the resume.
Why are my keywords not matching?
Three common reasons: (1) you used the synonym the JD did not — 'managed' vs 'led', 'Postgres' vs 'PostgreSQL'; (2) the keyword is in a section the parser deprioritises (image-only logo, header, footer); (3) the JD required term is a tool you have used but never named on the resume. The gap report tells you which of the three applies.
How honest is 'add it honestly'?
Each suggested keyword is paired with a proof point you have already entered (project, metric, scope). If no proof exists, the gap is flagged as 'real gap, not lexical' — meaning the issue is not your resume, it is the role-fit. We will not invent experience.
Product proof
See the product surface behind the claim.
Each page carries the matching RoleWorth surface in a glass-framed proof card: the radar, extension overlay, ATS matrix, review queue, dashboard, or package flow behind the promise.
The public promise, visible above the fold: score first, package second, approve before anything leaves.
Batch scan, ghost-risk skipped count, high-worth jobs, and Apply/Maybe/Skip routing in one product surface.