Experiencer
Experiencer
Open Free Editor

Experiencer documentation

ATS readability

Inspect PDF text corruption, source-word recovery and independent parser evidence without inventing an ATS score.

Last reviewed:

Review the PDF you will submit

Open ATS Review to inspect a PDF from your device. Signed-in Free and Pro accounts can run local checks. The file stays in your browser unless you explicitly request a server comparison. Limits are 25 MB and 20 pages.

The workbench reports concrete evidence: unexpected control or replacement characters, suspicious private-use glyphs, sparse or empty extraction, and words split into letter fragments. Findings include affected pages, counts and escaped examples. Unavailable or incomplete checks have not passed. Local PDF.js does not expose every decoding error, so empty extraction alone cannot establish that a page is healthy.

Compare an editor snapshot with its PDF

With Pro, choose File → ATS Review → Export current document and review. The workbench stays over your editor and includes unsaved changes in an immutable snapshot. This explicit action uses server processing; private notes and template guidance are excluded, and no saved document or history revision is created.

The resulting report binds source text and PDF bytes to that snapshot. Its fingerprint identifies the exported editor state, rather than a saved cloud revision. If the editor changes afterward, export again to check the newer state. An arbitrary uploaded PDF has no bound source comparison.

Source-word recovery measures how many expected words were recovered. It preserves meaningful punctuation in terms such as C#, C++ and .NET, contact strings, dates and numeric values, while tolerating benign Unicode forms, ligatures and line wrapping. Opening phrases and heading sequence are checked separately. A recovery percentage is not an ATS score or proof that a system assigned text to the correct field.

Inspect different extraction strategies

PDF.js prefers validated logical tag order and falls back to geometric reconstruction when tags are absent or unreliable. Expand engine details to inspect per-page tag coverage, mapping diagnostics and logical roles. Separate views show geometric order and diagnostic content-stream fragments where available.

Pro adds Compare with independent parser. This explicit action uploads the selected PDF to Experiencer for a one-time PdfPig comparison. Engine versions and strategies are identified. Different strategies within PDF.js are still one engine; neither engine is an ATS product.

A sidebar or two-column layout can interleave rows geometrically while retaining sound logical order. Treat that as an informational layout tradeoff when words and logical grouping remain intact. Raw fragment concatenation alone does not prove that content is missing. Parser disagreement is evidence to inspect, not a vendor failure probability.

Verify a correction

  1. Review the affected page and escaped example, along with the rendered PDF and labeled extracted text.
  2. Inspect export or font settings, document structure and any genuinely omitted text. Keep important content as text in normal document flow.
  3. Export a corrected PDF and run the checks again. Do not assume that changing a font or simplifying columns fixed the problem without checking the new output.
  4. Compare before/after findings and their PDF/snapshot identities. Download the text or schema-versioned JSON report to retain the evidence and limitations.

Closing the editor workbench keeps the current run and one previous report in page memory while you edit. Reopen it to export the correction. Clear results, signing out, changing accounts or leaving the page clears that memory; nothing is saved to browser storage or your cloud document.

No LLM, job description or job-fit score is required. These checks do not perform OCR or automatically rewrite your résumé, and they cannot certify acceptance by every applicant-tracking system. ATS products use different parsers, field models and employer settings.

Word comparison is conservative. Inserted spaces or line wrapping in scripts without word separators can appear as missing words even when the characters remain intact; inspect the labeled text directly in those cases.

See Exporting and printing and Troubleshooting for the surrounding workflow.