By Peter Miller · Published August 31, 2026 · Last updated: September 16, 2026
11 min read
You've got the right keywords somewhere on page two. The recruiter never scrolls that far because line six still reads like a career essay. That's not a mystery algorithm. That's placement.
Candidates swap synonyms at midnight while the summary stays generic and bullet one still says coordinated cross-functional stakeholders. The file didn't move in the queue because the top of the tape never changed.
Run a check your resume for free pass, then open your export in plain text. If the posting's must-have skill does not appear before your oldest job title, reposition before you tailor again.
Below you'll see why order beats density, the narrow cases where education or skills jump up, before-and-after positioning fixes, a copy-paste top-of-file skeleton, and what to change tonight.
Think of the file like a news article, not a biography. The lede carries the claim. Everything else supports it. When your lede is a generic objective, the rest of the story never gets read.
And if you're juggling multiple versions, name files by company plus date, not final_v7. Version chaos causes you to upload yesterday's file where bullet one still lags behind today's posting.
Quick Wins
- Move your target title to line two under your name.
- Rewrite bullet one under your current job before you touch the skills list.
- Delete objectives longer than three lines.
Why how resume positioning impacts ranking more than keyword count
Parsers read in file order. Greenhouse and Lever imports stack lines vertically. Workday search fields often pull employer, title, and dates from the first experience block they recognize. When your headline sits in a sidebar, the system may never attach your current title to the right company even if the word count on skills is high.
Recruiters skim the same top third on screen. They are not reading every bullet on the first pass. They're checking title match, recency, and one proof line. If bullet one is vague, you fall out of the short list before anyone appreciates page two.
Skills sections feel safe because they're easy to edit. They're also easy to overbuild. A forty-item cloud at the top pushes your last role down and duplicates words without showing scope. Matchers still need verbs and outcomes tied to employers.
Summaries fail when they read like personality tests. Three lines that name the target role, industry, and two posting nouns outperform a paragraph about passionate team players.
Volunteer lines and hobbies belong low unless the posting asks for community leadership. They rarely change ranking but they can push revenue bullets off page one when space is tight.
Certifications should sit near skills, not above your last employer. A long training list above experience signals student energy when the req wants someone shipping this quarter.
Remote candidates sometimes hide location at the bottom. Recruiters filtering by time zone read the header first. City and state or time zone on line three prevents silent drops that have nothing to do with keywords.
When two versions of your file differ only by skills order, keep the version where bullet one names scope. A/B tests on section order beat A/B tests on font choice every time in corporate queues.
This won't rescue a role you're underqualified for. It stops qualified files from losing because proof showed up late.
For layout issues that scramble order before positioning even matters, read the safest resume layout for US ATS . For title strings recruiters actually search, see how recruiters interpret job titles .
What to move when ranking feels stuck
Work top to bottom once. Don't rotate keywords at the bottom until the header stack matches the posting level.
Stack one: contact and headline
Before: Name in a banner, email in footer, generic Professional Summary label with no title.
After: Name, target title matching the posting, city and phone on one line, LinkedIn URL if you use it.
Stack two: summary versus skills
Before: Full-width skills grid, then a six-line objective, then experience.
After: Three-line summary with two posting keywords, then experience, then a short Skills block with six plain tools.
Stack three: bullet one under current role
Before: Bullet one says supported leadership on special projects.
After: Bullet one names the system, scope, and outcome: Owned Salesforce pipeline hygiene for 120 enterprise accounts, cutting stale opps 14% in two quarters.
Bullet two can carry collaboration. Bullet three can carry a secondary tool. But bullet one is the billboard. If a recruiter forwards your file internally, they often paste only the top role into chat. Make that paste self-explanatory.
Dates belong on the same line as title and employer when possible. Floating dates in the margin import last in some parsers, which makes your current role look older than it is.
Copy-paste top-of-file skeleton
Copy-paste block (edit brackets)
[Your Name]
[Target Title from posting] | [City, ST] | [phone] | [email]
SUMMARY
[Target Title] with [years] in [industry]. [Outcome verb] [scope] using [tool from posting].
Recent focus: [must-have from paragraph one of job description].
EXPERIENCE
[Current Title] | [Employer] | [Month Year] – Present
- [First eight words include posting noun] … [metric or scope]
- …
Before: Mid-level product marketer, certifications section above internships from college.
After: Certifications moved below last full-time role; first bullet names campaign channel from posting.
I've screened stacks where the skills column was perfect and bullet one still described admin work from five years ago, and the file never surfaced in recruiter filters built around current title plus tool.
Edge case: federal or academic CV norms want publications up front. Corporate US ATS uploads still benefit from a one-page snapshot at the top with title and last role before the long CV attachment if the portal allows two files.
Edge case: career pivot. Put a pivot headline and a projects subsection directly under summary with two bullets that prove the new lane, then chronological roles. Don't bury pivot proof under unrelated titles.
Before and after: operations analyst
Before: Core Competencies header with twenty verbs, current role starts halfway down page one.
After: Summary names analyst lane, bullet one cites SQL and stakeholder count, competencies trimmed to six tools repeated in bullets.
Before and after: customer support lead
Before: Soft skills paragraph, Zendesk listed only in skills rail.
After: Bullet one opens with Zendesk queue ownership and CSAT trend, skills line lists Salesforce Service Cloud once.
So what if your manager title is internal jargon? Translate it in the headline to the market title from the posting, then keep the internal string in parentheses on the experience line. Recruiters search market strings, not legacy codes.
Parents returning from a gap: put a one-line Re-Entry or Consulting header under summary with two bullets proving recent work, then chronological history. The gap explanation can wait for the interview if bullet one shows current skill.
Night-shift applicants should still optimize for East Coast morning skims. That means headline and bullet one ready before lunch their time, not buried after a long skills audit at 2 a.m.
If you're employed, redact client names in bullet one but keep industry and scope. Anonymous proof ranks higher than a polished summary with no numbers because parsers attach verbs to employers even when names are masked.
Multi-page federal conversions to corporate one-pagers fail when everything from page three onward is deleted instead of condensed. Lift the two strongest bullets per role, not the oldest duties.
Healthcare clinicians should keep license and compact specialty on line three, but patient care proof still belongs in bullet one under the latest employer. Credential without context ranks like a skills dump.
Legal candidates: matter lists go after experience unless you're a student. Partners want docket scope in bullet one, not a full case inventory above your current firm.
When breaking the default order still works
Recent grads with thin experience. Education and relevant internships can sit higher if every bullet ties to the posting. Keep the target title on line two anyway.
Licensed roles with credential gates. CPA, RN, or PE lines can sit directly under summary when the posting lists the license as a hard filter. One line, not a full page of coursework.
Contract-heavy histories. A Selected Engagements block under summary beats hiding client work at the bottom, as long as each line still shows title, client industry, and dates.
Before: Skills moved to footer to look modern.
After: Skills returned under experience as plain text; ranking improved because search fields saw tools next to employers.
Trap to avoid: duplicating the same keyword in summary, skills, and every bullet. Repetition without new proof looks like stuffing and wastes the top third.
Before: Photo and QR code in header pushing first job to page two.
After: Photo removed for US corporate upload, QR moved to LinkedIn only, first job visible without scrolling on a laptop screen.
Executive candidates sometimes lead with a board list. Unless the posting is board-facing, keep board lines compact under summary and let operating bullets carry page one.
Technical candidates love GitHub links at the top. Fine if one line. A full project appendix above experience pushes employer proof down. Put repos after experience or in a single Selected Projects block with two lines max up top.
International students on OPT should still lead with the role they're pursuing, not visa status. Work authorization belongs in a single footer line if needed, not in the summary where it replaces skill proof.
Sales candidates sometimes bury quota in bullet four. Quota and attainment belong in bullet one or two when the posting mentions revenue. Marketing candidates do the same with pipeline or ROAS numbers.
Confirm position before you tailor again
Paste the posting into score your job match after you move sections, not before. You want gaps tied to placement, not just missing words at the bottom.
Export the file and run the free ATS checker on the PDF or DOCX you'll upload. If title lines import below skills, fix layout before you argue about synonyms.
When you need a clean master after repositioning sections, open the free resume builder and rebuild the top third in single column before you clone versions per company.
Batch checker runs at the end of each tailoring session while the posting is still open. You'll spot when Workday imports push skills above titles faster than running the checker once a month after silence.
Save a plain-text snapshot after each repositioning pass in a folder named by date. Comparing Tuesday export to Thursday export shows whether bullet one actually moved or you only renamed files.
Cover letters should repeat bullet one proof, not introduce new claims. Use the cover letter generator only after bullet one matches paragraph one on the posting.
Move proof up before you add another skill
Open your master file. Read only the first screen. If you cannot tell what role you're targeting and what you shipped last quarter, reposition tonight.
Swap one bullet, run plain text export, and run a free ATS check before you apply to the next req. Order is the cheap fix. Keyword lists are the expensive distraction.
Job searching is draining. A ten-minute repositioning pass on one master file beats another hour scrolling templates that hide your best line at the bottom.
Share the copy-paste skeleton with a friend who's rewriting bullet five while bullet one still says assisted with tasks. They'll thank you when recruiters finally see the role they're actually targeting.
Read more
Frequently asked questions
Only when skills are plain text and your experience still carries proof. A skills cloud above a weak first bullet can import cleanly yet still lose recruiter skims. Put three to six core tools under a clear Skills header after a tight summary, and repeat each must-have once inside bullet one under your current role.
Not once you have relevant full-time roles. Education belongs after experience for most US corporate screens unless you graduated within the last year or the posting demands a recent degree upfront. Parsers still read education; recruiters weight recent job proof higher when ranking fit.
Directly under contact lines and before experience. Keep it to three lines max with the target title and two posting keywords woven into outcomes, not adjectives. If the summary repeats the skills list verbatim, cut the list or merge them so the top third of the file is not duplicate noise.
Length matters less than what sits on page one. If page two holds older roles while page one buries the current title under icons, ranking suffers from scan order, not page count. Mid-career candidates often need two pages; keep the highest-fit proof in the top half of page one.