Modern Niche World MNW

How Readback reads your resume — the method

This page is generated from Readback’s own engine, not written by hand — so what you read here is exactly what runs on your resume. If a rule changes, this page changes with it.

How we validate

Every rule has a hand-written “expected result” for a set of test resumes — our gold set. The engine is checked against all of them on every change: a rule only passes when it reads the right thing for the right reason, and a result is never loosened to manufacture a pass.

We are still validating against real files exported from Word and Google Docs. Until that is finished we are not publishing a headline accuracy figure — a number against our own test set would say less than this: here is exactly how we check, including the part we have not finished.

The readings

How well software reads your file. A machine-readability reading out of 100. A lower number means information could be lost or scrambled when hiring software reads your file.

  • Fit for this job — Arrives with a later phase, once a job posting is added.
  • How clearly it reads to a person — Arrives with a later phase.

These are separate readings. We never combine them into one score.

The machine-readability formula

The reading starts at 100. Each problem subtracts a penalty — a base amount for how much it hurts, multiplied by how confident we are:

SeverityBase penalty
Can block reading30
Weakens the reading10
Polish3
ConfidenceMultiplier
certain×1
likely×0.7
possible×0.4

The first time a rule fires it counts in full; the next three at a quarter each; after that, nothing. A file with no readable text scores 0. The score never goes below 0. (Formula version 1.0.0.)

The reading rules

Pack version 0.1.0. Each rule, what it checks, how serious it is, and the evidence behind it.

RS-1.1 — No real text to read (an image or a scan)

Can block reading Seen in our tests Reading standard RS-1.1

  • gold image-only.pdf; ResumeExtractBench scans (checked 2026-10-04)

Changelog: v1.0.0 (2026-10-04) first version

RS-1.3 — The file is password-protected

Can block reading Seen in our tests Reading standard RS-1.3

  • gold password.pdf (reader refuses with pdf-password) (checked 2026-10-04)

Changelog: v1.0.0 (2026-10-04) first version

RS-2.1 — A two-column layout many parsers scramble

Can block reading Seen in our tests Reading standard RS-2.1

  • gold two-column.pdf / sidebar fixtures (column detection) (checked 2026-10-04)

Changelog: v1.0.0 (2026-10-04) first version (re-dressing the layout column detection)

RS-2.2 — Content in a table

Weakens the reading Seen in our tests Reading standard RS-2.2

  • gold table.pdf / two-column (table detection) (checked 2026-10-04)

Changelog: v1.0.0 (2026-10-04) first version

RS-2.3 — Content in a text box, shape or frame

Weakens the reading Seen in our tests Reading standard RS-2.3

  • gold text-box.docx (text-box detection) (checked 2026-10-04)

Changelog: v1.0.0 (2026-10-04) first version

RS-2.4 — Contact details in a header or footer

Weakens the reading Seen in our tests Reading standard RS-2.4

  • gold header-contact.pdf / .docx (checked 2026-10-04)

Changelog: v1.0.0 (2026-10-04) first version (re-dressing the step-3 header/footer finding)

RS-2.5 — Content shown as an icon or graphic

Weakens the reading Seen in our tests Reading standard RS-2.5

  • gold icon fixtures (icon-font glyph detection) (checked 2026-10-04)

Changelog: v1.0.0 (2026-10-04) first version

RS-2.6 — Hidden text (white, tiny, off-page or marked hidden)

Weakens the reading Seen in our tests Reading standard RS-2.6

  • gold hidden-text.pdf / .docx (tiny/off-page/vanish detection) (checked 2026-10-04)

Changelog: v1.0.0 (2026-10-04) first version

RS-2.7 — Items fused with no visible separator

Weakens the reading Seen in our tests Reading standard RS-2.7

  • gold glue fixtures; planning test 23 Sep 2026 (checked 2026-10-04)

Changelog: v1.0.0 (2026-10-04) first version (re-dressing author glue)

