How to read a job posting for keywords, without keyword stuffing

Keyword advice has a credibility problem, and it is deserved. The genre is full of instructions to paste the job description into a word cloud, or to hide terms in white text behind the margin, or to append a "Key Skills" block containing every phrase from the posting. The first is imprecise, the second is detected trivially and gets you blocked, and the third is visible to any human who reads the page.

But underneath the bad advice there is a real mechanism. Recruiters search their applicant database using specific terms, and a resume that does not contain a term will not appear in a search for it. That is the whole thing. It is a search problem, not a trick, and the correct response is to make sure the true things about you are written in the words people search for.

What is actually being matched

Two different processes are often confused.

The first is a recruiter typing a query into their system: "prior authorisation" AND Epic, or NetSuite AND consolidation. This is an ordinary keyword search over the parsed text of your resume. If your resume says "insurance pre-approvals" and their query says "prior authorisation", you are not in the results, even though you have done the job for three years.

The second is an automated ranking or knockout question, which is less common than folklore suggests and usually restricted to hard requirements — a licence, a degree, years of experience, work authorisation. These are typically collected from the application form rather than inferred from your resume text.

Both are far more literal than people expect, and neither is doing semantic reasoning about whether you would be good at the job. That is what makes vocabulary matching worth doing, and it is also why the effort should go into wording rather than volume.

Reading a posting properly

Most postings are three documents stapled together: a legal-and-HR section, a wishlist written by a committee, and somewhere in the middle, a short description of the actual job. Only the third part is worth mining.

Start with the responsibilities, not the requirements. The requirements list is where wishful thinking accumulates — "10+ years", "PhD preferred", four cloud platforms. The responsibilities section describes what the person will do on Tuesday, and it is written by whoever needs the hire. That is where the operative vocabulary lives.

Note what repeats. If "cross-functional" appears four times across a posting, someone chose it deliberately and it is probably describing a real feature of the role, usually a difficult one. Repetition is the most reliable signal of priority available to you, and it costs nothing to count.

Separate hard terms from soft ones. Hard terms are specific and checkable: NetSuite, ACLS, ASC 606, Kubernetes, reach truck, Epic, multi-state payroll. Soft terms are qualities: collaborative, strategic, self-starter. Hard terms are worth matching exactly, because they are what gets typed into a search box. Soft terms are worth demonstrating and never worth listing.

Find the two or three terms that would be in the search. If you were the recruiter with sixty applications and thirty seconds, what would you type? Usually it is one system, one domain word, and one credential. Those three are your priority, and they should each appear at least once in a sentence about something you actually did.

Where the words go

Placement matters more than count, because a recruiter who finds you through a search then reads the page.

In your bullets, inside real sentences. A term that appears in a description of work you did carries evidence with it. "Ran prior authorisations for a four-provider practice, holding turnaround under 48 hours" is both a keyword match and a reason to call you. The same term in a comma-separated list at the bottom is a match with nothing attached.

In the skills section, for tools and systems only. This is where a hard term with no natural home belongs — the ERP, the certification, the language. Keep it to labelled groups and keep it short. A skills section of forty items dilutes the six that matter and reads as padding.

In the summary, for the one term that defines you. If the posting is for a multi-state HR generalist, "multi-state" belongs in your first three lines, not buried in your fourth bullet under your second job.

What not to do

Do not paste a keyword block. A dense paragraph of comma-separated terms at the bottom of the page is obvious to every human reader, and it signals that you expect to be filtered rather than read. Recruiters have described this as a reason for rejection often enough that it should be treated as one.

Do not use white text or margin-hidden text. Parsers extract all the text regardless of colour, which means the hidden block appears in your parsed record looking exactly like what it is. This is one of the few resume behaviours that gets people actively blacklisted rather than merely passed over.

Do not claim tools you have barely used. Every term on the page is interview material. Listing a platform you touched once trades a marginal search-result appearance for the risk of being caught out on a specific question, which is a bad trade at any level.

Do not spell things only one way. Postings are inconsistent, so write "Advanced Cardiac Life Support (ACLS)" once and both forms exist on the page. This is the single highest-return keyword habit and it takes no space.

Tailoring efficiently

Rewriting a resume per application is not sustainable, and it is not necessary. What works is a small, fixed edit:

1. Change one clause in the summary to match the posting's emphasis.
2. Reorder the skills groups so the most relevant group is first.
3. Check that the two or three hard terms from the posting appear somewhere true on the page, and reword an existing bullet if one is missing.
4. Leave everything else alone.

Two to four minutes. The gain comes almost entirely from step three, and almost none of it from adding new material.

Checking your own

The useful check is not "how many keywords do I have" but "which terms from this posting are missing from my resume, and is each one missing because it is not true of me, or because I called it something else". Those two cases need different responses: the first you leave alone, the second you fix.

You can do that comparison by hand with two windows open, or run both texts through the ATS keyword checker, which extracts the weighted terms from a posting and tells you which ones are absent from your text. Either way, the output is a short list to work through, not a block to paste.

The honest summary of this whole topic: keyword matching gets your resume seen. Nothing about it will make a weak resume succeed once it is seen, and any technique that could is a technique that gets noticed.

Related

• ATS-friendly resume format: what actually breaks the parse
• The resume summary: when it earns its space
• What belongs in the skills section