Dataset
ATS Synthetic Resume Corpus
Download ATS Synthetic Resume Corpus v0.1.0 with CSV/JSON artifacts, schema, checksum, license, source notes, limitations, and citation details.
About the Dataset
Privacy-safe synthetic resume cases index and expected labels for parser and layout risk benchmarks.
Intended Uses
- tool explanation
- research citation
- public methodology
Non-Uses & Constraints
- candidate evaluation
- hiring prediction
- ATS vendor claims
Method and scope
This dataset is tied to a route-owned method trail, source inventory, update cadence, and limitation record.
- Update cadence
- on publish
- Route family
- dataset
- Method IDs
- Launch method registry
Citation
Cite the page with its title, owner, publication date, and canonical URL.
InfiniteResume.ai Career Intelligence Lab. (2026). ATS Synthetic Resume Corpus v0.1.0. InfiniteResume.ai. https://www.infiniteresume.ai/datasets/ats-synthetic-resume-corpus
First published 2026-06-26. Last updated 2026-06-27.
Download Artifacts
Version Governance
Related Evidence
Dataset Preview (First 5 Rows)
Below is a subset of the dataset's rows. Use the download buttons above to retrieve the full CSV or JSON files.
| case_id | version | role_family | layout_id | layout_label | page_count | file_format | text_layer_expected | reading_order_risk_expected | section_detection_expected | contact_detection_expected | risk_flags_expected | expected_result_state | public_notes | limitations |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ats-v010-software-engineer-l01-001 | 0.1.0 | Software engineering | l01 | Single-column clean | 1 | present | low | contact;summary;skills;experience;projects;education | email;phone;location;linkedin | none | clear | Clean single-column software engineer resume with standard headings and clear text layer. | Standard layout which represents the easiest parsing target. | |
| ats-v010-software-engineer-l02-002 | 0.1.0 | Software engineering | l02 | Two-column sidebar | 1 | present | medium | contact;skills;experience;education;projects | email;phone;location | two_column_layout | review | Software engineer resume using a two-column layout with skills and contact in sidebar. | Some parsers read columns left-to-right rather than column-by-column, mixing text fragments. | |
| ats-v010-software-engineer-l03-003 | 0.1.0 | Software engineering | l03 | Table-based layout | 2 | present | high | contact;summary;experience;education;projects;skills | email;phone;linkedin | table_layout;complex_formatting | review | Software engineer resume layout constructed using invisible or border tables. | Tables frequently throw off reading order and cause text from adjacent cells to merge. | |
| ats-v010-software-engineer-l04-004 | 0.1.0 | Software engineering | l04 | Visual-heavy text-layer risk | 1 | partial | high | contact;skills;experience | email;phone | low_text_density;fragmented_extraction;image_heavy | high_risk | Visual-heavy designer-style software engineer resume with icons, graphics, and low text density. | Icons replacing section headers or non-standard fonts can break text layer extraction completely. | |
| ats-v010-product-manager-l01-005 | 0.1.0 | Product management | l01 | Single-column clean | 1 | present | low | contact;summary;experience;education;skills | email;phone;location;linkedin | none | clear | Standard clean resume layout for a Product Manager. | Represents optimal parsing setup. |
Schema & Field Definitions
Fields defined in the dataset dictionary:
| Field Name | Type | Required | Description | Notes / Source Grounding |
|---|---|---|---|---|
| case_id | string | Required | Unique code identifying the synthetic case. | — |
| version | string | Required | Corpus version. | — |
| role_family | string | Required | Target job role family. | — |
| layout_id | string | Required | Layout template variant code (l01-l04). | — |
| layout_label | string | Required | Description of layout complexity. | — |
| page_count | integer | Required | Page count of document (1 or 2). | — |
| file_format | string | Required | File type format (PDF, DOCX, TXT). | — |
| text_layer_expected | string | Required | Readable text layer expected status (present, partial, missing). | — |
| reading_order_risk_expected | string | Required | Layout reading order risk level (low, medium, high). | — |
| section_detection_expected | string | Required | Semicolon-separated expected section IDs. | — |
| contact_detection_expected | string | Required | Semicolon-separated expected contact details. | — |
| risk_flags_expected | string | Required | Semicolon-separated layout warning flags. | — |
| expected_result_state | string | Required | Expected diagnostic state (clear, review, high_risk). | — |
| public_notes | string | Required | Summary notes on case objectives. | — |
| limitations | string | Required | Layout constraints and parser bounds. | — |
Data Privacy & Governance Statement
No user-uploaded resumes or private user data.
Corrections or clarifications? Submit a request via the contributions form.