The Resume Pass/Fail Standard, Section by Section

This guide is a definition of done for a working professional's resume. It is for anyone who is about to hit submit and wants to know whether the document is good enough, and for the friend or reviewer they ask to check it. Instead of scattered tips, it gives you a section-by-section rubric with numeric thresholds and pass/fail line tests, so a candidate and a reviewer reach the same verdict and can point to exactly which lines fail and why.

The public alternatives split into two useless piles. Professional advice is scattered listicles - sixteen tips, the six-second scan - that no two people apply the same way. The only real rubrics online are student career-services PDFs that grade on vague aesthetics for entry-level students. This is the missing thing in between: a grading standard you can adopt as a team policy.

Why a rubric beats a tip list

A rubric produces the same verdict from two reviewers; a tip list produces two opinions. That is the whole point. A resume checklist before applying is only useful if a second person applying it to the same document lands where you did. Tips like "quantify your achievements" and "keep it clean" fail this test because two reviewers will disagree on what counts as quantified and what counts as clean.

The fix is to convert each piece of advice into a test with a written pass condition. "Quantify your achievements" becomes "every bullet contains an outcome, a measurement, and a method, or it is marked as a duty statement to rewrite." Now two people grading the same bullet reach the same mark. Everything below is written this way: a criterion, what it proves, and what it looks like when it lies.

The 7.4 seconds is a rejection clock, not a reading clock. Because 80 percent of it lands on name, current title, previous titles, employment dates, and education, misplacing your title or dates fails the resume regardless of how good the bullets are. That single fact reorders how you should grade: identity and structure first, prose second.

The seven-section standard at a glance

Grade in the fixed order below. Each section has a pass condition you can check without judgment calls, and a fail is a fail regardless of how strong the rest of the document is. This is the spine of the whole standard.

Two of these sections carry most of the rejection risk and deserve extra weight: file parse, because the damage is invisible on screen, and the bullet test, because it is where inflated claims hide. The rest of this guide unpacks each row.

Parse-test: the file must survive extraction

A passing file is a single-column, selectable-text .docx or PDF that parses cleanly on upload. Format failure is invisible to the author, which is why it survives revision after revision. A two-column template renders perfectly on screen yet merges titles and skills into nonsense during text extraction, so the damage only shows in the parsed output.

The load-bearing test is select-all. Press Ctrl+A. If any text - your name in the header, a skill in a sidebar, a value in a table cell - does not highlight along with the body, an applicant tracking system likely will not see it either. Documented offenders are tables, multi-column layouts, text boxes, headers and footers, graphics, and image-based PDFs. Tables and columns disrupt the order of extraction so that side-by-side content is skipped or jumbled; text boxes are treated as floating objects and may be hidden; header and footer text is frequently ignored.

Keep the mechanical settings inside the safe band: a standard font such as Arial, Calibri, or Times New Roman at 10 to 12 point, margins of 0.5 to 1 inch, and no tables, text boxes, or graphics. A vendor estimate puts more than 40 percent of resumes at one or more parsing-error elements, though the methodology behind that figure is not established, so treat it as a reason to run the test rather than a precise rate.

Top third: six fields, in reading order

The top third of the first page must carry name, current title and company, previous title and company, employment dates, and education, all readable and in reading order. This is where the 7.4-second screen is spent. In the eye-tracking work, recruiters look at your current title and company, then your previous one, then move right to check the dates for steady progression, then flip to the bottom for education.

Because 80 percent of the review lands on these six fields, they are the highest-leverage real estate on the page. A brilliant bullet in the experience section does nothing if the reviewer never gets past a missing title or a set of dates that reads as a gap. Grade this section as a hard gate: all six present, in order, above the first-third line, or fail.

Section order and length: the fixed skeleton

A reverse-chronological resume has six core sections in a fixed spine: contact details at the top, then a summary, then experience, education, skills, and certifications. The first three are not negotiable. Parsers read top to bottom expecting contact, then summary, then experience, mapping titles to dates to companies. Break that pattern and the parser produces a mangled record. Score a missing or misordered core section - among the first three especially - as a fail.

After the first three you have some flexibility based on the role. The one documented exception to order: for a current student, education outranks experience, so move education above experience in that single case. Everyone else keeps experience above education.

Length by experience

Length is a consensus, not a regulation: roughly one page for every ten years of experience. The bands below are the pass zones. Word count is the more predictive of the two measures - the 475 to 600 word range roughly doubled interview rate in a 6,000-application analysis, which means a one-page resume of 300 dense words can underperform a fuller two-page document.

Nearly half of job seekers now go past one page - 49 percent submit something longer, with 21 percent at a full two pages - so a second page is not itself a fault. The fault is the half-empty second page. If page two is less than two-thirds full, cut back to one page or fill it honestly; 1.5 pages is the worst length to land on.

The bullet test: outcome, measurement, method

A passing experience bullet contains three components: the outcome, the measurement, and the method. This is the XYZ formula from Laszlo Bock, the former Google Senior Vice President of People Operations, in his book "Work Rules!": accomplished X as measured by Y by doing Z. X is the accomplishment, the outcome rather than the task. Y is the measurement - a percentage, a dollar amount, time saved, or a volume. Z is the action - the specific method, tool, or decision.

