11 min read
US applicant tracking systems read your file top to bottom in export order, not visual layout. Name and contact lines parse first when they're in the body. Work Experience usually follows if nothing jumps ahead of it. A sidebar Skills block can parse before your current job when columns reorder the stream.
Check your resume for free on the same export you'll upload. Workday, Greenhouse, Lever, and iCIMS don't skim like a recruiter with a highlighter. They build a candidate profile from the first pass. When the wrong block lands first, your strongest bullet can sit under Skills while a tool list looks like your employer line.
You're not failing because you lack keywords. You're losing screens when parse order puts Education above Experience or stuffs phone numbers into the summary field. Job searching is exhausting. This page shows which blocks US systems ingest early, what breaks that order, and how to rebuild a file you can submit tonight without guessing.
Below you'll see the bar a parse-safe file must clear, before/after pairs for the section swaps recruiters notice in list view, mistakes that keep Skills on row one, and a copy-paste section skeleton. If you've been tailoring bullets while a two-column template still parses left rail first, fix order before you tweak verbs.
When the portal asks for a cover letter after upload, don't repeat the same scrambled lines. Generate a cover letter from the corrected resume text so the note matches the employer order you fixed in Word.
Quick Wins
- Move phone and email out of Word headers into the body under your name.
- Flatten two-column templates so Experience precedes Skills in plain text.
- Use standard section headers: Work Experience, Education, Skills.
- Paste the PDF into Notepad once and read block order top to bottom.
What US parsers mean by ATS resume sections read first
"Read first" sounds like recruiter priority. On US corporate portals it usually means file parse sequence: the order text exits your DOCX or PDF into profile fields. Fonts and colors drop. Section order is what survives.
The bar your file is judged against: plain-text export reads contact, optional summary, Experience with Month Year dates paired to employers, Education, then Skills. Each employer line stays attached to its title and bullets. Nothing from a sidebar jumps ahead of your current role.
Workday and Greenhouse sit on most US req stacks I've screened. Taleo and iCIMS still show up on legacy enterprise flows. Naming them is fine. Claiming how they rank candidates is not. Stick to what you can observe: preview tabs, parsed profiles, and a Notepad paste of your export.
A composite operations analyst whose Skills rail parses first looks like their top job is SQL, Looker, and Python. The real employer line drops to row four. Same career, same keywords. Different screen because layout drove parse order, not because the posting changed.
Edge case: you're returning after a gap and used a functional-style skills block up front. Parsers still read top to bottom. Put a dated contract or consulting line before the skills list so tools attach to a real employer, not a floating rail.
Edge case: you're a new grad with projects above Experience. Label the block Projects under Education or fold projects into Education with dates. A header that reads Portfolio can parse as stray sentences recruiters cannot filter.
Read resume rejected by ATS for the wider filter story. This page is section order on US upload, not keyword density alone.
Multi-page files add noise. Page-two headers with your name restart parse loops. Section breaks between Experience and Education can insert blank rows that read as gaps. Keep one continuous flow when you can. If you need page two, don't repeat contact blocks at the top.
Reorder ATS resume sections before you tailor bullets
Tailoring helps after parsers can find your current job. These pairs show layout choices, what US systems tend to do with section order, and the export fix. Swap in your employers and tools. Illustrative titles only.
Pair 1: Skills sidebar above Experience
Before: Left column lists twenty tools. Right column holds jobs. Canva-style grid with colored sidebar.
After: Single column, 11-point Calibri. Skills appear inside dated bullets or one short list after Experience. Plain-text paste shows employer before tool names.
Parsers often read down the left column first. Your Salesforce and Tableau lines become the opening "job." Fix the column, then tailor keywords inside Experience bullets.
Pair 2: Contact block in header/footer
Before: Phone, email, and city live in a Word header on every page. Name is centered in the body.
After: Name on line one, city and phone on line two, email on line three, all in the body. No header or footer content.
Headers parse early but map badly. Greenhouse may stuff your mobile number into a name field while your summary shifts below Education. Recruiters see contact soup before bullet one.
Pair 3: Education moved above Experience for a career change
Before: New degree block sits above a decade of unrelated roles to signal the pivot.
After: Experience stays first with a clear pivot bullet under the most recent employer. Education follows with degree, school, and Month Year graduation date.
Filters weighted toward recent titles still scan Experience first in list view. Lead with a dated role, even contract work, before the degree block unless you're a new grad with no roles to show.
Pair 4: Certifications table above jobs
Before: Bordered three-column table: Certification | Issuer | Year sits above Work Experience.
After: Active certs on line two under email. Each role lists relevant certs in bullet one with Month Year employer dates.
Tables flatten into one run-on line or reorder cells by row. A nurse's ACLS line can separate from the hospital role that required it.
Pair 5: Marketing manager with summary in a text box
Before: Gray shaded text box beside the name with a three-line summary. Skills icons in a left rail.
After: Summary as two plain lines under contact, same width as Experience. Tools named inside bullets under the employer that used them.
Before: Drove pipeline across SaaS segments; strong HubSpot and Salesforce skills.
After: Jan 2022 to Present · Marketing Manager · CloudTools Inc · Owned mid-market pipeline in HubSpot and Salesforce; lifted MQL-to-SQL conversion 14% in FY24 through nurture tests and sales handoff SLAs.
Pair 6: Software engineer with GitHub in footer
Before: github.com/handle and portfolio URL in a footer on every page. Kubernetes and Terraform icons in a left rail above jobs.
After: github.com/handle on line three under email in the body. AWS and Kubernetes inside bullets under the employer where you ran production traffic, with Month Year dates.
Footers compete with Education for the last parse pass. A preview may show your repo link as a stray sentence while your current title drops off page two.
Six moves to set section order tonight
- Open the source Word file, not the PDF you last submitted.
- Move contact into the body on lines one through three. Delete header and footer contact repeats.
- Flatten columns and tables into one vertical column.
- Set headers in this order: Work Experience, Education, Skills (Certifications optional after Skills).
- Paste the export into Notepad. Read block order once. Fix anything that jumps ahead of your current employer.
- Export PDF from that file. Open the portal preview if it exists before you hit submit.
Copy-paste US section-order block
Paste this at the top of a blank Word doc and replace bracketed lines:
[Full Name]
[City, ST] · [Phone] · [[email protected]]
[Optional two-line summary with title level and scope]
Work Experience
[Month Year] to [Month Year or Present] · [Employer] · [Title]
[Bullet with verb, scope, tool, and outcome]
Education
[Degree] · [School] · [Month Year]
Skills
[Comma-separated tools tied to roles above, or one short list]
Export PDF from this file only. If employers still scramble in preview, try DOCX upload from the same source. See Workday upload preview fixes when the portal shows a parsed profile tab after upload.
Where section order still breaks on US uploads
Trusting visual order because the PDF looks fine. Recruiters may open the attachment later. The parsed profile already buried your current role under Skills.
Renaming headers without flattening columns. My Journey instead of Work Experience still parses left rail first when the grid stays. Standard labels plus one column is the combo.
Repeating contact info in header, footer, and body. Duplicates fight for the same fields. Pick one body block and delete the rest.
Using design templates with invisible tables. Many online resume builders hide grid lines. Workday still reads the grid and can treat cell one as your first employer.
Uploading a scan of a printed resume. OCR guesses characters. Section headers and dates are the first casualties, which scrambles order even when the paper looked clean.
Stuffing keywords into a sidebar after a failed upload. More text in the wrong column makes parse order worse, not better. Flatten first, then tailor bullets under the right employer.
Skipping the preview because you're applying on mobile. Wait until you can open the desktop preview once. A scrambled upload is harder to fix after submit on some reqs.
Applying fixes only to page one. A clean first page with a two-column page two still scrambles the full profile. Scroll the entire doc before export.
Assuming every US company configures portals the same way. Preview steps vary. Plain-text export order is the constant you control tonight.
Confirm section order before you hit submit
Run the export through the free ATS checker with the job description pasted in. You're confirming employer-title pairing and whether Skills landed before Experience, not chasing a perfect score.
Then score your job match on the same plain-text order. Keywords only help after parsers attach them to the right job line. A high match on a scrambled file still loses to a readable lower score.
Set ATS resume sections in parse order tonight
ATS resume sections US systems read first are really about export sequence, not how pretty the PDF looks on your screen. Contact in the body, Experience before floating Skills rails, standard headers, and one plain-text paste catch most US upload surprises before a recruiter opens list view.
Pick the next req on your list. Apply the copy-paste section block. Run a free ATS check. Open the preview if the portal shows one. Upload when employer lines stay paired with the right titles and Skills no longer masquerades as your current job.
This won't fix applying to roles you're not qualified for. It does stop qualified candidates from losing screens because their best bullet landed under Skills while a sidebar full of tools became their fake first employer.
When you need a clean base file, build your resume in a single-column layout before you tailor for the posting. Parse order first. Keywords second.
Read more
Frequently asked questions
Not by design, but often in practice when Skills sits in a left column or table above the body. Parsers read export order top to bottom. A sidebar full of tools can become the opening block while your current employer drops to row five. Put Skills after Experience in a single column unless the posting asks for a short list near the top in plain body text.
No. Headers and footers parse early but map to the wrong profile fields in Workday and Greenhouse. Phone lines land in name slots. Email can overwrite summary text. Keep name, city, phone, and email in the body on lines one through three. That is the contact block parsers attach to your candidate record.
Standard English headers parse most reliably: Professional Experience, Work Experience, Education, Skills, Certifications. Creative labels like My Journey or Core Competencies may still extract text but fail to bucket it where recruiters filter. Boring headers are a feature when you need Experience to stay Experience in list view.
They read it when it is normal body text under contact lines. Summaries inside text boxes, shaded callouts, or floating objects often parse last or drop entirely. If you use a summary, keep it as two plain lines under email, same width as your job bullets, with no borders or icons.
Renaming headers alone will not fix column-driven reorder. Flatten to one column first, then set section order: contact, optional summary, Experience with Month Year dates, Education, Skills. Paste the export into Notepad and read top to bottom once. That sequence is what most US portals approximate on upload.