How the extractor works
The tool tokenizes the job description, removes English stopwords (the, of, with, etc.), filters out filler verbs (work, help, support), and ranks the remaining tokens by frequency. Words that match a curated dictionary of recognized skills (programming languages, ATS-tracked tools, certifications, methodologies) get a boost so they surface first.
It does not call any backend. The job description never leaves your browser. There is no upload, no log, no cookie record of the text you paste.
What to do with the keywords
For each recognized skill in the result: check whether your resume already contains that exact string in the Skills section or a recent role bullet. If it's missing and you've actually used the skill, add it. If you haven't used it, leave it off — fabricated skills cost you offers when they get verified.
For the frequent role-specific terms: these are usually the verbs and nouns that describe the work. Make sure your bullets use the same language. \"Built and shipped\" beats \"helped develop\" if the posting says \"build and ship.\"
Limits of keyword extraction
A keyword extractor is a starting point, not a finishing line. It can't tell you which keywords are mandatory vs nice-to-have. It can't read between the lines (\"strong communicator\" implies things the literal string doesn't capture). And it can't tell you the structure your resume should be in to actually score well — that's what a full ATS-tailoring tool does.
Use this to find the gaps. Use ATSHack's $1 tailor to fix them.
Related
What is an ATS? · Glossary · Keywords that get interviews · How to pass ATS screening