Open noindex dataset
ATS parser rules and public change log
A source-linked watchlist of public ATS resume parsing signals, format risks, AI feature notes, and dated audit rows.
Download
JSON keeps one row per ATS system. CSV expands summaries, parser notes, format guidance, and change rows for spreadsheet review.
Limits
This dataset does not reveal proprietary ATS scoring and does not guarantee interviews, recruiter review, or job offers. Rows marked verified:false are intentionally noindex until public effective dates and parser claims are stronger.
Citation
Cite the canonical dataset page so readers see the methodology, downloads, no-guarantee warning, and embed option.
ATS parser rules and public change log. PolishCat. Last reviewed 2026-06-29. https://polishcat.com/data/ats-parser-rules
Embed
The iframe is noindex and points attribution back to this canonical data page.
Source: ATS parser rules and public change log by PolishCat
| ATS | Public source | Parser notes | Verified |
|---|---|---|---|
| Greenhouse | Greenhouse Support - AI features | Use plain section headings and text-layer resume files so candidate data can be extracted and reviewed. Do not hide important evidence in images, headers, footers, or decorative layouts. Mirror the job's real skills and title language, but only where the experience is true. | false |
| Workday | Workday Talent Acquisition | Write canonical skill names that a skills graph can recognize, such as SQL plus the full context around it. Avoid stuffing repeated keywords; Workday's public copy emphasizes skills and matching, not exact-match spam. If the portal imports or parses your resume, review every auto-filled field before submitting. | false |
| iCIMS | iCIMS Coalesce AI | Use the job title, skills, tools, and outcomes in normal sentence context. Give skills enough surrounding evidence that a skills-and-experience model can understand seniority. Treat AI ranking claims as recruiter workflow support, not as a job-seeker guarantee. | false |
| Lever | Lever Help Center - Understanding Resume Parsing | Make the resume easy to extract into profile fields: name, contact, experience, education, and skills. Use conventional headings and keep important facts in selectable text. If a Lever profile shows parsed fields, review them before final submission where possible. | false |
| Oracle Taleo | Oracle Help Center - Candidate File Import | Treat the parsed profile fields as the object recruiters may search, not just the uploaded file. Use plain labels such as Experience, Education, Skills, and Certifications. After upload, manually review and correct any pre-filled fields if Taleo exposes them. | false |
| SAP SuccessFactors | SAP Help Portal - Configuring Resume Parsing | Make candidate profile fields easy to populate by using clear text and standard field names. Keep contact, employment, education, and certifications in normal reading order. If upload or parsing fails, follow employer instructions rather than trying hidden keyword tricks. | false |