RS-2.8 — An icon-font bullet

Polish Seen in our tests Reading standard RS-2.8

  • gold icon-bullets.pdf / .docx (icon-font bullet detection) (checked 2026-10-04)

Changelog: v1.0.0 (2026-10-04) first version

RS-3.3 — A letter-spaced heading

Weakens the reading Our best judgement Reading standard RS-3.3

Reasoned: a parser splits "E X P E R I E N C E" into single letters, losing the heading; no independent source, so assumption not community.

Changelog: v1.0.0 (2026-10-04) first version

RS-4.1 — The name is not clearly at the top

Weakens the reading Our best judgement Reading standard RS-4.1

We assume a parser looks for the name at the top of the body; the claim is widely repeated in résumé guidance but we have no independent source, so assumption not community.

Changelog: v1.0.0 (2026-10-04) first version

RS-4.2 — A phone number without a country code

Polish Our best judgement Reading standard RS-4.2

A phone without a leading +country is ambiguous abroad; reasoned, not independently tested, so assumption.

Changelog: v1.0.0 (2026-10-04) first version

RS-5.2 — More than one date format

Polish Our best judgement Reading standard RS-5.2

We assume mixed date formats make a parser's duration calc less reliable; widely advised but not independently tested, so assumption.

Changelog: v1.0.0 (2026-10-04) first version

The strict-system simulation

Beside the true reading, Readback simulates how a strict applicant tracking system would read the same file — what it might lose, scramble or misread. This is a simulation, always labelled as one, never a claim about a specific named product. There is one model, generic-strict-ats (version 1.0.0), built from the few behaviours that are actually documented.

  • runsOCR: false Documented by the vendor
  • columnReading: across-rows Reported by recruiters and testers
  • tableReading: drops-or-scrambles Reported by recruiters and testers
  • readsHeadersFooters: false Reported by recruiters and testers
  • readsTextBoxes: false Reported by recruiters and testers
  • headingRecognition: lexicon-only Reported by recruiters and testers
  • nameDetection: top-of-body Reported by recruiters and testers
  • dateParsing: single-format Our best judgement
  • extractsHiddenText: true Our best judgement

Documented per-system differences

  • greenhouse: Greenhouse's own "Unsuccessful resume parse" support doc lists columns, tables, headers/footers, text boxes, images, letter-spacing, unclear sections, bare company names (no Inc./LLC) and abbreviated titles as parse failures — the vendor anchor for the generic model. Documented by the vendor
  • workday: Workday's admin guide states it does NOT auto-fill Skills or Languages, and that parsing results vary with résumé format and word order; its extracted field set is narrower than the generic model. Documented by the vendor
  • lever: Lever's help article lists accepted formats (Word/docx, PDF, RTF, WordPerfect, HTML, ODF) and states it cannot parse image files (JPG/PNG). Reported by recruiters and testers
  • taleo: No vendor parsing document found — Oracle documents recruiter SEARCH modes (exact/related/conceptual), not parsing behaviour. Our best judgement

Versions & reproducibility

Same file, same rule versions, same date — same result. Every analysis records these:

  • Reading rule pack: 0.1.0
  • PDF reader: pdfjs-dist 6.3.289
  • Engine stage pdfLayout: 1.0.0
  • Engine stage glue: 1.0.0
  • Engine stage docxRead: 1.0.0
  • Engine stage intake: 1.0.0
  • Engine stage fields: 1.1.0
  • Engine stage findings: 1.0.0
  • Engine stage ruleEngine: 1.0.0
  • Engine stage simulate: 1.0.0

Each analysis also carries a reproducibility fingerprint — a short hash over these versions plus how your own device handles characters. You’ll find the exact fingerprint for your result in its receipt, under the methodology view.

Phase 1 uses no third-party datasets. Attribution for ESCO and O*NET arrives with the job-fit reading in a later phase.

← Back to the resume checker