Most advice about resumes is written from the candidate's side of the desk. It tells you what to put on the page. Far less is written from the other side — what actually happens when a recruiter picks your resume up, what they're looking for, and what goes through their mind in those crucial few seconds.
Understanding that perspective changes how you think about the whole document. So let's cross the desk.
The ten-second scan is real
The most-cited research on this comes from Ladders' eye-tracking studies, which clocked the initial resume scan at about six seconds in 2012 and 7.4 seconds in 2018. The exact figure is debated — it came from a small sample and lab conditions, and real-world times vary with role and volume — but the underlying truth holds across every study: the first pass is fast. Often under ten seconds.
This is not because recruiters are lazy or careless. It's because volume makes it necessary. When you're facing as many as 250 applications for one role, you cannot read each one deeply. You triage. The first pass isn't "is this person good?" — it's "is this an obvious no, or worth a closer look?" You're sorting into two piles as quickly as you can, and most resumes land in the "no" pile in seconds.
What survives the first pass gets a real read. But to survive it, your resume has to communicate the essentials almost instantly: roughly who you are, roughly what you've done, and whether you're plausibly a fit for this specific role. If a recruiter can't extract that in a few seconds, you're filtered — not because you're unqualified, but because you were illegible at speed.
What they're actually looking for
In that fast first pass, recruiters are scanning for a small number of signals:
Relevance to this role. Not your whole history — the parts that match what they're hiring for. A recruiter for a marketing role is hunting for marketing signal and skimming past the rest. This is why the same resume performs differently for different jobs, and why generic resumes underperform: they force the recruiter to do the work of finding the relevant parts.
Legitimacy signals. Recognizable companies, reasonable progression, relevant education or credentials — quick proxies for "this person is plausibly real and qualified." Fair or not, these shortcuts do a lot of work in the first pass.
Red flags. Things that prompt a "wait, what's going on here" — unexplained gaps, very short stints, a pattern that doesn't add up. Crucially, a red flag doesn't mean the recruiter knows something's wrong. It means they have a question — and in a fast triage, an unanswered question often defaults to "no," because there's no time to investigate and plenty of other resumes to consider.
That last point is the most important thing candidates don't understand, so let's sit with it.
The questions they never get to ask
When a recruiter reads your resume, they generate questions. Constantly. "Why did they leave here after seven months?" "Is this gap a problem?" "They list this skill, but did they really use it, or just touch it once?" "This title is vague — what did they actually do?" "Interesting project — I wonder how much of it was them."
These questions are the actual substance of resume screening. They're the recruiter's mind doing exactly what it should: probing, testing, trying to figure out if you're worth a closer look. In a perfect world, they'd ask you and you'd answer, and the good candidates would be sorted from the weak ones based on real information.
But they can't ask. You're not there. Your resume can't respond. So the recruiter is left to answer their own questions — with assumptions. And under time pressure, with a stack of other candidates waiting, those assumptions tend toward the conservative. The unexplained gap is assumed to be a problem. The short stint is assumed to be a bad sign. The vague title is assumed to be padding. Not because any of that is true, but because "no" is the safe default when a question can't be answered and there are 199 other options.
You lose candidates this way constantly — not to bad information, but to absent information. To questions that were raised and never answered, resolved against you simply because there was no way to resolve them any other way.
What recruiters wish candidates knew
If you could sit a hundred recruiters down, a few things would come up again and again:
Make relevance obvious. Don't make them hunt for why you fit this role. Put it up front, in their language, unmissable in a ten-second scan.
Don't create unanswered questions. Every gap, every short stint, every ambiguous title is a question you're forcing the recruiter to answer without you. Where you can, preempt them — a brief line of context defuses a question before it becomes a silent "no."
Specifics survive; generics don't. Vague claims get skimmed past. Concrete, specific accomplishments are what catch the eye and stick in memory.
The resume is the beginning of a conversation they mostly never get to have. This is the one recruiters feel most and candidates understand least. The resume raises questions the recruiter would love to ask — and the whole screening process is shaped by the fact that they usually can't.
The gap between screening and meeting
Here's the thing the recruiter's perspective reveals: screening and meeting are two completely different activities, and almost all the useful information lives in the second one.
Screening is fast, shallow, and defensive — a rapid sort based on incomplete data and conservative assumptions. Meeting is where the real evaluation happens: where questions get asked and answered, where context fills in, where a candidate who looked ambiguous on paper turns out to be exactly right, or a candidate who looked perfect turns out not to be. The whole point of screening is just to decide who gets to the meeting.
Which raises an obvious question: what if more of the meeting could happen earlier? What if the questions a recruiter forms in that ten-second scan could actually be answered — right then, by the candidate's own resume, instead of resolved against them by assumption? What if screening didn't have to be a defensive sort based on absent information, because the information was no longer absent?
That's the gap worth closing. Recruiters don't want to reject good candidates over unanswered questions; they're forced to by a process where the answers aren't available at the moment they're needed. Give them a resume that can actually answer, and screening starts to look less like a defensive triage and more like the early stage of a real conversation — which is what everyone, on both sides of the desk, actually wants it to be.