11 min read
Put must-have keywords in Experience bullet one and summary line two. That's where to put keywords so ATS understands them: terms tied to a job title, employer, and date range, not a Skills-only list at the page bottom. Parsers map keywords to context. Python in a footer doesn't tell Workday you used it at Acme Corp from 2022 to 2024. Bullet one under that employer does.
Check your resume for free with the posting pasted in after you highlight three required skills. If those terms appear only in Skills and nowhere under a dated job, you're listing words without proof. You won't fix that by adding ten more rows to the footer.
You've probably been told keywords matter. They do, but placement matters more. Job searching through ATS portals is already opaque. This page answers why context beats density, which exceptions still work, and what you'll change on your master file before tonight's apply. No keyword stuffing required.
Don't copy every verb from the posting into a cloud at the bottom. Recruiters ctrl-f inside Experience first. If your must-have tool isn't in bullet one under a real employer, the parsed view looks like you borrowed a word list. It's not convincing on either side of the screen.
Open the posting. Highlight three required skills. Find bullet one under your current job. If none of those three appear in the first eight words, you've got your answer before you upload again. Where to put keywords so ATS understands them isn't a mystery. It's bullet one and summary line two.
Quick Wins
- Highlight three must-haves from the posting before you edit anything.
- Rewrite summary line two with title plus two posting tools in one sentence.
- Put each must-have in bullet one under the employer where you used it.
- Keep Skills as scan support only; never Skills-only for required terms.
Why ATS maps keywords to job context, not footers
Applicant tracking systems ingest a text stream and attach fragments to fields: employer, title, dates, bullet body, Skills. Keywords inside a dated Experience block inherit that structure. The same word in a footer inherits nothing. Recruiters sorting by recency and hiring managers skimming bullet one see context. A Skills row sees a label.
Skills footer alone doesn't tie terms to employers. That's the failure mode most candidates miss. You listed Salesforce, SQL, and Tableau at the bottom. The posting required all three. The parser found the words. It didn't find them next to a job where you used them. Screening views that weight recent Experience higher treat footer-only terms as unproven.
Summary line one is usually your name and title line. Line two is your headline match: years of scope plus two tools from the posting in plain prose. That gives the ATS a dated-adjacent signal even before Experience. Bullet one under your current role closes the loop with an outcome number recruiters can quote.
I've screened files in Greenhouse where every posting keyword appeared in Skills and zero appeared in bullet one. Ctrl-f returned hits. The six-second skim returned nothing convincing. The candidate wasn't underqualified. The keywords weren't anchored.
Edge case: new grad with one internship. Put posting keywords in bullet one under that internship and mirror them in summary line two. Skills can repeat them for scan support. You still need one dated block even when the timeline is short.
Edge case: career change where old job titles don't match the new field. Summary line two names the target title honestly. Bullet one under a recent role describes transferable work using the posting's tool names even if the employer was a different industry. Context still beats a footer list.
Read how resume design impacts data accuracy when keywords are placed correctly but sidebar layout scrambles which employer block they attach to.
Where to put keywords so ATS understands them: placement pairs
Each pair shows the same candidate and posting. Only keyword placement changes. Open the req and highlight three must-haves before you compare.
Pair 1: Skills-only vs bullet one
Before: Posting requires HubSpot, SQL, and demand gen. All three sit in a 12-row Skills footer. Experience bullets mention campaigns without tool names.
After: Bullet one under current role: Ran HubSpot demand gen and SQL audience splits for 38K contacts; lifted MQL-to-SQL from 11% to 16%. Skills row repeats HubSpot and SQL for scan support only.
Pair 2: Summary keyword dump vs summary line two
Before: Summary reads: Agile, Scrum, Jira, Confluence, stakeholder management, roadmap, KPI, stakeholder, stakeholder.
After: Line two: Product manager with six years in B2B SaaS; shipped roadmap items in Jira for teams running Agile sprints. Two posting terms, one sentence, scope attached.
Pair 3: Footer synonym list vs exact posting spelling
Before: Posting says AWS Solutions Architect. Skills row says Amazon Web Services, cloud certs, infrastructure.
After: Education line: AWS Solutions Architect Associate, May 2024. Bullet one: Migrated three production workloads on AWS; cut monthly hosting spend 18% while holding 99.9% uptime.
Pair 4: Hidden header keywords vs body placement
Before: Required terms typed in Word header in 8pt white text because a blog said parsers read headers.
After: Terms removed from header. Bullet one and summary line two carry the same words in visible body text the Notepad paste confirms.
Pair 5: Repeated keyword stuffing vs one contextual use
Before: Python appears eleven times across Skills, summary, and five bullets with no outcomes attached.
After: Python once in bullet one: Built Python ETL jobs ingesting 2M rows nightly; cut manual reporting time from 6 hours to 20 minutes. Once in Skills for ctrl-f backup.
Copy-paste keyword placement block
Copy-paste this block and fill it before each tailored apply:
Posting must-have 1: _____________ → bullet one employer: _____________
Posting must-have 2: _____________ → bullet one employer: _____________
Posting must-have 3: _____________ → bullet one employer: _____________
Summary line two: [title] + [years scope] + [tool 1] + [tool 2] in one sentence
Skills: repeat terms only after they appear in bullet one or Education
Header/footer: leave blank; no keywords outside body text
Read why minimal resumes perform better when you've placed keywords in context and still need to trim footer noise.
Placement exceptions that still work
Certifications with exact posting acronyms on the Education line. PMP, CPA, and RN keywords belong next to completion dates, not only in Skills. Parsers map credential fields separately from bullet bodies.
Skills row after Experience for ctrl-f backup. Repeating a term you already proved in bullet one helps recruiters who search the footer first. Repeating without bullet one proof does not.
Projects section for tools you used outside paid work. Acceptable when the posting allows portfolio proof and the project has a date. Still use bullet format with scope and outcome, not a comma-separated keyword line.
Synonym plus exact match in the same bullet. Posting says JavaScript. Bullet can say JavaScript and JS once if both appear in the req. Don't add synonyms the posting didn't use.
Cover letter repetition of bullet one scope. Letters parse on some portals. One sentence mirroring bullet one keywords reinforces context. The resume still carries the proof. The letter carries the narrative.
Edge case: acronym-heavy postings in defense or healthcare. Spell out the term once in bullet one, then use the acronym in parentheses if the posting uses both forms. One line, not two footer rows.
Edge case: soft-skill keywords like stakeholder management. Put them inside a bullet that names who you worked with and what changed. Soft terms without scope read as filler in both ATS views and human skims.
What doesn't work even as an exception: keyword blocks in text boxes, white-on-white footer text, and Skills sections longer than twelve rows with no Experience anchor. Those patterns parse sometimes and convince never.
When a posting lists nice-to-have tools below required ones, put required terms in bullet one and summary line two first. Nice-to-haves can sit in bullet two or Skills if you truly used them. Don't bury must-haves below optional rows recruiters never scroll to.
Coordinators forwarding your profile often paste parsed Experience into email, not your Skills footer. Keywords in bullet one travel with the forward. Footer terms stay behind. Place for the forward, not just the ctrl-f.
Match check before you upload again
After you move keywords into bullet one, run a free ATS check with the job description pasted in. You're confirming must-haves appear inside parsed Experience, not only in a Skills block that imported cleanly while context stayed empty.
When the posting asks for a letter, generate a cover letter that mirrors bullet one scope in prose. Letter and resume should name the same tools under the same employer timeline.
Tailor bullet one before the next apply
Where to put keywords so ATS understands them is not a density game. Parsers and recruiters both read keywords inside job context first. Experience bullet one and summary line two tie terms to employers, dates, and outcomes. A Skills footer alone lists words without proof.
Open the posting tonight. Highlight three must-haves. Rewrite summary line two. Move each term into bullet one under the job where you used it. Run the copy-paste placement block before upload. This won't fix applying to roles you're not qualified for. It stops qualified files from looking like keyword lists nobody believed.
Save a master file and a tailored copy per req family. Label them so you don't upload the generic Skills-heavy version at midnight. Boring filename Targeted_Product_Manager.docx next to Master_Resume.docx saves you from repeating footer-only placement on every apply.
Read more
Frequently asked questions
No by itself. A Skills footer lists terms without dates or employer context. Parsers and recruiters both weight keywords inside Experience blocks higher because the tool name sits next to a job title and date range. Keep Skills for scan support, but every must-have from the posting needs a home in bullet one or summary line two under a real role. Skills alone tells the ATS you know a word, not that you used it on the job.
Both, but with different jobs. Summary line two carries your headline match: title plus two tools from the posting in one sentence tied to years of scope. Experience bullet one under your current or most relevant job proves you used those tools with an outcome. Repeating the same term in Skills without either placement is the pattern that fails. Summary frames fit. Experience proves it.
Once in context beats three times in a list. Pick three to five must-haves from the posting. Place each once in bullet one under the employer where you actually used it. Mirror the posting's exact spelling for tools and certifications. A second mention in Skills is fine for scan support. A third repetition in a hidden footer or white text hurts readability and can flag integrity screens. Context over density.
Often no. Many parsers skip Word header and footer zones, so keywords typed there never enter the text stream recruiters search. Put contact and headline terms in the body on line one and two. Same rule for text boxes and sidebar columns: if Notepad paste doesn't show the term, the ATS probably didn't read it either. Body placement only.
Certifications belong on the Education or Certifications line with the exact acronym the posting uses: PMP, CPA, AWS Solutions Architect. Degree keywords stay on the Education line with the full degree name. Do not park cert acronyms only in Skills when the posting lists them as required. One line under Education with Month Year completion date ties the keyword to a credential field parsers recognize.