By Peter Miller · Published August 10, 2026 · Last updated: September 17, 2026
12 min read
You already matched the posting once. You pasted every skill from the req into a list, hit submit, and still heard nothing. That's common, and it usually means the parser saw your keywords in the wrong neighborhood of the file.
US hiring stacks don't reward a word count. They reward terms tied to dated job blocks humans can scan in ten seconds. When the same phrase sits only in Skills, it reads like a wish list, not proof you ran the queue.
If you've been told to add more keywords, ask where the last one landed. Most advice skips placement entirely. That's the gap this page closes with steps you can run on the next req in fifteen minutes.
Before you rewrite, check your resume for free on the export you plan to upload. You'll see whether Experience imported before Skills, which is the order most recruiters trust.
Below you'll get five ordered steps, two edge cases for career changers and contractors, mistakes that look like optimization, copy-paste bullet shells, and FAQ rules so you stop guessing where a term should live.
Job searching is hard enough without fighting your own layout. This won't turn a weak fit into an offer. It stops a qualified file from hiding the words the req already asked for.
Quick Wins
- Highlight three must-have terms in the posting before you open Word.
- Move one term from Skills into bullet one today.
- Export PDF and confirm Work Experience is not empty in the checker.
Why placement beats keyword volume on US parsers
Most resumes never reach a human until the file parses. When Experience blocks import empty or out of order, keyword lists at the bottom do not rescue the record. Recruiters see a skeleton, not your proof.
The parser reads top to bottom inside each job block. Line one carries the method, tool, or scope the req repeats. Line four with the same word is backup, not anchor.
Skills sections help humans skim fast. They rarely replace missing proof in Experience for must-have tools. If SQL only appears in Skills, assume a sourcer will ask when you last wrote a query.
Postings mix exact vendor strings with plain duties. Your job is to mirror exact strings once where honest, then describe outcomes in normal language everywhere else.
Two-column Canva layouts often push Skills left and Experience right. Some parsers read columns out of order. Single-column DOCX or text-based PDF keeps title, dates, and bullets in one stream Workday expects.
For how section order affects ranking after import, see how resume positioning impacts ranking . For salary fields that sit beside your resume in the same portal, read how to answer desired salary on US applications .
Acronym soup hurts placement when spelled five ways. Pick the posting version for SOC 2, HIPAA, or PCI once, then stay consistent in that req's file.
Header lines matter for contact parsing, not keyword rank. Keep email and phone in plain text so recruiters can click after keywords work.
Part-time roles still deserve Month Year ranges. Undated keyword blocks look like side projects even when you worked twenty hours a week for two years.
Internal promotions should show title change on the same employer line when possible. Two employer headers for one company confuse parsers and humans.
Five steps to place keywords where US ATS reads first
Work the posting left to right once. Do not rewrite the whole resume until each step below is checked off for that req.
Step 1: Build a three-column term list
Column one is title strings the employer used. Column two is tools and certifications repeated twice or more. Column three is nice-to-have verbs you will only add if true.
Ignore buzzwords that appear once in a culture paragraph. If DevOps appears only in a team value statement, it is not your anchor term.
Step 2: Assign each must-have term to one role
Pick the job where you used the tool last. Contractors with six clients should not paste the same keyword under all six blocks. One primary home, one supporting bullet elsewhere at most.
Career changers: assign posting language to project or volunteer blocks when employment title differs. Dates still matter. Undated keyword blocks look like padding.
Step 3: Rewrite bullet one under current or target role
Put method or tool in the first eight words. Follow with outcome and scope. Numbers inside the bullet are illustrations of format, not claims about the market.
Before: Responsible for reporting and cross-team updates.
After: Built weekly churn dashboards in Looker, cutting reactive tickets 11% in Q3 for a 12-person CS pod.
Step 4: Align the job title line without lying
When your internal title was generic but scope matched the posting, use an ATS-safe line like Analyst (Financial Planning) or Customer Support Specialist | SaaS. Do not claim Manager if you mentored one intern.
Match posting seniority language when your years fit. A Senior tag on a two-year profile triggers human skepticism even if the parser smiles.
Step 5: Mirror one exact phrase from the req
Choose the single non-negotiable string. Paste it once in bullet one or title. Paraphrase the rest so you do not sound like you copied the posting into every line.
I've screened stacks where the Skills column was perfect and bullet one still said helped with projects. That file lost to a boring bullet with the vendor name in word three.
Copy-paste block: bullet one shells
Copy-paste shells (swap brackets)
[Tool] + outcome: Resolved 40+ daily [tool] tickets, avg handle time under 6 minutes, CSAT 96%.
Method + scale: Automated [process] in [platform], saving 8 hours/week for a 5-person team.
Compliance + scope: Owned SOX controls for [system], zero findings across two audit cycles.
Edge case: career changers with unrelated titles
Add a Selected Projects block directly under summary with Month Year dates. Place posting keywords in bullet one of the project, not only in a paragraph about passion.
Keep employment history honest. Projects supplement, they do not erase gaps you should explain in a cover letter.
Edge case: contractors with short engagements
Group related clients under one consulting header when contracts were under six months each. One bullet per client max. Put the shared tool in the group bullet one instead of repeating it six times.
Before: Six one-line gigs with tools only in Skills.
After: Consulting block with Zendesk in bullet one and client names in sub-bullets.
Run the same export through a parse check after grouping. Some systems merge dates oddly when headers multiply.
Parents returning from gaps: one volunteer block with ticket or CRM proof beats a Skills list that says organized and detail-oriented.
Students: capstone projects count when dated and scoped. Put the posting tool in capstone bullet one, not in a coursework paragraph at the bottom.
Remote applicants: time zone and async tools belong in bullet two, not in place of the must-have term on line one.
Federal or clearance reqs: put clearance level in header plain text, not inside a footer icon recruiters cannot select.
After each step, read bullet one out loud. If it sounds like a job description pasted from the posting, rewrite with your own metric scope inside the bullet.
Save the term list in the same doc as the req link. Future you will forget which three words mattered when the req reposts with a new ID.
When a posting lists nice-to-have tools you lack, skip them. One honest gap beats five fake icons that fail the phone screen.
Multilingual reqs: place language in bullet one only when you handled tickets in that language, not when you studied it in school unless the posting accepts that.
If you use a headline under your name, keep it one line and tie it to bullet one proof. Headlines without Experience anchors look like marketing slogans in Workday.
Where keyword lists fool you
Stuffing the Skills cloud. Fifteen tools in one row signals copy paste from the posting, not daily use.
White text tricks. Hidden fonts break trust with humans and may fail compliance checks. Do not do it.
Keyword only in the summary box. Fancy templates park summaries in text boxes parsers skip. Move proof to Experience.
Before: Every bullet starts with Responsible for.
After: Each bullet opens with method, tool, or metric scope tied to the req.
Chasing every synonym. Pick exact vendor language once, then write like a human for the rest.
Ignoring file type. A pretty PDF that imports blank Experience wastes a night of keyword work. Test DOCX when the portal allows it.
Night applicants: do not paste the whole posting into Skills at 1 a.m. Mark three terms, sleep, then place them in bullet one with fresh eyes.
Batch applying with one master Skills list and zero bullet edits is how qualified people stay invisible. Change bullet one per req when the must-have tool shifts.
Footer quotes and mission statements steal space from Experience on page one. Move them out or drop them during an active search.
When a req asks for industry experience, place industry name in bullet two with scope, not only in a summary adjective like healthcare background.
If you maintain two resume versions, label them in filenames by target lane. Uploading the data science version to a support req is a placement disaster even when both lists look polished.
Parse the file before keywords matter
Paste the posting into score your job match and note which must-have terms are missing from Experience, not from Skills. Fix gaps in bullet one before you tweak lists.
Run the ATS checker on the PDF or DOCX you'll upload. Empty Experience blocks make keyword placement irrelevant.
When match score and parse check disagree, trust the parse check. A missing job block is structural failure, not a synonym problem.
Save a plain-text export after each rewrite so you can compare imports across three reqs without reopening Word at midnight.
Use the cover letter generator only after bullet one matches the posting. Letters repeat one proof line, they do not replace Experience keywords.
Ship bullet one before you add another Skills row
Open the posting, pick three must-have terms, and rewrite one bullet under your current role. Export, parse check, then submit. That sequence beats another hour sorting alphabetized tools.
Run a free ATS check on the file you will upload tonight. If Experience imports clean and bullet one names the req tool, you are farther ahead than most stacks I see.
Keep a one-line brag doc each week. Paste fresh proof into bullet one before you batch apply on Sunday, not after the fifth rejection email.
When a req closes, archive your term map with the bullets you used. Reuse the structure on the next posting with the same stack, not the same words on a different tool chain.
And if someone tells you density beats placement, ask them to point at bullet one on your file. That's the only argument that matters in a US screen.
Read more
Frequently asked questions
No. Most US parsers read Work Experience before they treat Skills as context. A term that only appears in a badge list often fails to tie to a job block. Put must-have tools and methods in bullet one under the role where you used them, then repeat once in Skills if the posting asks for a list.
Usually once in a title or headline, once in bullet one for the relevant job, and optionally once in Skills when the posting lists it as required. Repeating the same phrase in every bullet reads like stuffing and does not help humans. Match phrasing from the posting for one critical term, not the whole paragraph.
Only if the summary is plain text the parser can read. Fancy summary boxes in two-column templates often import last or not at all. When you use a summary, keep it three lines max and repeat one posting title the employer actually used, not a invented headline.
Sometimes, but you should not gamble on them for must-have terms. If the posting says Salesforce Service Cloud, write that once exactly. You can add a second bullet with plain language about case management, but do not swap the vendor name for a generic phrase on line one.