RS-1.1 — No real text to read (an image or a scan)
- gold image-only.pdf; ResumeExtractBench scans (checked 2026-10-04)
Changelog: v1.0.0 (2026-10-04) first version
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.
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.
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.
These are separate readings. We never combine them into one score.
The reading starts at 100. Each problem subtracts a penalty — a base amount for how much it hurts, multiplied by how confident we are:
| Severity | Base penalty |
|---|---|
| Can block reading | 30 |
| Weakens the reading | 10 |
| Polish | 3 |
| Confidence | Multiplier |
|---|---|
| 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.)
Pack version 0.1.0. Each rule, what it checks, how serious it is, and the evidence behind it.
Changelog: v1.0.0 (2026-10-04) first version
Changelog: v1.0.0 (2026-10-04) first version
Changelog: v1.0.0 (2026-10-04) first version (re-dressing the layout column detection)
Changelog: v1.0.0 (2026-10-04) first version
Changelog: v1.0.0 (2026-10-04) first version
Changelog: v1.0.0 (2026-10-04) first version (re-dressing the step-3 header/footer finding)
Changelog: v1.0.0 (2026-10-04) first version
Changelog: v1.0.0 (2026-10-04) first version
Changelog: v1.0.0 (2026-10-04) first version (re-dressing author glue)
Changelog: v1.0.0 (2026-10-04) first version
Changelog: v1.0.0 (2026-10-04) first version (conformance over the reading headings)
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
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
A phone without a leading +country is ambiguous abroad; reasoned, not independently tested, so assumption.
Changelog: v1.0.0 (2026-10-04) first version
Changelog: v1.0.0 (2026-10-04) first version
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
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 Same file, same rule versions, same date — same result. Every analysis records these:
pdfLayout: 1.0.0glue: 1.0.0docxRead: 1.0.0intake: 1.0.0fields: 1.1.0findings: 1.0.0ruleEngine: 1.0.0simulate: 1.0.0Each 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.
Searches the site's blog and tools.