How ATS Parsers Read Work Experience Dates, Career Gaps & Overlapping Roles (Greenhouse, Workday & iCIMS Breakdown)
When a software engineer or product manager with seven years of full-time experience gets auto-rejected within 90 seconds of applying for a role requiring "5+ years of experience," the culprit is rarely their skill set. In our audits at Smart Resume Analyzer , date-span tokenization failure is the single most common reason an Applicant Tracking System (ATS) miscalculates total Years of Experience…
When an applicant's resume is processed by an Applicant Tracking System (ATS), several factors can lead to automatic rejection, with date tokenization failure being the most common issue. ATS platforms such as Workday, Greenhouse, iCIMS, Lever, and Oracle Taleo convert the applicant's work experience layout into a structured format that requires explicit start and end dates in ISO-8601 format (YYYY-MM).
If the date string fails to match the required format, the parser defaults the EndDate to StartDate (0 months) or drops the tenure altogether.
The calculation of work experience and total years of experience in an ATS is carried out using regex tokenizers that require explicit month and year pairs (MM/YYYY or MMM YYYY – Present) associated with the job title or company name. After extracting date ranges, the system merges overlapping intervals to avoid double-counting and sums the non-overlapping months to determine total Years of Experience (YoE).
Commercial resume parsers tokenize date strings based on specific regular expressions. However, they fail on certain date patterns, such as Day-Month-Year slash ambiguity (04/05/2022 - 08/11/2024) due to locale ambiguity between US and UK/EU formats, year-only spans (2023 – 2024) where missing months default to 01, and side-by-side date blocks that break the StartDate regex token, resulting in 0.0 calculated years for senior roles.
To avoid undercounting in work experience, applicants should format their date blocks properly. For instance, a "FinTech Core - Remote, US Senior Backend Engineer" role with "March 2021 – Present" would be parsed correctly by all major ATS platforms. Similarly, when listing multiple promoted titles directly under one another without repeating the company context, older parsers may incorrectly bind only the first role's dates to the company header and merge the remaining titles into the bullet body. To prevent this, each promoted title should be listed separately with its own company context.
When working multiple jobs simultaneously or running a freelance consulting practice alongside a full-time job, enterprise ATS parsers prevent double-counting using Interval Union Normalization. For example, working full-time from January 2021 – Present alongside running a consulting practice from June 2022 – Present would result in a merged timeline of 70 months of total YoE rather than the sum of the individual roles.
Lastly, ATS platforms like Greenhouse, iCIMS, and Lever populate the "Current Title" field based on whichever Present role appears first in the resume. To ensure the correct title is highlighted, applicants should list their primary full-time Present role at the top and place concurrent consulting below it. By following these guidelines, applicants can ensure their work experience and dates are accurately parsed by ATS platforms, increasing their chances of passing through the initial screening process.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
