12 min read
Don't build one keyword cloud from the whole posting. That's the advanced keyword research move most people skip. An ATS checker scores your file against the job description, but you still have to decide which lines are must-haves and which are nice-to-haves. Required skills, responsibilities, preferred qualifications, and legal boilerplate carry different weight. When you dump everything into a single list, you treat a podcast mention like a HIPAA requirement.
You're not gaming a hidden algorithm. You're matching language recruiters ctrl-f before they'll read bullet two. Workday and Greenhouse don't publish ranking rules. You can observe what hiring managers highlight in the req and what disappears when you paste the posting into plain text.
Below you'll get a five-step section split, before/after bullet fixes, a copy-paste worksheet, edge cases for career changers, and where an ATS checker fits after you've tagged terms by section. Job searching is tedious. This page is about reading the posting the way a recruiter skims it, not generating a word salad.
Start with the role on your list that has a clean required block. If you've been stuffing Skills while bullet one stays generic, flip the order. Keywords in a cloud don't attach to an employer. Bullets do.
Quick Wins
- Label four posting sections before you highlight a single term.
- Mirror three must-haves in Experience bullet one with Month Year dates.
- Keep Preferred skills in a separate column you may skip.
- Run the ATS checker after bullets change, not before.
What advanced keyword research means for an ATS checker
Basic keyword research copies nouns from the job description into a Skills list. Advanced keyword research tags where each term lived in the posting and whether you can prove it under a dated employer line. The ATS checker then tells you which must-haves still don't appear in parse order on your file.
The bar your file must clear: three to five must-have phrases from the Required block appear in Experience bullet one under the job where you used them. Nice-to-have lines from Preferred stay optional unless you have proof. Legal and compliance lines get one mention if you hold the license or certification.
A composite data analyst whose Skills list says Python, SQL, and Tableau but whose bullet one still reads "Responsible for weekly reports" will score keywords in a checker and lose the human screen. Same tools, no employer attachment. Recruiters search inside Experience before they read a skill cloud.
I've screened stacks of these in Workday and Greenhouse. The file that wins lists three must-haves in bullet one with dates attached. The file that loses hides the same terms in a Skills rail that parses before the current employer line.
Read resume rejected by ATS for the wider filter story. This page is the section-by-section research step that happens before you run a match scan.
Posting structure varies by company. Some Greenhouse reqs bury must-haves inside a long Responsibilities paragraph. Some Workday postings use a clean Required Skills bullet list. Your worksheet still uses four buckets so you don't miss a line because the template looked different.
Edge case: no Required section label
When the posting is one wall of text, split it manually. First paragraph through first verb list becomes Responsibilities. Lines with "required," "must," or "minimum" become must-haves. Lines with "preferred," "nice," or "plus" land in nice-to-have. Anything mentioning license, clearance, or work authorization goes in Legal.
Edge case: career change without the title
You won't have the exact title. Map must-have tools to the closest employer block and name the transfer in bullet one: "Client reporting using Excel and SQL models" under a customer success role when the posting asks for a business analyst. Don't invent a fake job title. Attach tools to real dates.
Five ATS checker keyword research steps
Work one posting top to bottom. Don't batch five reqs into one master cloud. Section tags drift when you merge unlike roles.
Step 1: Split the posting into four buckets
Open the job description in a doc. Highlight the Required or Minimum qualifications block. Copy Responsibilities next. Park Preferred or Nice-to-have in column three. Legal, clearance, and work authorization lines get column four. If the portal only shows a short summary, open the full req on the careers site before you tag.
Before: One highlight pass across the entire posting with 40 yellow terms.
After: Four labeled lists with 6 must-haves, 12 responsibility verbs, 5 nice-to-haves, and 2 legal lines you can prove or skip.
Step 2: Promote only Required and Responsibilities to must-have
Must-have means you'd decline the interview if you couldn't speak to it for five minutes. Responsibility verbs become must-haves when the posting repeats them twice or pairs them with a tool name. "Build dashboards in Looker" is a must-have. "Podcast guest experience a plus" is not unless you have episodes to cite.
Before: Nice-to-have table stakes mixed into Skills: podcasting, Spanish, volunteer mentoring.
After: Must-have column lists Looker, SQL, stakeholder reporting, and HIPAA awareness because each appeared under Required or repeated in Responsibilities.
Step 3: Rewrite Experience bullet one per must-have cluster
Group related must-haves into one bullet when they share an employer. Bullet one under your current role should open with a verb, name the tool or scope from the posting, and carry one illustrative outcome number inside the bullet, not as a claim about the world.
Before: Responsible for analytics and reporting for leadership team.
After: Jan 2024 to Present · Analytics Lead · RetailCo · Built Looker dashboards and SQL models for weekly stakeholder reporting; cut ad-hoc data requests 11% in Q3.
Before: Skills box lists Python, Airflow, and dbt with no dates.
After: Same employer block, bullet two names Airflow and dbt on a pipeline you ran with Month Year dates in the employer line above.
Step 4: Paste the posting into the ATS checker
Upload the tailored single-column file. Paste the full job description, not just your must-have column. The checker shows which tagged terms still don't appear in parse order. Cross-check each miss against your worksheet. If it's a nice-to-have, ignore it. If it's a must-have you truly lack, decide whether to apply or add an honest adjacent bullet.
Before: Chasing a 100% match by repeating the same keyword in Skills six times.
After: Three missing must-haves fixed with one bullet rewrite each; two nice-to-haves deliberately skipped.
Step 5: Plain-text paste test before submit
Export PDF or DOCX from Word. Paste into Notepad. Read top to bottom. Must-have terms should appear inside employer blocks, not only in a trailing Skills paragraph. If Looker shows up before your name because of a sidebar, flatten layout before you rerun the checker.
Save a screenshot of your section worksheet beside the checker results for that req. When you apply to a similar title next week, you'll see which must-haves repeat across companies and which were one-off nice-to-haves. That repeat list becomes your master bullet-one bank for the cluster.
Edge case: internal referrals. When a employee forwarded your resume, the hiring manager may still run the standard req text through the same filter. Tag sections on the official posting, not the forwarded email summary. The careers site version is what the checker should see.
See US resume skills section format that ATS understands when Skills still parses as a floating block. Keywords without employer attachment fool a list view and fail a human skim.
Copy-paste section tagging worksheet
Paste this into a blank doc beside the posting:
Role: [Job Title] · Company: [Name] · Req ID: [if shown]
MUST-HAVE (Required + repeated Responsibilities)
1. [exact phrase from posting] → bullet under [Employer]
2. [exact phrase] → bullet under [Employer]
3. [exact phrase] → bullet under [Employer]
NICE-TO-HAVE (Preferred only)
· [term] (skip unless true)
LEGAL / COMPLIANCE
· [license or clearance] (Y/N on file)
CHECKER RUN: [date] · Missing must-haves after rewrite: [list]
Where advanced keyword research still breaks
One keyword cloud for five different postings. Must-haves diverge by company. A merged list stuffs your Skills with terms no single req asked for.
Treating Preferred lines as Required. You'll rewrite honest bullets to chase a plus line you can't defend in a screen.
Running the checker before you change bullets. The score tells you what's missing after research, not instead of it. Tag sections first.
Repeating the same keyword six times without outcomes. Parsers and recruiters both notice duplication without scope. One strong bullet beats six Skills rows.
Ignoring layout while chasing terms. A sidebar Skills rail that parses first makes your current employer drop below tools. Flatten columns, then rerun the scan.
Adding must-haves you can't speak to for five minutes. The checker can't save you in a hiring manager interview when bullet one was fiction.
Skipping synonyms only when the posting uses them twice. If the req alternates "stakeholder management" and "executive communication," mirror the exact phrase once and use the variant once in the same employer block.
Run the ATS checker after your section pass
Check your resume for free with the full posting pasted in. You're confirming must-haves landed in Experience, not chasing a perfect score on nice-to-haves you skipped on purpose.
When the req asks for a short cover letter, generate a cover letter from the same bullet-one terms you tagged. One paragraph should name two must-haves with the same wording as your resume. Don't introduce new keywords the file can't support.
Tailor one req with section tags tonight
ATS checker advanced keyword research techniques start with four posting buckets, not one cloud. Tag must-haves, rewrite bullet one, run the checker, and skip nice-to-haves you can't prove. That's the loop recruiters recognize when they open your Workday profile.
Pick the next posting on your list. Paste the worksheet. Highlight the Required block only. Change one Experience bullet before you upload anything. Rerun the scan when the plain-text paste shows employer lines in the right order.
This won't turn a missing clearance into a hire. It does stop qualified files from losing screens because podcast keywords crowded out the HIPAA line buried in Responsibilities.
Read more
Frequently asked questions
Keyword clouds weight every line equally. A nice-to-have line about podcast experience counts the same as a required line about HIPAA compliance. Section-aware research tags each term with where it appeared: Required, Responsibilities, Preferred, or Legal. You mirror must-haves in bullet one. You skip nice-to-haves you cannot prove.
Aim for three to five must-haves from the posting's required block inside Experience bullet one under your current or most relevant role. Add two more in a short Skills line if the portal has a separate field. More than eight repeated terms without proof bullets reads like stuffing when a recruiter opens the attachment.
No. The checker shows gaps after you've built a section-tagged list. Run it with the full posting pasted in, then confirm each missing must-have either belongs in a bullet you can defend or is a nice-to-have you deliberately skipped. The tool catches omissions. You still choose what is true.
Put the posting's exact phrase in bullet one when you have the work to back it. Use one plain-language synonym later in the same employer block if the posting repeats a concept with different words. Do not scatter five variants of the same skill across Skills without a dated bullet underneath.
Tailor must-haves for each posting when the required block changes. Keep a master resume with truthful bullets and swap bullet-one openers to mirror three terms from that req. Full rewrites for every apply burn time. Section tagging tells you which three lines actually moved.