12 min read
Your bullets are strong. Your file still lands in silence. Workday shows a Skills block full of tools but an empty Experience tab. Greenhouse filed three jobs under Additional Information. You didn't miss keywords. You missed how parsers read ATS headings.
Parsers map content by heading text first. A label like Where I've Made Impact doesn't route to Experience. It dumps bullets into uncategorized fields while standard Professional Experience imports as employer rows. Before you rewrite bullet one, check your resume for free and paste your export into Notepad. If job titles appear below a block labeled Summary or Misc, fix headings tonight.
Job searching when every upload feels like a black hole is exhausting. You're not failing because you're unqualified. You're often fighting section labels the parser never learned to sort. This page maps symptom to cause so you know which heading to rename before you touch wording.
Below you'll get three causes, tell tests for each, fixes with before/after pairs across roles, two edge cases for career changers and contractors, and a copy-paste heading block. When the posting wants a letter that mirrors your renamed sections, generate a cover letter after your Experience block parses in order.
Quick Wins
- Rename creative section titles to Professional Experience or Work Experience.
- Apply Heading 2 styles in Word or Docs, not bold body text alone.
- Keep one Skills heading after Experience, not two tool blocks with different labels.
- Paste your PDF into Notepad and confirm job titles sit under the Experience label.
The symptom: jobs vanish behind the wrong label
The failure isn't always a blank upload. It's a mis-sorted upload. Lever shows your name and email, then lists Python and Salesforce under Skills while your manager title sits in a field labeled Other or Notes. iCIMS duplicates Education and skips a job because the parser never found Experience as a section header.
Parsers treat heading text like folder names. They match Professional Experience, Work History, and Education against a dictionary of known labels. Content below an unrecognized title often lands in catch-all buckets recruiters never open first.
A composite operations analyst whose resume still used Where I've Made Impact for three roles looked qualified on PDF preview. Workday imported the tools from bullet two but filed every employer line under Additional Information. Same bullets. Wrong folder.
Recruiters ctrl-f posting keywords inside Experience first. When your best bullet lives under a misc field, the human skim never reaches it even if the parser kept the text somewhere in the file.
Taleo and SuccessFactors behave similarly on mislabeled sections. A heading the dictionary does not recognize becomes plain text above a blob. The blob still contains your Salesforce wins. They just do not sort into the Experience tab where the req's must-haves get scored.
You will not see a rejection email explaining the heading failed. You will see silence. That is why the paste test matters before you spend another hour on bullet edits.
For layout failures that scramble order before headings matter, read resume template mistakes that break ATS . Fix column order first if Notepad paste shows Skills before your current title. Then rename headings.
Which ATS headings route bullets into Experience
Three heading failures cover most mis-sorted imports on US corporate stacks. Run the tell test after each block. Only rename what your paste test proves is misfiled.
Cause 1: Creative section titles instead of standard labels
Design-forward resumes replace Professional Experience with My Impact, Career Highlights, What I Deliver, or The Work. Those phrases read well to humans. Parsers often lack a map from them to Experience. Bullets under creative titles import as narrative text, not employer rows.
How to tell: Notepad paste shows your job titles and dates immediately below a non-standard heading. Parse preview lists jobs under Summary, Profile, or Additional Information while Skills populated normally.
Before: Section title Where I've Made Impact with three employer blocks beneath.
After: PROFESSIONAL EXPERIENCE in Heading 2, same three employers with title, company, Month Year dates unchanged.
Cause 2: Bold body text pretending to be headings
Many templates style section breaks with 14-point bold Arial on a normal paragraph. Visually it's a heading. Structurally it's body text. Taleo and SuccessFactors often read those lines as the first bullet of the prior section or drop them entirely.
How to tell: Click the line in Word or Google Docs. If the style bar shows Normal or Body Text instead of Heading 1 or Heading 2, parsers may not treat it as a section break. Notepad paste runs job bullets directly into Education with no clear break line.
Before: Bold 14-point line reading Work Experience with no heading style applied.
After: Same words with Heading 2 style, 12-point bold, blank line before first employer block.
Cause 3: Duplicate or ambiguous section labels
Splitting tools across Core Competencies, Technical Toolkit, and Skills creates three partial lists. Labeling paid jobs under both Professional Experience and Selected Projects without dates on project lines duplicates employers. Parsers merge or drop the second block unpredictably.
How to tell: Parse preview shows Skills twice with different tools in each, or the same employer name appears under two headings. Notepad paste lists Salesforce in three places with no single consolidated block.
Before: Core Competencies sidebar plus Skills footer plus tools repeated in a Summary paragraph.
After: One SKILLS line after Experience: Salesforce, Tableau, SQL, Jira as comma-separated text echoing tools already proven in bullets.
How to tell which cause is yours
Run this three-step diagnostic before you rewrite bullets:
- Export the file you upload. Paste into Notepad. Read top to bottom and note every line that looks like a section title.
- Compare those titles to Professional Experience, Education, and Skills. Flag any creative or duplicate label.
- Upload to a parse check with a recent posting. If must-have keywords match in Skills but Experience shows zero employers, headings misfiled before keyword scoring failed.
Creative titles fix with rename to standard labels. Fake headings fix with real Heading styles. Duplicate labels fix by consolidating to one Skills block and one Experience block. Mixing fixes wastes time when you haven't diagnosed yet.
Copy-paste block: ATS headings that parse on US stacks
[Full Name]
[City, ST] · [phone] · [email] · [LinkedIn URL plain text]
PROFESSIONAL EXPERIENCE
[Job Title]
[Employer], [City, ST] [Mon Year] – [Mon Year]
• [Bullet with tool and outcome in first eight words]
• [Second bullet]
EDUCATION
[Degree], [University], [City, ST] [Year]
SKILLS
[Tool], [Tool], [Tool] (one comma line, no duplicate tool headings)
Fix walkthrough: marketing coordinator with creative title
Before: Section My Campaign Wins holds Manager, Brightline Media and two prior roles. Greenhouse filed all three under Profile text.
After: PROFESSIONAL EXPERIENCE heading. Same employers. Bullet one under Brightline: Managed paid social in Meta Ads Manager with 18% lower cost-per-lead over two quarters. Parse check shows three employer rows in Experience.
Fix walkthrough: nurse with styled text headings
Before: Bold lines Clinical Background and Licenses & Certifications with no heading styles. Workday merged license lines into the last job bullet.
After: PROFESSIONAL EXPERIENCE and EDUCATION as Heading 2. Licenses listed under Education as plain lines: RN, State of Texas, 2022. Paste test shows clean breaks between sections.
Fix walkthrough: software engineer with split Skills headings
Before: Technical Skills table, Programming Languages bullet list, and Cloud Platforms icons in a sidebar. Parser imported Python from sidebar only.
After: Single SKILLS line: Python, Go, AWS, Kubernetes, PostgreSQL. Tools already named in Experience bullets. Duplicate headings removed.
Edge case: career changers with a Projects block
Use Relevant Projects only when each entry carries Month Year dates, project name, and two bullets with posting keywords. Put paid work under Professional Experience. Do not label unpaid portfolio work as Experience without dates. Parsers still need employer-shaped lines.
Edge case: contractors with many short engagements
One PROFESSIONAL EXPERIENCE heading can hold multiple clients if each block has client name, role title, and date range. Avoid Consulting Engagements as the only label without client names on separate lines. Recruiters search client names; parsers attach bullets to the nearest recognized heading.
A composite DevOps contractor kept Client Work as the section title. Greenhouse imported two clients correctly and dropped four because the parser treated the third block as continuation of Education. Renaming to PROFESSIONAL EXPERIENCE with client names on separate lines fixed import without changing a single bullet verb.
For bullet shape after headings parse, read how to write resume experience ATS understands . Headings open the folder. Bullets still need Month Year dates and employer lines inside it.
Heading traps beyond the three main causes
Using Summary or Profile as a second Experience block. A long summary paragraph above jobs is fine. Labeling job bullets under Profile because the template styled that box as a header misfiles roles. Keep jobs under Experience only.
Mixing UK and US section names on one file. Personal Statement plus Professional Experience on the same US corporate req confuses parsers trained on US labels. Pick US standard headings for US employers.
Hiding certifications under random titles. Licenses & Credentials, Continuing Education, and Professional Development split one cert list across three misc fields. Consolidate under Education or a single Certifications sub-block with plain lines.
Renaming headings without re-exporting. Changing a title in Word but uploading yesterday's PDF leaves the old label in the file employers receive. Re-export after every heading edit and re-paste into Notepad.
Keyword stuffing inside heading lines. PROFESSIONAL EXPERIENCE | SQL | PYTHON | AWS reads as a corrupted label. Keep headings clean. Put tools in bullets and one Skills line.
Assuming the ATS reads your PDF visually. Color bands and icons beside heading text do not help parsers. Standard text labels with heading styles beat designed section dividers every time.
Moving Education above Experience because the template looked balanced. Most US corporate parsers expect Experience first after contact. Education above jobs can still parse, but recruiters scanning top-down see degree before scope. Keep Experience first unless you are a new grad with one internship.
This won't fix applying to roles you're not qualified for. It stops qualified files from losing when Workday filed three years of jobs under Additional Information because the section title wasn't on the parser's map.
Parse check after you rename sections
After you rename headings and apply real Heading styles, run the same export against the req on your screen. You're confirming employer rows land under Experience, not under misc fields, before you tune bullet wording.
Upload your renamed file to HireFlow's free ATS resume checker . If job three still imports under Summary, the heading isn't fixed yet.
When you're rebuilding section structure from scratch, build your resume with standard Experience, Education, and Skills headers so you don't reintroduce creative labels on the next edit.
Do this now: Paste your PDF into Notepad. If job titles sit below a label other than Experience or Work Experience, rename that heading before you rewrite a single bullet.
Rename headings, then resubmit
ATS headings decide which folder your jobs land in. Creative titles, bold body text, and duplicate Skills labels misfile strong bullets before a recruiter opens the profile. Standard Professional Experience, Education, and Skills headings route content correctly on Workday, Greenhouse, Lever, Taleo, and iCIMS.
Paste your export into Notepad tonight. If job lines sit under the wrong label, rename sections and apply Heading styles before you touch bullet wording. Then run a free ATS check with the posting attached and confirm employer names appear under Experience, once, in date order.
- Replace creative section titles with Professional Experience or Work Experience.
- Apply Heading 2 styles instead of bold Normal text for section breaks.
- Consolidate split Skills blocks into one comma line after Experience.
- Re-export after every heading change and re-paste into Notepad.
- Fix layout columns first if Skills still imports before your current title.
And if a template markets itself as ATS optimized but uses My Journey for jobs, rename the heading anyway. Parsers read labels, not marketing badges.
Read more
Frequently asked questions
You do not need word-for-word matches on every platform, but close variants parse most reliably: Professional Experience, Work Experience, or Employment History for jobs; Education for degrees; Skills or Technical Skills for tools. Creative titles like Where I've Made Impact or My Journey often land bullets in uncategorized or summary fields in Workday and iCIMS. Rename the heading before you rewrite bullets.
Yes when the line is a real heading style, not bold body text. PROFESSIONAL EXPERIENCE in Heading 2 or bold 12-point Arial parses the same as title case for most US corporate stacks. ALL CAPS alone does not fix a heading the parser does not recognize. Pair caps with a standard label recruiters expect.
After Experience for most US corporate roles. Parsers read top to bottom. A Skills block above jobs can import tools before your current title in Greenhouse, which makes keyword matches look like your headline skill instead of job scope. Put Skills after Experience unless the posting is entry-level and your tools are the proof.
Use Professional Experience or Work Experience when the unpaid role proves posting keywords and carries Month Year dates. Use Volunteer Experience or Relevant Projects when you need a separate block. Avoid Community Involvement or Giving Back as the only label without dates on each line. Parsers map by heading text first, then hunt employer names under it.
Export the same file you upload, paste into Notepad, and read section order top to bottom. Upload to a parse check with the posting attached. If job bullets appear under Additional Information or Summary while Skills duplicated, rename headings to standard labels and re-export before you touch keyword density.