01 · Weight 15 Parse integrity Does the software that reads this file recover the name, contact details, section headings, employers, titles, and dates without losing any of them? | Extracted as plain text, every element survives: name, contact details, all section headings, every employer, title, and date range. Single column, no tables or text boxes, contact details in the body. | Everything material survives, with cosmetic loss only, such as an icon or a horizontal rule. Reading order stays correct. | One element is lost or scrambled: dates detach from employers, a heading merges into body text, or contact details sit in a header that does not extract. | A whole section is missing or unreadable after extraction, or the reading order interleaves two columns into nonsense. |
|---|
02 · Weight 35 Required criteria For every requirement the posting states as required, is there evidence on the resume, in language a reader searching for that requirement would find? | Every required criterion has evidence on the page, stated in language a reader searching for that requirement would find. | Every required criterion is met, but one or more are described in an internal project name, a former employer's jargon, or a synonym the posting does not use. | One required criterion has no evidence behind it. The rest are met, whether or not the wording matches. | Two or more required criteria have no evidence behind them. |
|---|
03 · Weight 15 Preferred qualifications Which preferred qualifications are met, and are the met ones visible rather than buried? | Most preferred qualifications that are genuinely met are stated, and they sit where a reader will see them rather than in the last line of the oldest role. | Several met preferences are stated, others are met but never mentioned. Nothing is claimed that is not held. | Preferences are largely unaddressed even where the underlying experience exists elsewhere on the resume. | Preferred qualifications are claimed without evidence, or contradicted by the experience section. |
|---|
04 · Weight 20 Evidence quality Does each claim carry a scope, an outcome, or a number, rather than asserting a responsibility? | Most bullets carry a scope, an outcome, or a number. Where a figure is genuinely unavailable, scope stands in: team size, system size, client count. | A mix. The strongest roles carry evidence, older or less relevant roles assert responsibilities. | Most bullets describe duties rather than results. The reader learns what the person was responsible for, not what changed. | Bullets are a list of tools and adjectives with no scope, outcome, or number anywhere. |
|---|
05 · Weight 15 Human readability In the first fifteen seconds, can a human reader tell what this person does, at what level, and why they fit this specific role? | Within fifteen seconds a reader can state the person's function, their level, and why they fit this posting. The top third does that work. | Function and level are clear; fit to this specific posting takes a second read to establish. | The reader has to reconstruct the story from the roles, because the top of the page is a generic summary that would suit any posting. | Function or level is ambiguous after a full read, or the document argues for a different role than the one being applied to. |
|---|