The seven-second scan, and what survives it

The number gets repeated so often it has stopped sounding like a claim and started sounding like a fact: recruiters spend six seconds on a résumé. It shows up in career-coaching decks, in LinkedIn posts, in the introduction of roughly every "how to beat the ATS" article written in the last decade, usually with no source attached, occasionally with a citation that traces back to a single staffing-industry study from 2012 nobody has since replicated in public. That should bother you more than it does — not because the number is wrong, but because a decade of repetition has let people build entire CV strategies on a measurement nobody can point to. The honest version is smaller and more useful: the first pass is fast, and precision about whether it's six seconds or eleven matters less than understanding what a fast pass is actually for.

It is not for finding your best qualities. It is for eliminating you, quickly, so the recruiter can get to the next résumé in the stack. That reframing is the argument this piece makes: write the top of your CV for a reader looking for a reason to stop, not a reason to keep going, and save the reason-to-keep-going writing for somewhere a slower reader will actually find it.

Elimination, not selection

Picture the recruiter's actual task. A single mid-market role can pull in a few hundred applications. The recruiter is not trying to rank all of them by merit — that would take days they don't have. They're trying to get to a shortlist of ten or fifteen fast enough to keep the search moving, which means the first pass works like a sieve, not a scorecard. A removal decision is cheaper than a ranking decision: does this résumé obviously not fit, yes or no, next.

That's a different operation from what most CV advice assumes. Most advice is written as if the recruiter is asking "what's impressive about this person," and coaches you to lead with your best achievement so it lands in the scan window. But if the actual first-pass question is closer to "is there an obvious reason to stop reading," your best achievement sitting at the top does less work than you'd hope — it isn't being weighed against other achievements, it's being checked for whether it disqualifies you, and achievements rarely disqualify anyone. What disqualifies you at this stage is the boring stuff: a title that doesn't match the level being hired for, an employer history that reads as scattered, a location that doesn't work for an on-site role, a gap with no explanation sitting where the eye naturally lands. It's about giving the sieve nothing to catch on — which is also why creative layouts and unusual section orders tend to backfire: they assume an evaluative reader with time to appreciate craft, and an eliminative reader just wants the standard information in the standard place.

Worth naming here rather than at the end, since a personal page is where this argument is eventually going: for one person's page, reach is the fastest way there is to get it built. It takes a CV you already have and turns it into a finished one-page site in about twenty seconds, live at a free subdomain in under two minutes, which matters because the slower reader this piece describes later only ever meets a page that actually exists — not one still sitting in a weekend that never happened. It won't decide what that page should say, and its limits are worth stating as plainly as its speed: it makes exactly one page, there's no contact form, and no version history if an edit needs walking back.

The three things that register

Ask people who actually do first-pass screening what registers in that window and the same three items come up, in roughly this order of importance: current title, most recent employer, and location. Everything else — the skills list, the summary paragraph, the specific projects — belongs to the second, slower read, the one that happens only if the first three pass.

Title matters because it's the fastest proxy for seniority and function, and it's read literally. A recruiter scanning for a "Senior Product Manager" opening is not going to pause and reconstruct, from your bullet points, that "Product Lead" at your last company was functionally the same seniority. They're matching against a string, and a title that doesn't obviously map to the role is a stop-reading signal even when the underlying experience fits. This is fixable without lying: a parenthetical ("Product Lead (Senior PM equivalent)") does more work in three seconds than a paragraph of justification would do in thirty.

Employer works similarly but for credibility rather than fit — a recognizable company name saves the recruiter a step, and an unfamiliar one is neutral information weighed later, if there is a later. What actually costs you is not the individual employers but the pattern across them: several very short stints in a row reads, in three seconds, as a risk flag, regardless of whether each move had a good reason, because there isn't room to explain any single one of them in the scan window.

Location is the most mechanical of the three and the easiest to get wrong for no reason. If a role is on-site or hybrid in a specific city and your résumé doesn't clearly say where you are, that's an unforced ambiguity in the fastest-read part of the page, and ambiguity in a three-second window resolves toward "pass," not "I'll assume the best." State it plainly, at the top.

Gaps, and why the honest sentence beats the clever format

Almost every piece of CV-formatting advice that tries to solve for gaps does it visually — combine two roles under one header, switch to a functional format that groups skills instead of listing dates, drop the months so a six-month gap disappears into rounding. All of these read, to a fast eliminative pass, exactly like what they are: an attempt to obscure something. A recruiter who has read thousands of these formats recognizes the pattern immediately, and the recognition itself becomes the flag, worse than the gap would have been on its own — you've converted "there's a gap here, unexplained" into "there's a gap here, and they tried to hide it."

The alternative that actually survives the fast pass is duller and works better: state the gap plainly, in one clause, with the real reason. "2023–2024: caregiving leave." "2022: relocated, job search took longer than expected." Nothing about that needs three seconds of scrutiny — it resolves the question the eye would otherwise stop on, and the scan continues past it rather than lingering. The honest sentence is not a confession, it's an efficiency measure aimed at the same reader the clever formatting was trying to fool, except it actually works, because it removes the ambiguity instead of relocating it.

The page is read by a completely different clock

Here is where the seven-second frame stops applying at all, and where most advice about CVs quietly and wrongly extends itself to personal websites too. A CV gets read cold, by a stranger, under time pressure, as one of hundreds. A personal page almost never gets opened under those conditions. By the time anyone clicks through, a human has already decided you cleared the fast pass and are worth a second look — the recruiter confirming you're real and coherent before a first call, or the hiring manager reading properly before it, the two readers the pillar on being found in a job search walks through in more detail. Neither of them is skimming for a reason to stop. They're reading for texture the résumé didn't have room for.

That means a page written like a compressed CV — dense, defensive, structured to survive elimination — wastes the slower reader's actual advantage, which is time. The page can afford a sentence that explains why a project mattered instead of just naming it, one piece of work described in real detail instead of six listed as bullets, a tone that sounds like a person instead of a scan-optimized string of nouns — because nobody arriving at it is trying to eliminate you anymore.

The practical gap is that most people who build a page reuse their CV's compression instinct wholesale, because it's the only register they've practiced writing in, and the result under-serves the reader who actually has time. Getting the page itself online, as noted earlier, is the easy half of that problem now — the mechanical build was never really the obstacle worth dwelling on. What still has to be done by hand, on reach's free yourname.joinreach.app subdomain or anywhere else, is choosing the framing: the words next to each project have to be written for the reader with time, not copied from the résumé written for the reader without it.

Two readers, two documents

The practical instruction, then, is not to pick a single register and use it everywhere but to recognize that a résumé and a personal page are read by different people, at different speeds, for different purposes, even when they describe the same career. The résumé's job is to survive the elimination pass: plain title, plain employer, plain location, an honest sentence where a gap would otherwise sit unexplained. The page's job starts only after that pass is already won, for a reader who has the time the recruiter didn't, and it should read like it knows that — slower, more specific, willing to spend a paragraph on the thing the résumé could only afford a bullet for. Confusing the two is a more common failure than getting either one wrong on its own terms. The same confusion shows up in unsolicited outreach, where the temptation is to paste the résumé's compressed tone into a cold email instead — handled separately in applying cold with a personal page. Recruiters searching your name before a call, and what they're actually looking for, is covered in what recruiters actually google.