A bullet fails when it is a duty statement. Most resumes read like job descriptions because people list what they were responsible for rather than what they accomplished. "Responsible for managing the deployment pipeline" is a duty; "Cut deployment failures 40 percent by rewriting the release checks in CI" carries all three components. Word order is flexible - vary the sentence structure - but all three parts must be present. Aim for three to five strong XYZ statements per role.

[Outcome: what changed, not what you were assigned]
  as measured by
[Measurement: a percent, dollar figure, time saved, or volume]
  by
[Method: the specific tool, decision, or approach you used]

Example:
Reduced customer churn 18 percent over two quarters
  by rebuilding the onboarding email sequence around
  activation milestones instead of calendar days.

Z is the anti-fraud component and the one a reviewer should weight most. The method demonstrates whether you can replicate the result in a new context, so a bullet with an outcome and a number but no method is exactly where inflated claims hide. When you grade, ask of each bullet: can I name the specific thing this person did? If not, mark it for rewrite even if the number is impressive.

A bullet with a number and no method is where the exaggeration lives; make the method mandatory.

Quantification: grade per bullet, not by quota

Every role should carry at least one quantified bullet, but there is no defensible global ratio, so grade per bullet and flag only roles with zero numbers. Published figures conflict. One guide claims at least 50 to 60 percent of bullets should be quantified; another asserts roughly 80 percent. Neither traces to a controlled study, so treat any fixed percentage as not established publicly.

What is checkable sits underneath those claims. A survey of hiring managers indicated that 34 percent pass over resumes with few or no measurable results. In one resume analysis, only 26 percent included at least five instances of measurable results. That scarcity is the opening: the single most fixable edge is quantification, not writing quality. Adding one honest metric per role moves a candidate past most of the field.

The reason the bar has to be set locally, not globally, is that pool size is wildly uneven. In Refolk's index, the counts differ by role and geography by more than an order of magnitude.

Counts come from Refolk's index of professional profiles; the ratios are derived by division. The same resume competes against roughly 16 times as many people for a United States software role as for a German one, and about 12 times as many Software Engineers as Data Scientists in the United States. A deeper pool needs a sharper quantified spine. If you want to see how the top of your pool actually writes, Refolk can pull real profiles and show you which quantified claims recur, so you calibrate against the field rather than against a generic tip.

The grading procedure

Run the standard in this order, with a second reviewer for the sections marked. The whole pass takes about 40 minutes and produces a line-by-line verdict, not a vibe. Grade identity and structure before prose, because a fail there ends the review regardless of bullet quality.

Reconciliation is what makes this a standard rather than a review. Two reviewers grade independently, then compare. The only place the sources disagree on order is the student exception - education above experience for current students - so resolve that case explicitly and move on. If the two verdicts still differ after that, the criterion was not sharp enough; rewrite the pass condition until both graders land in the same place.

How this goes wrong: failure modes and false positives

Most failures are false positives - the resume looks correct and still fails a test. These are the cases where two reviewers most often disagree, so each one below comes with the check that settles it.

Two of these deserve extra words. The fake XYZ hides behind a real number: "Attended 40 meetings" has a measurement but no outcome. Strip the number and ask whether anything of value remains; if not, it is a duty statement wearing a metric. The inflated metric is worse, because it survives the resume and collapses in the interview - experienced interviewers probe your numbers, and getting caught in an exaggeration destroys credibility instantly. The defense is the method test: if you cannot name how the number was measured, do not put it on the page.

Two structural traps reject the file outright. A functional, skill-grouped layout that files jobs under skill categories produces a mangled parsed record, and some systems reject it. A creative heading such as "My Journey" confuses a parser that is scanning for "Work Experience," "Education," and "Skills." Both look like reasonable design choices and both fail. Confirm reverse-chronological order with dates mapped to companies, and use the standard headings verbatim.

The last failure mode is misusing this very guide. Do not treat any quantification percentage as gospel and pad weak bullets with numbers to hit a quota. There is no verified public threshold. Grade per bullet, keep the method mandatory, and flag only the roles that carry no quantified bullet at all.

The pre-send checklist

Run this immediately before you submit. If every item is checked and a second reviewer agrees line by line, the resume is good enough to send. If any item fails, you can point to the exact line and the reason.

Keeping the standard current

Most of this standard is evergreen because it rests on how parsers read files and how the eye moves, neither of which changes with the calendar. The parts that can drift are the numbers, so re-check them at the mechanism rather than the value. The word-count band and page conventions come from consensus and one large analysis; if you see a newer application study, compare its interview-rate band to the 475 to 600 word figure before overwriting it. The parsing offenders can change as tools improve, so the durable move is to keep running the select-all test on whatever system you are actually submitting to, rather than trusting a list of banned elements.

The one number that is truly yours to watch is pool size. The volumes competing for a role shift as markets grow, and the same resume that passes comfortably in a scarce market can sit mid-pack in a deep one. Re-check the size of your specific pool before you decide how sharp your quantified spine needs to be, and tailor each application to the posting in front of you rather than sending one document everywhere. That per-posting tailoring, the fit scoring, and the first-draft rewrite are exactly the friction Refolk removes once your base resume passes this standard.