The Resume Standard, and What a Good One Has to Contain

This is a grading standard for a resume, not a writing tutorial. The job is to define pass/fail criteria precise enough that two people checking the same resume reach the same verdict, then run your own document through them. It is for anyone writing or rewriting a resume who is tired of contradictory advice and wants a rubric they can defend, adopt as team policy, and re-apply per application.

A standard has one test that separates it from a tip list: reproducibility. If two reviewers can look at the same bullet and disagree on whether it is "strong," that criterion is an opinion, not a standard. Everything below is built to survive that test, and the last section tells you exactly where the common rules lie so you do not grade a good resume as bad.

What a resume standard actually grades

A resume standard grades objective properties, not taste. The reason so much resume advice conflicts is that it mixes measurable requirements with preferences, then states both with equal confidence.

Sort every rule you have ever heard into two piles. The first pile is objective: a parser can read the file, the top bullets carry numbers, there are zero spelling errors, the target title appears near the top. Two graders will agree on all of these. The second pile is preference: page count, whether to include a summary, font choice within the safe set, photo or no photo. These vary by market and role, and a standard should either bind them to a checkable condition or leave them to the candidate.

The dossier's failure modes are almost all cases of a preference being enforced as if it were objective. That is the trap. Build the standard from the first pile, and treat the second pile as documented judgement calls.

Why the first pass is short, and what that forces

The first pass is short and shallow, which means placement beats volume. Where evidence sits on the page matters more than how much of it there is.

The most-cited number is 7.4 seconds, from a 2018 Ladders eye-tracking study of 14 hiring professionals. Take that figure with its caveats: the sample was tiny and the study is old, and broader estimates put a first review anywhere between 5 and 30 seconds. The exact number does not matter for the standard. What matters is the mechanism it points to. Reviewers scan down the left side of the page and read only the first few words of each bullet. So the highest-leverage edit is not adding a result, it is moving the result to the front, because the reader may never reach the end of the line.

This is why front-loading is a rule and not a tip. A quantified result buried at the end of a bullet is, for scanning purposes, invisible.

The core criteria: what every resume must contain

Every resume must clear the same objective floor before any preference debate is worth having. These are the pass/fail lines, and each one is phrased so two graders will agree.

• Parseable structure. Single column, standard headings, contact block in the body. A parser extracts name, title, dates, and skills without ambiguity. It lies when a resume looks clean to a human but was built in a multi-column template that scrambles when the machine reads it.
• Target mirror. The posting's title and key skills appear verbatim near the top. It proves the resume was tailored. It lies when someone pastes keywords into a hidden white-text block, which modern parsers and humans both catch.
• Front-loaded quantified results. The top two or three bullets in each role open with a number. It proves impact over activity. It lies when the numbers are vague ("many," "significant") or when every line has a weak metric and the strong ones are buried.
• Reverse-chronological order. Most recent role first, dates on every role. It proves recency and continuity, and it is the ATS-safe default.
• Zero spelling and grammar errors. No exceptions. It is the single most common auto-rejection trigger.
• No unsupported numbers. Every figure is one the candidate can explain. It proves the achievements are real. It lies when a bullet reads impressively but the basis collapses under one interview question.

Reverse-chronological with standard headings is not stylistic. Over 90% of Fortune 500 companies use an applicant tracking system, and named platforms in wide use include Greenhouse, Workday, Oracle Taleo, Jobvite, BambooHR, and iCIMS. The parser is your first grader. A standard two humans apply identically has to first survive a machine that reads only plain structure, and the good news is that those two constraints call for the same fix, not competing ones.

Tailoring each resume to each posting by hand is the part that quietly eats hours. Pulling the exact title and skill language from a job description, matching it to your own history, and rewriting the top of the document per application is what Refolk automates: it drafts the resume from your own record and tailors it to every posting you apply to, then scores how well you actually fit.

Front-loading the number is a higher-leverage edit than adding one, because the reader may never reach the end of the line.

The rejection triggers to grade against

Some criteria are best graded as absences: things that must not be present. These are the documented deal-breakers, and they fail a resume outright regardless of how strong the rest is.

Read this as a checklist of veto conditions. Typos dominate: 77% of employers screen out a resume with typos or bad grammar, and 58% of resumes contain such an error, which is why proofreading is a named step and not an afterthought. The generic-resume and missing-results triggers map directly back to the target mirror and front-loaded-results criteria above, which is a useful cross-check: if you have graded those two as pass, you have already cleared two of the four vetoes.

The email one is cheap to fix and easy to forget. Use a plain name-based address, not a novelty handle from a decade ago.

The length and format debate, resolved by condition

Length is not a rule, it is a conditional. Grade the content, and the page count answers itself.

The one-page rule is contested by evidence. In the ResumeGo simulation of 482 recruiters reviewing 7,712 resumes, two-page versions were preferred at higher rates the more senior the role.

Now hold that against the counter-finding: TalentWorks, across 6,000 applications in 66 industries, found resumes over 600 words were 43% less likely to result in hiring. Both are true and they are not in conflict. ResumeGo measured what recruiters chose in a simulation, a preference signal. TalentWorks measured hiring outcomes. Reviewers linger on longer resumes but hire tighter ones.

So the standard does not grade page count. It grades this: does every line, including everything on a second page, carry a dated, quantified, relevant result? If yes, length is fine. If a second page exists to reach two pages, cut it.

