Dataset
Resume Section Taxonomy
Download Resume Section Taxonomy v0.1.0 with CSV/JSON artifacts, schema, checksum, license, source notes, limitations, and citation details.
About the Dataset
Resume Section Taxonomy launch dataset outlining canonical headers, aliases, and detection hints used by InfiniteResume.ai parser diagnostics.
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). Resume Section Taxonomy v0.1.0. InfiniteResume.ai. https://www.infiniteresume.ai/datasets/resume-section-taxonomy
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.
| section_id | canonical_label | section_group | aliases_high_confidence | aliases_review | detection_hints | risk_notes | example_headings | glossary_links | tool_linkage | locale | version_added | status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| contact | Contact | core | Contact;Contact Information;Contact Info;Personal Info;Personal Details | About Me;Connect;Reach Out | Located at the very top of the document or in a sidebar. Often contains phone numbers, emails, LinkedIn links, or locations. | If labeled 'About Me', a parser might confuse it with a professional summary. | Contact;Contact Information;Get In Touch | contact-information-visibility | ats_parser_preview | en-US | 0.1.0 | active |
| summary | Summary | core | Summary;Professional Summary;Profile;Professional Profile;Career Summary;Executive Summary | Objective;Career Objective;About Me;About | A short text block (paragraph or bullet points) at the top of the resume below contact information. | 'Objective' is considered outdated in modern resumes. 'About Me' can overlap with contact information. | Summary;Professional Summary;Profile;About Me | ats-score | ats_parser_preview | en-US | 0.1.0 | active |
| skills | Skills | core | Skills;Technical Skills;Core Competencies;Key Skills;Technologies;Skills & Expertise | Expertise;Qualifications;Tool Stack;Stack;Strengths | Grid or list of single-word or short-phrase items representing tools, languages, methodologies, or capabilities. | 'Expertise' might overlap with summary. 'Qualifications' might overlap with education or certifications. | Skills;Technical Skills;Skills & Technologies;Core Competencies | hard-skills;soft-skills;skills-taxonomy | ats_parser_preview;jd_keyword_extractor | en-US | 0.1.0 | active |
| experience | Experience | core | Experience;Work Experience;Professional Experience;Employment History;Work History | Career History;Roles;Client Work;Professional Highlights | Reverse-chronological list of roles with company names, dates, job titles, and bulleted achievements. | 'Client Work' could be projects rather than traditional employment history. | Experience;Work Experience;Professional Experience | recruiter-screen | ats_parser_preview | en-US | 0.1.0 | active |
| projects | Projects | core | Projects;Technical Projects;Selected Projects;Personal Projects;Key Projects | Portfolio;Case Studies;Open Source;Academic Projects | Lists of individual project achievements, tools used, and links, separate from professional employment. | Portfolio sections sometimes redirect to external links, which parsers might ignore or fail to follow. | Projects;Selected Projects;Technical Projects | transferable-skills | ats_parser_preview | en-US | 0.1.0 | active |
Schema & Field Definitions
Fields defined in the dataset dictionary:
| Field Name | Type | Required | Description | Notes / Source Grounding |
|---|---|---|---|---|
| section_id | string | Required | Unique snake_case identifier of the section. | — |
| canonical_label | string | Required | Display name of the section. | — |
| section_group | string | Required | Group category (core or secondary). | — |
| aliases_high_confidence | string | Required | Semicolon-separated high confidence parser headings. | — |
| aliases_review | string | Required | Semicolon-separated ambiguous headings requiring review. | — |
| detection_hints | string | Required | Parser layout and parsing hints. | — |
| risk_notes | string | Required | Ambiguities and parser mismatch notes. | — |
| example_headings | string | Required | Semicolon-separated synthetic heading examples. | — |
| glossary_links | string | Required | Linked glossary terms. | — |
| tool_linkage | string | Required | Semicolon-separated tools relying on this section. | — |
| locale | string | Required | Locale (en-US default). | — |
| version_added | string | Required | Dataset version when field was added. | — |
| status | string | Required | Active or deprecated status. | — |
Data Privacy & Governance Statement
No user-uploaded resumes or private user data.
Corrections or clarifications? Submit a request via the contributions form.
