The Sell-One-Role Resume Standard, and What Fails It

This is a definition of done for a resume: the pass/fail criteria you apply to decide whether it is finished and strong enough to send. It is for anyone rewriting a resume, profile, or portfolio who wants to grade their own draft the way a second reviewer would, and it is written so two people grading the same resume reach the same verdict and can point to the exact criterion each failure breaks.

Free graders return a black-box number weighted mostly on machine-readability, with rubrics that differ tool to tool. This standard replaces that with a human-gradeable spine focused on one thing: does the resume make one clear claim for one target role, backed by evidence. Everything below is either a binary test or the procedure for applying it.

What is the sell-one-role standard actually grading?

The standard grades one thing: whether the resume argues for a single named role and backs that argument with evidence a second reviewer can verify. It does not grade taste, visual design, or how many keywords match. It grades positioning, and it treats machine-readability as a knockout gate rather than the score itself.

Career-services and academic rubrics converge on a small set of axes. A representative career-center rubric assesses resumes on clarity, skills alignment, ATS compatibility, and demonstrated impact rather than visual preference alone. Academic rubrics add completeness and mechanics. The axes everyone agrees on are clarity, quantified impact, relevance and positioning, formatting and parsing, and completeness. Where rubrics diverge is in weighting and in what "pass" means: some collapse quality into ATS parsing, while a hiring-side rubric separates binary must-haves, such as a required license or work authorization, from scored quality signals, such as depth of experience or evidence of impact.

This standard borrows that separation and makes it strict. Knockouts are binary and non-negotiable. Positioning is the spine. Formatting is a gate you must pass to be read, not a source of points once you clear it. The reason to weight it this way is where attention goes on the first pass.

The competing pool is also large enough that a nonstandard title costs you the match. In Refolk's index of professional profiles, there are 348,536 people in the United States holding the title "Software Engineer," and in a 25-profile sample, 22 of them used that exact title string. A candidate who invents a clever nonstandard title forfeits recognition on the six data points recruiters actually read.

Why positioning outranks everything on the first pass

Positioning outranks detail because a first-pass reader spends their attention on six fixed slots, not on your prose. If the target-role claim does not live in those slots, the argument is invisible when it matters most.

The Ladders eye-tracking studies are the primary source. The 2012 study found recruiters spent about 6 seconds per resume; the 2018 update showed 7.4 seconds, with core scanning patterns holding steady. In that window, 80% of initial review time went to six pieces of information: name, current title and company, previous title and company, employment dates for both, and education, scanned in an F-pattern. That is the mechanism behind the "one target role" criterion. Explanatory prose below the fold is nearly invisible on pass one.

This figure is contested, and the standard treats it as such. Some recruiters push back on the 7.4-second number, arguing real screening times vary by role complexity, application volume, and screening stage. So the standard uses the scan test as one gate, not the whole grade: a resume must pass the seven-second test and survive a full-content read. Grading purely for a seven-second scan can reward a thin resume, which is a failure mode covered below.

Title language is more standardized for some roles than others, which changes how explicit your role claim must be. In Refolk's index, in-sample title convergence drops from 88% for Software Engineer to 60% for Data Scientist. A Data Scientist applicant faces more title ambiguity and must state the target role explicitly rather than rely on the title being recognized.

The knockout criteria: binary, non-negotiable

Knockouts are the pass/fail tests that a resume must clear to be graded at all. Each is binary, each has observable evidence, and each fails loudly when broken. If any knockout fails, the resume fails, and you name the knockout.

The reason to state these as binary is calibration. The documented method for turning subjective judgement into a shared verdict is to separate binary knockouts from scored signals, define observable signals for each, and fix pass rules before reviewing. Keywords alone are weak evidence; you look for scope, level, recency, outcomes, and comparable work. Below are the knockouts, each with what it proves and what it looks like when it lies.

The number test is the sharpest of these because it removes reviewer taste. Replacing "does this have impact?" with "does it contain a before-and-after or a measurable outcome?" converts a judgement two graders would split on into one they score identically. A bullet without a number is a claim without evidence.

The completeness and format baseline for a US resume

The completeness baseline is five standard sections in reverse-chronological order, with the strongest credential first. The format baseline is a single-column layout with standard headings, a system font, and a text-selectable PDF. Meeting both is a knockout gate, not a source of extra credit.

The standard US resume is reverse-chronological, listing the most recent positions first. It should always contain a contact header with name, phone, and email at the top; a professional summary or objective; and experience, education, and skills. That is five sections. Lead with your strongest credential: for most professionals that is experience; for students and bootcamp graduates it might be education or projects. US convention excludes photo, references, and personal data.

On format, single-column wins on parsing decisively. A single-column, reverse-chronological or hybrid layout with standard headings, a system font, and a text-selectable PDF parses at 95 to 99 percent in tests across Workday, Greenhouse, Lever, Taleo, and iCIMS. Two-column and functional layouts score far lower, because a linear parser reads a two-column layout as scrambled word salad. The PDF myth is outdated: every major modern ATS parses clean, text-based PDFs reliably. What breaks parsing is scanned images, tables, multi-column layouts, and content buried in headers, not the PDF format itself.