Format is the other half. The ATS-safe format is single-column, with a web-safe font (Arial, Calibri, Garamond, Georgia, or Times New Roman), body text at 10 to 12pt and headings at 14 to 16pt, and no more than two font sizes. Avoid tables, columns, text boxes, graphics, and design-tool exports, because the parser cannot read them reliably. On file type, sources genuinely disagree: some career centers still advise .doc or .txt as the safest bet, while newer guidance accepts PDF because parsers have improved. When in doubt, follow the posting's stated preference, and if none is stated, a well-structured PDF is a reasonable default.

How crowded your title is, and why differentiation is market-specific

The differentiation bar is set by how many other people carry your exact title, and that number changes by market. Generic bullets vanish faster in a bigger pool, so the same resume needs sharper evidence in a crowded market than in a thin one.

In Refolk's index of professional profiles, the scale of that gap is concrete.

The US pool for that one title is roughly 8 times the UK pool. That ratio is a proxy for how crowded a keyword is per market, and it explains something the raw advice glosses over: quantified lines matter more in the larger pool, because there are simply more near-identical resumes for a duty-based bullet to disappear into. The same guidance ("add numbers") carries different weight depending on where you are competing.

This is where quantified achievements stop being generic advice and become the mechanism. Quantified resumes draw 2.5x more interview invitations than duty-based ones. The number converts a claim into evidence, which is what persuades both the matching engine and the human reviewer, and in a 349,752-deep pool, evidence is the only thing that separates you.

Before you finalize your bullets, it is worth seeing how people who cleared the bar you are aiming at actually phrased theirs. Refolk lets you search real profiles to benchmark language and quantified claims against your live competition.

The procedure: from master record to a graded resume

Run this once to build the resume, then re-run steps two through seven per application. The full pass is a few hours the first time and 20 to 40 minutes per tailored version after that.

The last step is what makes this a standard rather than a checklist. If your two graders disagree on a line, you have found a subjective criterion. Fix the criterion, not the resume.

Here is a rubric you can hand to both graders so they are scoring the same thing.

[ ] Parser can extract name, title, dates, and skills with no ambiguity (single column, no tables/text boxes)
[ ] Target posting's title and key skills appear verbatim in the top third
[ ] Most recent role is first; every role has start and end dates
[ ] Top 2-3 bullets in each role open with a number
[ ] No role has more than 3 lead metrics (strongest figures not diluted)
[ ] Every number is one the candidate can explain the basis for
[ ] Zero spelling and grammar errors
[ ] Contact block is in the body; email is name-based and professional
[ ] Web-safe font; body 10-12pt, headings 14-16pt; no more than two sizes
[ ] Every second-page line (if any) carries a dated, quantified result
Verdict: PASS only if all lines are P for both readers.

How this goes wrong: failure modes and false positives

The most valuable part of a standard is knowing where its own rules lie. Each of these is a case where applying a rule mechanically grades a good resume as bad, or a bad one as good.

• Treating 7.4 seconds as fact. It is an n=14 study from 2018; other work reports 5 to 30 seconds or minutes on second reads. The false positive is building a rule on a hard "7 seconds." Check: cite the sample size and date every time you invoke it, and grade the mechanism (front-loading), not the number.
• "Two pages always wins." The ResumeGo preference is a simulation choice, not a callback guarantee, and over 600 words correlates with 43% lower hiring odds. The false positive is padding a thin one-pager to two pages. Check: does every second-page line carry a dated, quantified result? If not, cut it.
• Quantifying every line. Quantifying literally every bullet dilutes your strongest figures, so ten weak metrics can bury two strong ones. Check: no more than two or three lead metrics per role.
• Invented numbers. A clean-looking bullet with a fabricated figure collapses in the interview. Check: can the candidate explain the basis for every number? If not, it fails, however good it looks.
• ATS panic. Not every employer uses one, and modern parsers read PDFs; over-stripping produces an ugly document a human then rejects. Check: is the resume both parseable and readable by a person? Both, not one.
• Typo screening theatre. The fewest resume errors occur among the unemployed, because more people reviewed them, so rejecting on one typo can screen out experienced, employed people. Check: separate the objective error from the inference about the person.
• The photo and design trap. Some European guidance recommends a photo; US and ATS guidance warns it breaks parsing, and some reviewers reject for it. Check: match the convention to the target market, not to a universal rule.
• Non-reproducible grading. If two reviewers disagree on a "strong bullet," the criterion is subjective. Check: rewrite any line where two graders split, until the standard produces the same verdict twice.

Verify before you call it done

Run this final check before submitting. It is the same rubric the two graders use, condensed to what you can verify yourself in one pass.

Keeping the standard current

A resume standard is not a one-time pass, because the pool you compete in and the postings you target both move. Re-grade whenever either changes.

Re-run the tailoring steps for every application, since the target mirror is posting-specific by definition. Re-check the crowding of your title when you switch markets: the same keyword that is manageable in a smaller pool can be near-invisible in a larger one, as the 8x US-to-UK gap shows. And re-open the failure-modes section whenever a piece of advice tempts you to enforce a preference as a rule; that is the section that keeps the standard honest.

The evidence base here has known limits, and a good standard states them. The scan-time figure rests on a tiny old sample. The two-page finding is a preference measurement, not an outcome. The vendor-sourced interview-lift figure should be read as directional. What holds across all of them is the shape of the method: build objective criteria, grade them with two readers, cut anything the readers cannot agree on, and re-run per posting. That shape survives whatever the specific numbers turn out to be.