12 min read
An ATS matches skills to job requirements by scanning parsed Experience bullets and job titles first, then comparing those strings to must-have terms in the posting. A Skills sidebar without the same terms repeated in dated bullets rarely scores as a match. Put posting keywords in bullet one under the role where you used them, not only in a rail. That's why qualified files lose to boring ones. The parser read your layout before any human did.
You've listed Salesforce, SQL, and stakeholder management in a neat column. The req asks for all three. You're still getting silence because Greenhouse search on imported Experience returns blank for tools that never left the Skills box. You're not crazy. The file and the filter aren't looking at the same fields.
Before you rewrite bullet ten, check your resume for free with the job description pasted in. Empty Experience rows mean layout failed. A full Skills rail with empty bullets means matching'll fail next. Fix import first, then mirror posting language.
Job searching's already a grind. This page walks through what gets weighted, where synonyms help or hurt, and what to change in the next twenty minutes. There's no magic density score. It's just the field order recruiters actually filter on in Workday and Greenhouse.
Quick Wins
- Highlight three must-have tools from the posting before you edit wording.
- Place each tool in the first eight words of a dated Experience bullet.
- Open portal preview and confirm employers imported with bullets attached.
- Trim Skills to terms that already appear in Experience or Certifications.
How ATS matches skills to job requirements after the parser runs
Think of import as step one and matching as step two. The ATS extracts plain text from your upload, chunks it into employer, title, dates, education, and bullet bodies. Only then does it compare those chunks to the skill strings the recruiter typed into the req or pulled from a template.
Experience bullets carry the most match weight. When a posting lists HubSpot, the system looks for HubSpot beside a date range, not floating in a tag cloud. Recruiters running keyword filters on imported Experience never see sidebar-only terms. That is the gap most candidates miss.
Job titles are the second lane. A filter for Business Analyst will not surface Operations Coordinator even when bullets describe SQL and Tableau work. Titles are short, high-signal strings. Mirror the posting family once when your scope is honest: Analyst (Operations) reads better to both parser and human than a cute internal nickname.
The Skills section is third. It helps when the same term already appears in Experience. It rarely rescues a file when bullets stay generic. Parsers sometimes dump Skills into a separate field recruiters skip during quick screens. Treat Skills as a index, not the proof.
Certifications and Education lines matter for credentialed reqs. PMP, CPA, RN, or AWS Solutions Architect belong in a labeled block with the exact acronym from the posting. One repeat in a project bullet ties the credential to work history. Orphan cert lines without dates import cleanly but do not always surface in search views.
Synonym handling is inconsistent. Some employer builds map JavaScript and JS; many do not. Customer success and client relations might pair on one tenant and not another. Do not bet the apply on shorthand. Spell the full term once in a bullet, add parentheses for the acronym, move on.
Must-have versus nice-to-have weighting shows up in recruiter filters, not in a public score you can see. Postings label requirements in prose; the human sets which strings are knockout filters. You cannot read that config. You can place every honest must-have in Experience and stop guessing.
Soft skills follow the same rule when the posting names them explicitly. Leadership, cross-functional communication, and stakeholder management need a verb and an object in a bullet, not a lone word in Skills. Write "Led weekly sync with finance and product on headcount planning" instead of "leadership" floating in a rail. The parser and the recruiter both want a sentence they can tie to a date.
A composite operations analyst kept losing Lever screens on SQL reqs. Her Skills rail listed SQL, Python, and Excel. Bullets said "supported reporting requests" and "helped with data pulls." Same person, wrong field. After she rewrote bullet one as "Wrote SQL queries in Snowflake for weekly ops dashboards," the imported profile finally matched the filter a recruiter had already saved.
For how full resume text maps to posting language, read how ATS matches resumes to job descriptions . This page stays on skills placement and weight, not every section of the file.
What to do now: move skills where matching actually looks
Work in order. Do not stuff keywords into Skills on a file that still parses empty. Four moves, one sitting per application once you have a master resume.
Step 1: Pull three must-haves from the posting
Highlight one tool, one method, and one outcome phrase from the requirements block. Ignore perks until those three have a dated home. If you cannot place two of three honestly in Experience, the req is a long shot. Save your energy for a tighter fit.
Before: Yellow highlight on every noun in the ad; Skills list grows to nineteen items; no priority order.
After: Sticky note with three strings: Salesforce, pipeline forecasting, QBR decks. Every edit serves those until each appears in a bullet.
Step 2: Confirm import before you tailor language
Upload to the employer portal or a test profile. Open preview. Paste the PDF into Notepad on Windows or TextEdit on Mac. If Skills appear before your current employer, fix layout before mirroring terms. Matching cannot score text the parser dropped.
Before: Two-column template; Greenhouse preview shows name and Skills only; recruiter search for your last employer returns blank.
After: Single-column Word export at 11-point Calibri; preview lists Northline Corp | Operations Analyst | Jan 2022 to Present with bullets attached.
Step 3: Rewrite bullet one under your current role
Open with a posting keyword in the first eight words. Close with scope you can defend in a phone screen. Numbers inside bullets illustrate strong shape for your own history, not market averages.
Before: "Responsible for weekly reports and cross-functional collaboration."
After: "Built Salesforce pipeline forecasts for 14 enterprise reps, cutting surprise slip deals 12% in Q2 2025."
A composite customer support lead targeting a CS operations role reframed ticket work: "Tagged 180 Zendesk macros by root cause in March 2024 sprint, dropping repeat contacts 9% over six weeks." Same job, searchable tool, honest scope.
Step 4: Align title line and trim Skills to match
Mirror the posting title family in your profile or current role when accurate. Then cut Skills to six or eight items that already appear in bullets or certs. Delete orphan tools you cannot explain in an interview.
Copy-paste bullet skeleton:
[Tool or method from posting] + [object you touched] + [result with scope]
Example: Drafted SQL joins in Looker for supply chain KPIs, replacing three manual Excel pulls used by six planners.
Example: Ran Agile standups for payments squad of nine engineers across two release trains in Jira.
Edge case: posting asks for SAP you only used in a classroom lab. One honest Projects bullet beats pretending it was a full-time duty. Label it Academic project with month and year.
Edge case: internal title was Growth Ninja at a ten-person startup. Add a recognizable string in parentheses once: Growth Lead (Marketing). Parsers and humans both need a title they can filter on.
Repeat each must-have once in the summary or profile only if it also appears in a dated bullet the same page. Summary-only keywords look like stuffing when Experience stays vague. Two clean mentions beat six scattered ones in fields recruiters do not search.
Read resume rejected by ATS when preview keeps failing after you moved skills into bullets. Sometimes the blocker is file type or hidden tables, not keyword placement.
When skill matching still fails after you mirrored the posting
Exceptions matter because job boards repeat bad advice about keyword density. These are the patterns that still kill a match when bullets look fine on your screen.
Skills-only tailoring. You swapped six items in the rail but left Experience verbs generic. Search still misses you. Flip the order every time: bullets first, Skills second.
Hidden or tiny text. White font footers and micro-type keyword blocks sometimes import and sometimes get flagged when a recruiter opens the native PDF. Keep terms visible in normal body size under a real employer line.
Acronym without spelled-out pair. You wrote KPI everywhere; the req says key performance indicators in the requirements paragraph. One bullet with the full phrase plus KPI in parentheses covers both human and parser reads.
Tools trapped in tables or icons. Excel inside a graphic skill bar does not always extract. Spell Excel in a bullet about models you built, then list it in Skills if you still want a rail.
Conflicting titles across files. Resume says Coordinator; LinkedIn says Manager; cover letter invents Strategist. Pick one honest title string and repeat it. Mismatch pauses humans even when parsing looks fine.
Exception: some older Workday builds strip PDF hyperlinks but keep plain text. If your portfolio URL vanishes from preview, paste the URL as visible text once. Do not rely on blue underline alone.
Exception: agency portals sometimes recompress your file before it reaches the employer ATS. When preview looks wrong and your source DOCX is clean, apply again on the company careers site with the same single-column export.
This will not fix applying to roles where you lack two of three must-haves. It stops a qualified file from losing to a filter that never saw your tools because they sat in the wrong section.
When the portal asks for a letter, draft three short paragraphs in the cover letter generator . Repeat two posting keywords tied to bullets you already rewrote. Letters do not replace empty Experience rows after a bad parse.
Score skill overlap before the next upload
Run the free ATS checker with the job description pasted in. It flags whether must-have terms still sit only in Skills and whether Experience imported as separate dated lines.
Score your job match on the two reqs you are comparing this week. Low score with honest inputs means fix gaps or skip, not hope. High score with clean preview means submit once and log which three keywords you moved into bullet one.
Your next apply: match where the filter looks
How ATS matches skills to job requirements is not a mystery density game. Import reads Experience and titles first. Skills repeat what bullets already prove. Pull three must-haves, fix preview, rewrite bullet one, trim the rail, submit once.
Open the req you are closest to winning. Highlight the first tool in the requirements block. Put it in the first eight words under your current employer tonight. Preview before knockout questions. You will not land every role, but you'll stop losing readable files to sidebar-only keywords.
I've screened enough Greenhouse queues to know the next shortlist usually follows boring, specific proof in dated lines. Not a longer Skills cloud. Three posting terms in bullet one, honest titles, single column. Run the loop once per employer and move on to the next tight fit.
When you are ready to tighten file structure before the next keyword pass, read PDF vs Word resume for ATS for upload choices that keep parsed Experience intact.
Read more
Frequently asked questions
Rarely on its own. Most parsers attach higher weight to the same term inside a dated Experience bullet or a job title line. A Skills rail without that repetition often fails recruiter keyword filters even when the PDF looks keyword-rich. Repeat must-have tools in bullet one under the role where you used them.
Behavior varies by platform and employer configuration. Some imports treat common pairs as related; many do not. Safer practice: spell the full term once in a bullet and put the acronym in parentheses on first use. Do not assume the parser will bridge informal shorthand you invented in a sidebar.
Yes. Title strings are searchable fields in Workday, Greenhouse, and Lever. A posting filter for Project Manager will not catch Program Coordinator even when bullets describe the same work. Mirror the posting title once in your profile or most recent role line when honest scope allows.
Copy only terms you can defend in an interview and place in Experience. Dumping the full posting into Skills without dated proof creates a mismatch when a recruiter opens the file. Pull three must-haves first, prove each in a bullet, then trim the Skills list to what already appears in body text.
List them under a Certifications heading with the exact credential string from the posting. Repeat the acronym once in an Experience bullet if you applied it on a project. Certifications without a dated role anchor sometimes import to a separate field recruiters forget to search.