Résumé keywords, and what a checker can honestly tell you

Almost every article about applicant tracking systems is about keywords, and most of them promise a match score. This page is about what can honestly be said, which is less than that and more useful.

Two different questions

The ATS résumé checker here answers two questions and keeps them apart. The ATS score asks whether a parser can read your document and whether the evidence is there to read; it takes no job description and counts no keywords. The Job match, which you open after the check and fill with a posting, asks what that posting requires and which of those requirements a line of your résumé actually shows.

Neither number is an employer's. Employer systems weight terms in ways nobody outside the company can see, and they differ between systems and between roles. What the job match prints is its own arithmetic, row by row, so you can see exactly what it counted.

What the job match counts

• Required and preferred skills. Read from the posting's requirements, with "Go or Java" counted as one requirement and "Scala is a plus" counted as preferred.
• Evidence, not mentions. A skill is found when it stands in your résumé, and the report shows the line it stands on.
• Years, degree and title. Your dated career against the years asked, your degree against the one named, and your role family against the posting's.

Keyword coverage, the plain count of the posting's terms on your page, is reported beside these and never scored, because repeating a term is not evidence of the work.

Where keywords genuinely matter

• A recruiter searching a database. They type a tool, a certification or a job title and read what comes back. The word has to be on your page.
• Systems that do match text. Some employer systems rank or filter on terms from the posting. You cannot see the rules, and having the right words for work you did costs nothing.
• The human reader. A hiring manager scanning for the thing they need is running the same search with their eyes.

How to choose them

Take the posting's own words for the work you have actually done. If they say "incident response" and you wrote "on-call rota", use their phrase. If they name a tool you have used, name it the way they spell it. Put each term inside a sentence that shows the work, because a term in context is credible and a term in a list is not. The tailoring guide is a twenty-minute pass that does exactly this.

What not to do

No keyword block at the bottom of the page. No white text, no hidden layers, no repeated terms in a font size nobody reads; the extraction takes everything, and what it takes is what gets seen. No terms for work you have not done, which is the same trade as an invented number and fails at the same moment.

What to do with a missing skill

If the job match lists a skill as asked for and not found, there are two honest answers. If you have done the work, write the line that shows it, in the posting's own words, and check again. If you have not, leave it off; the cover letter builder names such a requirement in one plain sentence rather than claiming it, which is a better answer than a word on the page with nothing behind it.

Terms that are genuinely worth checking

• Job titles. The industry's word for your role, not your employer's internal grade name.
• Tools and systems. Spelled as the posting spells them, including version numbers where they matter.
• Certifications. The issuer's own name for the certificate, which is what a search will use.
• Methods and standards. The named framework, regulation or process, written out once in full.

Each of these belongs inside a sentence that shows the work. A term in a list is a claim; the same term in a line about what you did with it is evidence, and the skills guide covers how a list is read.

What to do instead of chasing a match score

Spend the time on the three things that are true whoever reads the file: a layout that extracts in order, headings that are recognised, and experience lines that carry figures. Then use the job match for what it is good at, which is showing the requirement you forgot to evidence. A higher match rate earned by adding true lines is worth having; one earned by adding words is not.