By Peter Miller · Published March 24, 2026 · Last updated: October 4, 2026
10 min read
You can keyword-match a posting and still lose because the ATS filed your best bullets under Education. That's not bad luck. It's section recognition failing while the PDF still looks fine to you.
Parsers aren't reading for story. They're splitting text into buckets recruiters search later. If you're not sure what bucket your file landed in, check your resume for free on the export you plan to upload before you tailor another version.
Below is how heading labels, date patterns, and column order drive those buckets, then a six-step audit you can run tonight without buying a new template. You won't need new design software, just Notepad and fifteen quiet minutes.
Quick Wins
- Rename creative headers to Experience, Education, and Skills in plain text.
- Put each job title on the line above Month Year dates, not inside a table cell alone.
- Paste the PDF into Notepad and confirm headers appear on their own lines before bullets.
How ATS recognizes resume sections in practice
Think buckets, not design. When Greenhouse or iCIMS ingests your file, it looks for tokens that match a small dictionary: Experience, Work History, Education, Skills, Summary, Certifications. Text between two recognized headers usually inherits the upper label until a date range signals a new job block.
Date lines do heavy lifting. A line with Jan 2022 to Present or 03/2020 to 06/2023 often tells the parser to open an employment record. If your dates sit in a right column while titles sit left, some systems merge two roles or drop tenure math entirely.
Contact is its own micro-section at the top. Name, phone, and email should appear before the first major header. When contact lives in a sidebar, parsers may still read it, but often after experience, which breaks recruiter mail-merge and phone search.
Skills lists behave differently by platform. Comma lines under a Skills header usually stay intact. Skill tags inside paragraph prose get split on punctuation, so Python, SQL may become two tokens while Python and SQL in one sentence might not register as a list at all.
Volunteer work, publications, and languages each deserve a typed header when they matter for the role. When they sit under unrelated labels, keyword search still works sometimes, but recruiter filters on employer and title will miss them.
Multi-page files do not automatically create new sections. Page breaks without headers can make parsers think everything after page one is still part of Experience, which is why long CV-style uploads struggle on US corporate portals even when the content is strong.
Summary and objective blocks are read lightly for keywords but rarely drive ranking alone. They still need a clear header so bullets below are not swallowed into a free-text blob recruiters cannot filter.
If you want the parser-level view of what happens after upload, read what recruiters actually see after ATS screening next. Section labels are the bridge between your PDF and that recruiter view.
Six-step section audit before upload
Step 1: Flatten to one column
Before: Skills and contact sit in a colored left rail while experience fills the right column.
After: Contact, summary, experience, education, and skills stack top to bottom in the body. Rails become plain paragraphs above the first job.
Step 2: Standardize header words
Before: Where I Have Worked and What I Bring headers.
After: Professional Experience and Skills as plain lines with Title Case or ALL CAPS, but no icons or emoji prefixes.
Step 3: Anchor each role with dates
Put company on one line, title on the next, dates on the third, then bullets. Repeat the pattern for every role so parsers do not merge adjacent employers.
Step 4: Run the Notepad paste test
Copy text from your PDF into Notepad. Headers should appear alone on a line. If experience bullets sit under Education in plain text, fix headers before keywords.
Step 5: Split mixed sections
Move volunteer roles under a Volunteer header instead of hiding them inside Experience without dates. Move licenses to Certifications with issuer and year.
Step 6: Match file type to the portal
Upload the same cleaned DOCX or PDF the posting accepts. Re-run the paste test after export because PDF printers sometimes flatten tables in odd ways.
Workday-heavy employers often behave better with DOCX when the posting allows it. Greenhouse uploads frequently accept PDF if the source Word file was single column. When in doubt, submit the format the application screen labels as preferred and keep a second copy in the other format for quick swaps.
After each employer block, leave one blank line before the next company name. Dense stacks without spacing can cause parsers to treat two jobs as one long paragraph, which breaks tenure filters on later screens.
Copy-paste block: ATS section skeleton
PROFESSIONAL SUMMARY
Two lines of role scope and tools tied to the posting.
PROFESSIONAL EXPERIENCE
Northwind Health
Operations Analyst
Jan 2021 – Present
• Bullet with metric and tool name from the job description.
EDUCATION
B.S. Economics, State University, May 2019
SKILLS
SQL, Excel, customer onboarding, stakeholder updates
Pair this skeleton with resume skills section: what ATS actually reads if skills still vanish after headers look correct. The issue may be list format, not the label.
Layout tricks that scramble section labels
I've watched strong analysts get filtered in Lever because a text box around Summary prevented Experience from getting a header match, which is why I start every audit with Notepad instead of the template preview.
Tables for the whole page. Designers love invisible grids. Parsers read row by row, so a table can interleave employer names with bullet fragments from another role.
Repeated mini-headers inside Skills. Technical Skills and Leadership Skills under one Skills banner can create nested labels some systems ignore. Use one Skills header and comma groups if you must categorize.
Graphics as section dividers. Horizontal bars and icons do not create boundaries. Only text headers do. Replace bars with a blank line and a typed header.
Combining Education and Coursework without dates. Long course lists without graduation year look like skills soup. Keep degree lines tight and push electives to a single line or drop them for US corporate screens.
Projects floating without a header. Side projects need a Projects header with dates or they attach to the nearest job and confuse title filters.
All-caps body text. Headers in caps are fine. Entire experience sections in caps sometimes lose casing cues parsers use to separate titles from company names.
Footnotes for contact email. A star next to the name with email in a footer often imports blank. Keep email on line two under the name in the body.
Confirm section fields before you apply
After you rename headers, run the export through the free ATS resume checker and read whether experience, education, and skills populated as separate blocks. Empty employer rows mean the parser never locked onto your section labels.
When you rebuild from scratch, the free resume builder single-column defaults keep headers in body text so you are not fighting hidden tables.
For a targeted packet, align section keywords with the posting using the job match score tool after structure is stable. Keywords cannot fix misfiled bullets.
Save a version named with the date after each successful parse check. When you tailor for a new role, clone that clean file instead of editing the broken template you started with last month.
If the checker shows skills merged into summary text, rename the summary header to Professional Summary and add a blank line before Experience. Small spacing fixes often unlock header detection without a full redesign.
Labels first, keywords second
How ATS recognizes resume sections comes down to plain headers, predictable date lines, and a single main column. When buckets are wrong, recruiters search empty fields even if your PDF reads well on screen.
Treat section labels like form field names. If you would not invent a random field name on a job application, do not invent a cute header on the resume file recruiters import from that application.
Once experience and skills land in separate buckets, keyword tweaks take minutes. Until then, every hour spent on synonyms is guesswork because the parser never attached bullets to the employer you meant.
Run the six-step audit once per template change, not once per application. Stable structure lets you swap bullets for each posting without fighting the parser again.
After sections import cleanly, add a short note from the cover letter generator so your Greenhouse packet tells one consistent story.
Frequently asked questions
Most US parsers walk the main column in reading order. Contact and summary usually import first, then experience blocks tied to date lines. Sidebars and tables can reorder fields, so a skills rail may land after education even when it looks higher on the PDF.
You can, but many systems only match common labels like Experience, Work History, or Professional Experience. Creative headers often fall into an Other bucket, which means bullets may not attach to employer names in recruiter search.
Often yes. A star or arrow before Skills can strip the word Skills from the stored label. Use plain text headers on their own line with blank space above and below.
Give certifications their own header or list them under Education with a subheading Certifications. Mixing licenses inside Skills without dates makes it harder for parsers to match required credentials on the posting.