12 min read
Put keywords in experience bullets, not in a Skills dump. Open bullet one with a required tool from the posting in the first eight words. Skip the summary for keyword strategy. That's where to place keywords so ATS understands them, and it's the opposite of what most templates tell you to do.
You've probably been told to "optimize your Skills section." You're not wrong to list tools. The parser already extracted those lines. What it often can't map is which job you used the tool in. Recruiters filter on current role tokens. A keyword floating in a sidebar without dates doesn't answer "have they done this recently?"
Check your resume for free with the job description pasted in. You're confirming bullet one carries a required skill in the right section, not chasing a perfect keyword count. This page shows placement by section, the exceptions, and what to change in the next ten minutes.
Job searching is slow enough without rewriting the wrong block. This won't get you past a hard degree requirement or years-of-experience gap. It stops a qualified file from looking empty in a Greenhouse filter because every keyword lived in a list nobody weighted.
If you're switching stacks, don't panic and dump every new tool into Skills. Put the posting's must-have in a project or internship bullet with dates. You'll still need honest scope, but the parser can't credit a keyword that never touched an Experience header. That's the gap most "optimized" files still have.
Quick Wins
- Rewrite bullet one so a required tool from the posting appears in the first eight words.
- Move keyword proof from Skills into the job block where you used the tool.
- Trim summary keyword stuffing; keep summary to two lines max for humans.
Why keyword placement beats keyword density
Applicant tracking systems extract plain text, chunk it by section headers, and attach tokens to employer rows when the layout allows. Experience blocks carry dates. Skills blocks often do not. When a recruiter runs a filter for "Salesforce AND current employer," the match lives in a bullet under your latest job, not in a comma list on line forty.
The rule recruiters act on: prove the skill inside a dated role. Lists are skimmed. Bullets are searched.
The first eight words of bullet one get read twice: once by the parser as a headline token, once by a human in the six-second skim. If you open with "Responsible for various tasks," you burned the slot. If you open with "Built Terraform modules for EKS," you named the stack before the recruiter scrolls.
Summary sections sit above Experience on the page but below it in many scoring workflows. Parsers that treat Summary as marketing copy deprioritize it. Humans like a tight summary. ATS keyword strategy should not depend on it.
Read why skill overload hurts ATS scores for what happens when the Skills section grows faster than your bullets. This page is the placement fix: same keywords, different real estate.
Edge case: career changers with thin direct experience. Put the posting keyword in a project bullet under a clearly labeled Projects section with Month Year dates, not only in Skills. Edge case two: acronyms the posting spells out. Use the form from the job description in bullet one; you can add the other form once in Skills if space allows.
Education keywords matter for credentialed roles, but they sit below Experience in most filters. CPA, RN, or PE belongs in Education with the license month and year. The daily tools still need bullets. A CPA line does not replace "built quarterly close models in NetSuite" under your last employer.
Volunteer work can carry keywords when it is recent and relevant. Treat it like a job block: organization, role, Month Year, bullets with tools. Do not hide volunteer AWS work only in Skills while paid experience shows unrelated verbs.
Where to place keywords on your resume by section
Work top to bottom inside Experience first. Touch Skills last. Ignore keyword density calculators. You're building a map a parser can tie to employment dates.
Experience bullet one under current role
Open the posting. Highlight the top three required tools or channels. Pick the one you truly used in the last twelve months. Rewrite bullet one so that word appears before word eight. Follow with scope, stakeholder, and one metric from the role.
Before: Software Engineer bullet: Worked on backend services and improved performance.
After: Software Engineer, Northwind Labs, Mar 2023 to Present · Built Go microservices on Kubernetes handling 12k RPS; cut p95 latency 22% after query index pass.
Before: Marketing Coordinator: Assisted with email campaigns and reporting.
After: Marketing Coordinator, Bright Path, Jun 2022 to Present · Ran HubSpot nurture flows to 48k contacts; lifted SQL 14% in Q1 without raising spend.
Bullet one is not the only bullet that matters. It is the one every filter and every human reads first. Get it right before you tune bullet four.
Second and third bullets under the same role
Spread secondary keywords across bullets two and three. Each bullet should name a different verb and a different tool. Repeating "Python" three times in one job block adds noise without new proof.
Pair a keyword with an outcome recruiters can repeat in a screen. "Used Jira" is weak. "Cut sprint spillover 30% after Jira workflow redesign with eng leads" ties the tool to a result.
Skills section as backup, not primary
Keep Skills to one or two lines of comma-separated tools you already proved above. Order tools the posting repeats. Do not add tools you cannot defend in a phone screen. The Skills line is for human skim when they're on page two, not a substitute for Experience.
If a posting lists "Tableau" as required and you only mention it in Skills, you are betting the filter ignores section weight. Move Tableau into a bullet with a deliverable before you apply.
Summary: human hook only
Two lines max. State level, domain, and one outcome. Do not mirror the entire posting. If you mention a keyword here, it should already appear in bullet one.
Before: Summary paragraph listing twelve tools copied from the job ad.
After: Backend engineer with payments and PCI scope. Bullet one below shows Kubernetes and Go in production.
Copy-paste keyword placement checklist
Run beside the open posting before you export PDF:
[ ] Top required tool appears in first eight words of bullet one
[ ] Same tool appears in a dated Experience block, not only Skills
[ ] Secondary keywords spread across bullets two and three
[ ] Skills line matches tools already proven in bullets
[ ] Summary ≤2 lines; no pasted job description
[ ] Acronym matches posting spelling in bullet one
[ ] PDF paste into Notepad keeps section order intact
Edge case: contract roles stacked in one year. Label each client with dates so keywords map to the right stint. Edge case two: internal jargon the posting does not use. Translate to the posting term in bullet one; keep internal name in parentheses once if needed for your manager reference check.
Job title lines carry keywords too. If the posting title is "Product Marketing Manager" and your internal title was "Growth Lead," consider a truthful subtitle: Growth Lead (Product Marketing). Do not invent a title you cannot verify on a background check. A honest subtitle beats a keyword-free title line.
Location and remote keywords belong in the header for humans, not as a substitute for stack proof. "Open to remote" does not replace "Terraform" in bullet one for an infrastructure req.
When keyword dumps and summary stuffing fail
The pattern: high keyword count in a checker, empty recruiter inbox. The file repeated words without tying them to work history.
Pasting the job description into Summary creates a block quote recruiters recognize instantly. Parsers still extract it. Humans downgrade trust. You have not proved experience; you have proved copy paste.
Skills sections with thirty tools and three thin bullets signal keyword stuffing even when the layout parses cleanly. I've seen profiles where every trending tool appeared in Skills and none appeared under the current employer. The filter says no match on recency.
White text or hidden columns are an old trick and a fast rejection when someone opens the Word source. Do not do it. Plain single-column text wins.
Burying the keyword at the end of a twelve-word bullet wastes the headline slot. Move the tool forward. Cut filler adjectives instead.
Using keywords only in a cover letter while the resume stays generic fails when recruiters filter on the resume file first. If the portal allows a letter, generate a cover letter that repeats bullet one's nouns, not a new keyword list the resume does not support.
Certifications without production bullets work for entry gates, not for "five years of X" lines. Match the req type. If they want years in role, the keyword must sit in Experience with covering dates.
Synonym sprawl hurts search. If the posting says "customer success," do not scatter CSM, client success, and account success in five places. Pick the posting phrase in bullet one. One alternate in Skills is enough.
Read what recruiters look at first on a resume to align keyword placement with the six-second human skim. Parser placement and human placement overlap on bullet one more than anywhere else.
Graphic skill bars and star ratings replace searchable text. Swap them for words. A five-star icon row for Excel does not give the parser the token Excel the way a bullet about pivot tables does.
Keyword placement in a two-column template often parks Skills in a left rail the parser reads before Experience. Your employer names end up below thirty tools. Flatten to one column before you tune keywords.
Test keyword placement before you submit
Paste the posting and your export into a checker. You're looking for missing section headers and warnings about tables, not a green score for keyword volume.
Run a free ATS check on the file you'll upload. Fix employer order and bullet one before you chase secondary keywords. Then score your job match to confirm the top required skill appears in Experience, not only in Skills.
Edge case: applying to five similar roles in one night. Swap bullet one per posting. Keep the same file name pattern so you do not upload the wrong company's version.
Fix bullet one before you add another keyword
Open the posting you're targeting tonight. Highlight one required tool. Rewrite bullet one under your current role so that tool lands in the first eight words. Move any orphan keywords from Skills into the job block where you used them.
Export single-column PDF. Paste into Notepad to confirm order. Apply once per role with that tailored bullet. Where to place keywords so ATS understands them is really where to prove you used them recently, in a dated line, at the top of the file.
You do not need a longer Skills dump. You need one boring, specific bullet recruiters can filter on and ask you about on a call. That is the whole placement game.
When a friend asks whether more keywords help, tell them placement first. A third use of "Agile" in a sidebar does not beat "Shipped React features in two-week sprints" in bullet one. Same word count, different signal.
Batch similar postings if you want momentum. Change bullet one and the Skills order per req. Keep layout flat. Do not rebuild the template every time. Ten tailored bullet ones beat one generic file with forty Skills lines.
Save a master resume with every bullet you've ever used. Fork a tailored copy per application. Edit Experience first, Skills second, Summary last. That order keeps you from decorating a summary while bullet one still says "assisted with projects."
When you get a recruiter reply, note which keyword they asked about first. That's your next bullet one for similar roles. The placement lesson compounds once you see what people actually query on a screen share.
Read more
Frequently asked questions
Put the posting's must-have tools in experience bullets first. The Skills section is a backup list for human skim, not the main parse signal. A bullet that opens with Python and AWS ties the keyword to a role and date. A Skills line that says Python without context extracts as a loose token recruiters cannot filter on reliably.
Parsers and humans both read top to bottom inside each job block. The opening phrase becomes the headline for that bullet in many ATS profile views. If your strongest keyword sits at word twelve, some systems never weight it as highly as the verb at the start. Front-load the tool or channel from the posting, then add scope and metric after.
A short summary is fine for humans. It is a weak place for ATS keyword strategy because many parsers skip or de-prioritize summary blocks compared with Experience. If you use a summary, keep it to two lines and mirror one keyword you already proved in bullet one. Do not paste the job description into the summary to chase match scores.
Three to four natural uses across the file is enough when placement is right. Once in bullet one under your current role, once in a second bullet with a different context, and optionally once in Skills if the tool is truly core. Repeating the same word fifteen times in a sidebar looks like stuffing to recruiters even when the parser still reads it.
Put AWS Certified or PMP in Education or Certifications with the month and year. Do not rely on that line alone for a hard skill the posting lists under required experience. If the req says three years of Kubernetes in production, the word must appear in a job bullet with dates that cover those years.