11 min read
You've heard recruiters skim fast. What almost nobody explains is the scan pattern itself: title and company strip first, first eight words of bullet one second, two bullets per role on a first pass, then ctrl-f for a must-have from the posting. Generic advice about keywords and formatting doesn't name those beats.
Check your resume for free with the job description pasted in. You'll often see matched terms in Skills while bullet one still opens with supported initiatives. The parser might pass you. A human scan in Workday or Greenhouse stops on the strip and the first line, not page three.
Below you'll walk through the six-beat pattern I use on US corporate reqs, five edits you can run tonight with before/after pairs, two edge cases, and what still kills files after the layout is clean. Job searching's exhausting. This page tells you where eyes land so you're not guessing.
Pull up your latest PDF before you read on. We're going to trace the same path a recruiter's eyes take, beat by beat.
Quick Wins
- Put job title, company, and Month Year dates on one clean strip per role.
- Rewrite bullet one so a posting must-have lands in the first eight words.
- Move your second-best metric into bullet two under the same employer.
- Ctrl-f your PDF for three must-haves from the ad and fix any gaps in Experience.
How recruiters actually scan resumes in the USA: the six-beat pattern
Blog posts talk about a mythical six-second glance like it's random. On US corporate reqs in Workday, Greenhouse, Lever, and iCIMS, the glance follows a pattern. Once you see it, you'll know exactly which lines to fix first.
Beat 1: Title-and-company strip. Eyes hit the job title, employer name, and dates before any bullet. If the title is too junior, too creative, or the dates parse wrong, the role gets skipped. Match the posting's level when honest: Senior Marketing Manager, not Marketing Guru.
Beat 2: First eight words of bullet one. That's the hook. Supported cross-functional projects loses here. Owned Salesforce CRM pipeline for 38 enterprise accounts wins because the tool and scope show up immediately.
Beat 3: Bullet two, if bullet one earned it. One strong line often buys a second look. Weak bullet one means bullet two never gets read.
Beat 4: Current role only on many first passes. If your latest job block is thin, recruiters may never scroll to older wins. Front-load proof under the employer that ended most recently.
Beat 5: Ctrl-f for posting must-haves. I search the PDF for the top three terms from the req: HubSpot, SOX, Kubernetes, whatever repeats. If they're only in Skills, the file often stalls even when the checker said match.
Beat 6: Layout sanity check. Two-column templates, icon rows, and text boxes can look fine on screen and import as scrambled lines. Single-column PDF, plain headings, Month Year dates inline.
A composite operations analyst whose strip says Coordinator while the req asks for Senior Analyst gets cut at Beat 1. Another file with the right title but bullet one starting with assisted with reporting dies at Beat 2. Same queue, different failure point.
Read what recruiters actually see after ATS screening when you're unsure whether a human or a parser rejected you first. This page is the human scan after the file opens.
Five edits that match how recruiters scan
These steps follow the scan order. Fix strip before bullets, bullet one before bullet five. Each step includes a before/after pair you can paste against your file.
Step 1: Clean the title-and-company strip
Open your PDF at the role you want scored. The strip should read like a ledger line: title, employer, start and end Month Year. No graphics between title and company. No floating dates in a sidebar.
Before: Marketing professional with creative layout; employer name in a colored sidebar; dates missing on contract work.
After: Digital Marketing Manager | Northwind Health | Mar 2022 to Present on one line, left-aligned, 11-point Calibri or Arial.
Step 2: Rewrite bullet one for the first eight words
Pull the heaviest must-have from the posting. Put it in word one through eight under your current job. Verbs can follow. Outcomes close the line. That's the beat most generic resume advice never names.
Before: Responsible for paid media campaigns and reporting for the growth team.
After: Managed $420K quarterly paid social across Meta and LinkedIn; cut cost per qualified lead 18% in H1 2025 while holding lead volume flat.
Step 3: Put your second proof line in bullet two
Recruiters who liked bullet one often read exactly one more line. Don't waste it on a duty. Stack a different dimension: channel, tool, or metric the posting cares about.
I've screened batches where bullet five held the only HubSpot proof while bullet one said helped with email. The ctrl-f at Beat 5 sometimes found it. The first-pass scan never did.
Before: Bullet two: Attended weekly standups and coordinated with design.
After: Bullet two: Built HubSpot nurture workflows for 12 lifecycle segments; lifted MQL-to-SQL conversion from 11% to 16% over two quarters.
Step 4: Run the ctrl-f test from the posting
Copy three must-haves from the job description. Search your exported PDF. Each should appear inside a dated Experience block, not only in Skills or a summary footer. If a term hits only in Skills, move it into bullet one or two with scope.
Before: Tableau appears six times in Skills, zero times under a company name.
After: Bullet under current role: Built Tableau dashboards for finance and ops; automated 9 weekly reports and cut manual prep from 5 hours to 45 minutes per cycle.
Step 5: Export single-column and paste into Notepad
Beat 6 is where pretty templates die. Save a one-column PDF. Paste into Notepad on Windows or TextEdit plain mode on Mac. Employer names should stay in reverse chronological order with bullets attached to the right company.
Before: Canva two-column layout; Skills rail imports between job blocks.
After: Single column: Contact, Experience with Month Year strips, Education, Skills echo at the bottom.
Copy-paste bullet skeleton for the first eight words
Copy-paste and fill honestly: "[Must-have from posting] + [verb] + [scope] + [outcome with number you can defend]." Example: "Owned Salesforce CRM pipeline for 42 regional accounts; standardized stage fields and raised forecast accuracy on opps above $50K in FY2024."
Count the opening words. If the posting must-have is not inside word eight, slide it left. Everything else can compress after the hook lands.
Edge case: career change with a new title strip
Your strip might not mirror the posting yet. Use an honest title: Career Transition Program Graduate or Project Coordinator when that's true. Bullet one still carries transferable proof: Jira, stakeholder alignment, budget tracking. Do not invent Senior Director on the strip to game Beat 1.
Before: Strip says unrelated title with no bridge in bullet one.
After: Strip stays honest; bullet one leads with the skill the new req searches: Coordinated 4 cross-functional workstreams in Jira for a product launch; delivered MVP on schedule with $1.2M scoped budget.
Edge case: contract roles stacked in one block
Parsers and humans both need separate strips per client. One merged paragraph with twelve tools and no dates fails Beat 1 and Beat 4. Split each engagement with Month Year ranges and put the strongest win in bullet one for that client.
Before: Independent Consultant 2019 to 2023 with one bullet listing every client tool.
After: Separate lines: Marketing Analyst | Client A | Jan 2022 to Jun 2023 with two bullets; repeat for Client B with its own strip and dates.
See why weak bullet points get ignored when Beat 2 keeps failing even after the strip looks right.
Where scanned resumes still get skipped
Keyword clouds in place of bullet proof. Skills footers do not survive Beat 5 when Experience stays generic. Move three terms into dated lines tonight.
Six equal bullets per job. Recruiters rarely read six on a first pass. Lead with two strong lines; trim or merge the rest.
Creative job titles on the strip. Brand Storyteller reads pretty and fails level match on corporate reqs. Use the market title when it's accurate.
Burying the req's top tool in bullet four. Promote it to bullet one for that apply. You can swap bullet order per posting without rewriting the whole file.
Assuming the ATS screen equals the human scan. Parser match gets you opened. Beats 1 through 5 decide callback. Optimize for both, starting with the strip and first eight words.
Uploading the Word file when the portal asks for PDF. Formatting shifts between exports. The scan pattern assumes a stable PDF layout. Export once and review beats on that file.
Test your file against the posting before you upload
After you fix the strip and bullet one, paste the job description into Run a free ATS check. You're confirming must-haves appear in Experience text, not only in Skills.
Then score your job match on the same export. Gaps on tools that already sit in bullet two tell you which beat still needs a move left on the page.
When a recruiter call follows, the same lines you fixed for Beat 2 are the lines you'll repeat aloud. Read how to prepare for a recruiter screening call to line up the scan with what you say on the phone.
Match the scan pattern before you upload again
How recruiters actually scan resumes in the USA is not a mystery once you name the beats: strip, first eight words, second bullet, current role, ctrl-f, layout check. Fix in that order and you'll feel the file get tighter even before you hear back.
Open tonight's posting. Fix the strip on your latest role. Rewrite bullet one so the must-have lands in word eight. Stack bullet two with a second metric. Export single-column PDF and run a free check. When the portal wants a letter, generate a cover letter that repeats the same figure from bullet one.
This won't fix applying ten levels above your scope. It does stop qualified candidates from losing on Beat 2 while their best proof sat in bullet six.
And if you're applying to multiple reqs this week, swap bullet one per posting. The strip stays stable. The first eight words change with the must-have on your screen. Same career, different hook.
Read more
Frequently asked questions
On a first pass in a full queue, yes. That pass is not random. You get a title-and-company strip, the first eight words of bullet one, maybe bullet two, then ctrl-f for a must-have from the posting. If those beats are blank or generic, many files never get a second read even when the rest of the page is strong. Fix the strip and bullet one before you worry about font choice.
The single horizontal line at the top of each job block: job title, employer name, and Month Year dates on one line or stacked within two lines. In Workday and Greenhouse I scan that strip before I read any bullet. If the title does not match the req level or the dates look off, I may skip the role entirely. Put the title the posting uses when it is honest, and keep dates in a format parsers import cleanly.
That is where eyes land on a skim. Verbs like supported, assisted, and responsible for burn the opening. Lead with the tool, channel, or outcome the posting searches: Salesforce CRM, paid social, Tableau, or cut churn. The rest of the bullet can carry scope and proof. If the must-have sits at word fourteen, many first passes never reach it.
Often two, sometimes one if bullet one is weak. I rarely read six bullets under a single employer on a first screen. Put your strongest proof in bullet one and your second-best in bullet two. Older roles can stay shorter. Burying your best campaign or pipeline win in bullet five is a self-inflicted skip.
Only if it repeats proof that also sits under a dated employer line. A keyword-stuffed summary without matching bullets reads like SEO, not experience. If you use a summary, keep it to two lines and make sure the same terms appear in bullet one under your current job with Month Year dates. Many recruiters jump straight from the title strip to Experience.