Page count is the criterion people most often over-worry. The norm is one page if under ten years of experience and two pages if more. Recruiters and applicant tracking systems do not auto-reject two-page resumes unless the posting explicitly requires one page. The condition is that every line earns its place; a two-page resume that earns every line is an asset, but one padded with filler is worse than a tight one-pager.

Turning a scattered history into one legible top-third claim is exactly where Refolk removes friction: it writes the resume from your own history and tailors it to a single posting, so the target role lands in the six slots a recruiter actually reads.

The grading procedure, start to verdict

Grade in a fixed order so the verdict is reproducible: name the role, set the pass rules, run the scan test, grade bullets, check completeness, test the parse, check length, then calibrate with a second reviewer. Following the order matters because some tests only make sense once an earlier one has passed.

Sources disagree on the order of the scan test and the parse test. Some fix parsing first, because an unparsed resume never reaches a human. The eye-tracking sources put the human scan first. This procedure runs the human scan before the parse because the scan is faster to run and catches the more common failure, but if you are grading at volume and know the pipeline is heavily automated, swap them.

The pass rule is where calibration lives. Set it before opening resumes, for example a total score of 3.5 or higher and at least a 3 on every critical criterion. At the bullet level, the two binary tests are: "Would this bullet appear in the job description for my role?" and "Does it contain a before-and-after or a measurable outcome?" Rubric benchmarks such as Basic, Proficient, and Strong reduce grader variance because all reviewers evaluate against the same anchors.

Target role: __________
Knockouts (all must pass):
  [ ] Top-third names the target role, legible in 7 seconds
  [ ] Every experience bullet: strong verb + measurable outcome
  [ ] PDF copies out as clean, in-order text
  [ ] Five standard sections, reverse-chronological
Pass bar: verdict = PASS only if all knockouts pass AND page 1 is self-sufficient.
Failure log: criterion violated -> exact line -> fix owed

How this standard produces false passes and false fails

The most dangerous failures are the ones that pass a naive grader and fail the real job. A resume can clear a completeness rubric and still fail the sell-one-role standard, and a bullet can look quantified while proving nothing. Grade for these explicitly.

The table below is the checklist for false verdicts. Each row names the trap, the wrong verdict it produces, and the test that catches it.

Strong-verb theatre deserves a note. "Spearheaded" on routine process work reads as inflated, because verbs like "processed," "verified," or "maintained" often sound more accurate, and hiring teams can usually tell when wording does not match likely responsibilities. Harvard's guidance flags the opposite problem too: bullets that begin with "Responsible for," "Helped with," "Assisted in," or "Worked on" signal passive participation, not ownership. The test is not "is the verb strong" but "does the verb match the scope."

The scan-time trap is the subtlest. Grading purely for a seven-second scan can reward a thin resume, and the 7.4-second figure is disputed and stage-dependent. Always run a full-content read alongside the scan test. A resume that passes the scan and collapses on a close read has not earned a pass.

A number that measures nothing is not evidence, it is decoration that passes a lazy grader.

Positioning against the size of your competing pool

How aggressively you scope the one-role claim depends on the market you are competing in. The larger and more standardized the pool, the more a nonstandard title costs you; the smaller the market, the more geography and scarcity shape the claim.

Two datasets from Refolk's index make the scale concrete. First, the size of the US pool by title, which is a proxy for competition:

Second, the same target role compared across countries, which changes how tightly you scope the claim:

A UK-targeted Product Manager resume competes in a market roughly 4.3 times smaller than the US one. Relative scarcity and geography change how the one-role claim is scoped: in a smaller market you can afford to be more specific about domain and level, because there are fewer near-identical competitors to blur against. In the vast Software Engineer pool, where title language is 88% convergent, matching the standard title string exactly is the price of being found at all.

Tailoring one resume to one posting for one role, and scoring how well it actually fits before you send it, is the friction Refolk removes: it drafts the tailored resume and cover letter from your history and scores the fit against the posting, so the sell-one-role claim is built in rather than bolted on.

The final checklist before you send

Run this checklist last, after the full procedure. It is the definition of done: if every item is checked, the resume passes; if any item fails, name the criterion and fix it before sending.

Keeping the standard current

The standard's spine - one role, evidence per bullet, clean parse - does not go stale, but two inputs do, so re-check them rather than trusting a fixed value. First, the seven-second scan figure is contested and stage-dependent; treat it as a threshold to test locally, not a law, and re-run your own scan test with a real second reader for each new role type you target. Second, ATS parsing behavior changes as vendors update, so verify the parse with the copy-paste test on the actual file you are about to send rather than assuming last quarter's result still holds.

To keep a resume current against a specific market, re-scope the one-role claim whenever you change target roles or geographies. The pool sizes and title-convergence rates above are the reason: a title that reads as standard in one market or role may not in another, and the six data points a recruiter reads are only as strong as the exactness of your title string.

To pressure-test your own positioning, look at how people who already hold your target role describe themselves.

The last discipline is the second reviewer. A standard only earns the word if two people applying it reach the same verdict. If your grade and a colleague's grade diverge, the fix is almost never a new opinion - it is a criterion that was not binary enough or a pass rule you set after you started reading. Tighten the test, re-grade, and the verdicts converge.