9 min read · Order beats keyword stuffing
Your resume looks complete on screen. The portal import tells a different story: phone number in the skills field, last employer missing, summary paragraph sitting above your name. That's not bad luck. It's section order and labels the parser didn't recognize, and it won't fix itself on the next upload.
Most applicants assume every block gets equal weight. They don't. Corporate stacks in Workday, Greenhouse, Lever, Taleo, and iCIMS read like a tape: contact, current title, experience rows, then everything else. When you're qualified but invisible, the fix usually isn't more adjectives. It's moving proof where the tape starts, and you'll feel the difference on the paste test.
You can't control how a recruiter skims. You can control which fields populate clean on import. If bullet one under your current role still reads "Responsible for weekly reports," the parser saw it. The matcher just didn't score it.
Before you reorder anything, check your resume for free and copy the imported text into a plain editor. Compare that paste to your PDF. Gaps between them show which sections never made the trip.
Below you'll get direct answers on import priority, how to stack sections without breaking pairing, header traps that blank whole blocks, a copy-paste order checklist, and a short test loop before your next apply batch.
Quick Wins
- Put name, phone, and email in plain text on lines one through three.
- Name the posting must-have in the first eight words of bullet one under your current role.
- Label sections Work Experience, Education, and Skills exactly.
- Paste imported text after every template change.
What are the resume sections ATS reads first?
Think import order, not importance to a human. Parsers build fields from predictable anchors. Contact lines establish who you are. The first Experience heading pair becomes your current role anchor. Everything after attaches to the nearest label the system recognizes.
Contact imports first. Name, phone, email, and city or state should sit in the body, not a decorative header. Parsers map these to applicant profile fields before they touch narrative text. A missing email because it lived inside a text box is a silent fail.
Current job title and employer come next. The top Experience row sets the anchor for tenure filters and title search. If your real current role sits third because you listed freelance work above it, matchers may score the wrong row as "current."
Bullets under that role carry more weight than a Skills list. The same keyword in a bullet with an outcome beats the naked tool in a grid. Parsers read bullets sequentially. Matchers often treat early tokens in Experience as primary evidence.
Summary text imports early but scores lighter. A tight two-line summary helps humans. It rarely rescues a thin Experience block. Do not hide must-have tools only in the summary when bullet one stays generic.
Skills, Education, and Certifications follow. They still matter for keyword hits and degree gates. They rarely outrank a well-written bullet on page one. Duplicate skills that already appear in bullets add length without adding match.
I've screened imports in Greenhouse where a "Core Competencies" block above Experience caused the parser to treat skills as the current job title, and the candidate spent a week adding synonyms instead of moving one bullet.
Volunteer, projects, and publications import last unless you placed them high visually. Side columns and text boxes can pull those blocks ahead of Experience in the character stream even when they look lower on the PDF.
For layout rules that keep this order intact, see the safest resume layout for US ATS . Two-column templates scramble the sequence before section labels even matter.
How do you stack sections so matchers catch proof early?
Work top to bottom in the import tape, not in design software. Each move should survive a plain-text paste test.
Step 1: Lock contact in the main flow
One column. No icons for phone or email. No "CV" or "Resume" header line above your name.
Before: Email inside a Word text box in the margin; parser left the field empty.
After: Name, phone, email, and Denver CO on three plain lines; import populated contact on the first pass.
Step 2: Open Experience with the role the posting targets
Reverse chronological order. Employer, title, Month Year to Month Year or Present. Bullet one names a must-have from paragraph one of the posting in the first eight words.
Before: Operations Manager bullets opened with "Oversaw daily tasks."
After: "Lean Six Sigma process mapping cut dock wait 18% across four sites in Q2" led bullet one; posting must-have landed in the first line.
Step 3: Place Summary after contact, before Experience
Two lines max. Mirror the target title from the posting. Repeat one must-have you will prove again in bullet one. Skip objective statements and soft skill lists here.
Step 4: Skills after Experience, not before
List tools you already proved in bullets. Cut duplicates. Long grids push page breaks that scramble later sections.
When skills lists balloon, read why skill overload hurts ATS scores before you add another column of tools.
Copy-paste block: section order checklist
Copy-paste checklist (top to bottom)
{`[ ] Contact: name, phone, email, city/state (plain text, no text boxes)
[ ] Summary: 2 lines, target title + one must-have you'll repeat in bullet one
[ ] Work Experience: reverse chronological, standard heading
[ ] Bullet one under current role: posting must-have in first eight words
[ ] Skills: tools not already proven in bullets; no duplicate grid
[ ] Education: degree, school, graduation year on one line each
[ ] Certifications: directly under Experience if posting lists license in paragraph one
[ ] Paste-test imported text: contact → title → bullets in order`}
Step 5: Run the paste test after every reorder
Upload the file to the portal preview when you have it. Copy all imported text. Read once top to bottom. If Skills appears above your current employer, move the block or fix columns before you tailor keywords.
Before: Skills section sat in a right column; paste showed Salesforce above the current job title.
After: Single column; Salesforce appeared inside bullet two under the correct employer.
Which headers make parsers skip whole blocks?
Creative labels feel modern on paper. Parsers map to a fixed field list. Unknown headers become unlabeled body text.
Renaming Work Experience. Career Highlights, Impact Wins, and Professional Journey often fail to map. Use Work Experience or Professional Experience every time.
Leading with Skills or Core Competencies. Matchers see tools before titles. Recruiters searching title plus employer get empty pairs. Move proof into bullets, then mirror spare tools below.
Burying licenses on page two. Nursing, finance, and security roles gate on certs named in paragraph one. A cert line under volunteer work imports late. Put RN, CPA, or CISSP where Experience ends.
Using tables for dates. Parsers pair dates with the nearest text line, not your visual grid. Flatten to employer, title, dates, bullets.
Before: "Selected Wins" header above three bullets; import dropped the block entirely.
After: Same bullets moved under Work Experience with the employer line restored; import scored the metrics.
This will not turn a stretch role into a fit. It stops qualified files from losing match because the parser never mapped the section that held the proof.
Should you parse-test before reordering sections?
Yes. Section moves change the import tape. Test the exact file you will upload, not an older one-page draft mixed with tonight's edit.
Run the free ATS checker after you paste-test. Parse errors belong in the edit session, not after ten portal submits. If contact imports clean but match stays low, tune bullet one before you touch the Skills grid.
Rebuilding from scratch? Use the free resume builder with standard headings so you are not fighting a template that puts Skills in a sidebar. When the posting asks for a letter, draft it after page-one bullets match paragraph one via the cover letter generator .
Do this now: Paste imported text. If Skills sits above your current title, fix layout before you add another keyword.
What to reorder on page one tonight
Resume sections ATS reads first are contact, your current title row, and the bullets directly under it. Everything else supports that anchor or arrives too late to save a thin match.
Open the posting. Fix bullet one. Run the checklist. Paste-test the import. Retest the checker on the file you will actually submit.
Job searching is already draining when the file looks fine on your screen. A clean import saves another week of synonym edits that never touched the real order problem.
Read more
Frequently asked questions
Usually no. Most corporate parsers import contact lines first, then scan Experience headings and bullets before a standalone Skills block. A skills grid can still add keyword hits, but matchers often weight the same tool inside a bullet under your current role more heavily. Put must-have tools in bullet one on page one, then mirror them in Skills only if you have room.
It can. Headers like Professional Profile or Career Narrative sometimes fail to map to the summary field in Workday, Greenhouse, Lever, Taleo, or iCIMS. The text may still import as body copy, but out of order. Use Summary or Professional Summary as the label unless the portal gives you a custom field name to match.
Top of page one, plain text. Headers and footers repeat on page two in many templates, and parsers can treat those repeats as body text. That pushes real bullets down or duplicates phone numbers inside the skills field. Keep name, phone, email, and city on line one through three in the main flow.
Directly under your current role bullets or in a Certifications block immediately after Experience, before Education. Late-page cert lines get parsed, but matchers that weight early tokens may never score them. If the license is a hard gate, do not bury it under volunteer work on page two.