Where is the evidence?
A term in a skills list is not the same as a term inside something you describe doing. This tells the difference — and where something is missing it asks what you actually did rather than writing it for you.
Where the evidence is, and where it is not
A term in a skills list is not the same as a term in something you describe doing. This tells the difference, and it will not write anything for you.
Coverage
Missing from your resume
Each shows the job’s own words and asks a question. Nothing here is text to paste.
Listed but not evidenced
Well evidenced
Shown, and deliberately not scored
How matching works
Concepts, not strings. "K8s" and "Kubernetes" are one requirement. "AWS" and "Azure" are not, however adjacent they look — treating related tools as equivalent would tell you that you meet a requirement you do not.
Where the evidence sits changes what it is worth. A term inside an achievement counts fully; the same term in a skills list counts for a third. A resume can be made to match any job by padding a list, and rewarding that would make this tool worse than useless.
Requirement level follows the nearest heading. A term under "Nice to have" is not required, however emphatically it is phrased.
Location, work authorisation, travel and schedule are shown and never scored. Matching a person against those would build discrimination into the result.
Why the skills list is the weakest place to put something
A skills list costs nothing to extend. That is exactly why it persuades nobody: a reader who sees "Kubernetes" in a list and nothing about it anywhere else has learned that you know the word.
The same term inside "led the migration of 40 services to Kubernetes, cutting deploy time from 45 minutes to 8" is evidence. It has a scale, a context and a result, and it survives the interview question that follows.
The gap list is a set of questions
Where something is missing, this shows the job's own wording and asks what you actually did. It does not offer a sentence to paste, and that is deliberate.
A resume is a document you will be interviewed against. Anything inserted because a tool suggested it is something you will be asked about by someone who does the work.
Related is not equivalent
Plenty of tools treat AWS and Azure, or React and Angular, as interchangeable evidence. They are not, and a candidate told otherwise walks into a technical conversation believing they are covered.
Genuine naming variants are matched — K8s is Kubernetes, PMP is Project Management Professional. Different products are kept apart, deliberately and by an explicit list.
What is left out of the score, and why
Work authorisation, location, travel and schedule requirements are surfaced because they matter practically. They are excluded from any coverage figure, because scoring a person against them is the mechanism by which a hiring tool discriminates.