I have watched a lot of people sort resumes. Not skim them in some abstract sense, but sit at a desk with a stack of forty applications and a meeting in twenty minutes, deciding which six to call. The thing nobody tells you about resume writing is that the document you labored over is almost never read the way you wrote it. It is scanned. The recruiter is hunting for a small set of signals, and the rest of the page is, for the first pass, mostly noise.
The good news is that the scan is predictable. Recruiters look in the same places, in roughly the same order, every time. Once you understand the pattern, you can stop fighting it and start writing for it. That is most of the job. Good resume writing is not about saying more. It is about putting the right four or five things exactly where a tired person will look for them.
The six-second scan is real, and it has a shape
The famous claim is that a recruiter spends about six seconds on a resume before deciding whether to keep reading. The original eye-tracking study put it closer to seven, and a follow-up tightened it further. Argue about the exact number if you like. The behavior is the point, and it is consistent: a recruiter does not read top to bottom. They jump.
The eye-tracking heat maps show a clear path. In the first pass, the recruiter looks at your name, then your current title and company, then the dates on that role, then your previous title and company and its dates, and then your education. That is the spine. Only after that, if you have survived, do they do a quick top-down skim of the rest, mostly catching bolded words, numbers, and the left edge of each line.
Read that order again, because it tells you how to build the page. The recruiter is reconstructing a story in five glances: who are you, what do you do now, for how long, what did you do before, and how were you trained. If any one of those is hard to find, the scan stalls, and a stalled scan is usually a no.
Write the top third like it is the whole resume
Almost every decision happens in the top third of page one. That real estate is the most valuable thing you own in a job search, so treat it that way. Your name should be the largest text on the page and unambiguous. Directly under it, give a one-line summary of who you are professionally, not a mission statement. "Senior data engineer, eight years, payments and fraud" does more in eight words than a paragraph about being passionate and results-driven.
Then comes your current role, and this is where most resumes quietly fail. The recruiter wants title, company, and dates in one clean glance. Do not bury the title inside a sentence. Do not put the company in gray six-point type. Make the line scannable: title on the left, company next to it, dates flush right. If a recruiter has to work to figure out what you currently do, you have already lost a second you did not have.
One opinionated rule I will defend: keep it reverse-chronological. Functional resumes that group skills and hide dates feel clever, but they break the exact pattern the recruiter is scanning for. The instinct that you are hiding something kicks in fast. If you have gaps or a winding path, address them plainly in the role descriptions rather than rearranging the whole document to obscure them.
Results before responsibilities, and never bury the win
Here is the single most useful resume tip I can give you. When the recruiter does that top-down skim, their eyes catch the start of each bullet and any number on the line. So put the result first and the responsibility second, and make sure the number is visible.
Most people write the inverse. They lead with the task and tuck the outcome at the end, where it dies.
Example: instead of "Responsible for managing the email program and improving engagement metrics over time," write "Grew email revenue 38 percent in two quarters by rebuilding the lifecycle program." The verb is concrete, the result is up front, and the number is impossible to miss in a fast scan.
A few things make this work in practice:
- Lead each bullet with an outcome and a verb, not with "Responsible for" or "Tasked with."
- Put a number in roughly half your bullets. Percentages, dollars, headcount, time saved. Even rough figures beat none.
- Keep bullets to one or two lines. A four-line bullet is a paragraph, and paragraphs do not get scanned, they get skipped.
- Cut the bullets that only describe routine duties. If it would be true of anyone with the title, it is not earning its space.
Clean layout is not decoration, it is legibility
The recruiter's scan depends on visual hierarchy, so a cluttered layout actively works against you. You do not need a designer. You need restraint. One or two fonts. Generous white space. Consistent spacing between roles. A clear distinction between a job title and a bullet point. Bold the things you want caught in the skim, which means titles, companies, and the occasional standout result, and then stop bolding so the emphasis still means something.
Two columns can work, but only if the main column reads cleanly on its own, because that is where the eye goes first. Skip the skills-rated-with-five-dots graphics. They look modern and tell a recruiter nothing, since nobody rates their own Python a confident three out of five and means it.
One page is being read by two readers
There is a tension worth naming. You are not writing for one reader, you are writing for two. The recruiter scans for signals and human judgment. The applicant tracking system parses for keywords and structure. The two do not always want the same thing, and chasing one can wreck the other. Stuff in keywords for the machine and your top third turns into mush for the human. Design a gorgeous two-column layout for the human and a weak parser may scramble it into nonsense before a recruiter ever sees it.
The resolution is less dramatic than it sounds. Use a clean, standard structure that a parser can read, use the real language of the job description where it is genuinely true of you, and keep the top third sharp for the person. Most resumes can satisfy both readers at once. The ones that fail usually optimized hard for one and forgot the other existed.
This is part of why we built Portfolio, our tool at portfolio.wrxstack.com that turns a resume into a professional website. It ships with resume layouts designed around the scan pattern and gives you live ATS scoring as you write, so you can see how both readers will handle your document before you ever send it. The point is not the tooling, though. The point is that you can see the scan now, so you should write for it.
Pull up your own resume and give it the six-second test. Look only at the top third. Can you find your name, your current title, your dates, and one real result without reading a full sentence? If yes, you are writing with the recruiter instead of against them. If not, you know exactly where to start.