Date formatting on a resume is one of those small details that looks like it shouldn't matter and quietly matters a lot. Wrong format and an ATS parser misreads your dates — sometimes assigning the wrong tenure to a role, sometimes dropping a role entirely, sometimes calculating your total experience as half what it is. The recruiter then sees a candidate who looks underqualified by years.

This post is about which date formats survive ATS parsing reliably and which ones don't.

What parses cleanly

The formats that parse reliably across most ATS systems share a pattern: they're unambiguous and use a four-digit year.

Full month name with four-digit year. "January 2022 – March 2024" is the safest format. Every major ATS parser handles it. Even older systems that were trained on inconsistent data parse this correctly.

Abbreviated month with four-digit year. "Jan 2022 – Mar 2024" works in essentially all modern parsers. Slightly more space-efficient than the full month name; same reliability.

Numeric MM/YYYY. "01/2022 – 03/2024" works in most systems. Use a leading zero (01 not 1) and the four-digit year. Some old parsers handle slashes inconsistently, so this is slightly less reliable than month-name formats, but acceptable.

Year-only when context is clear. "2022 – 2024" works for roles where the exact months don't matter (long tenure, no overlap risk with adjacent roles). Use sparingly — most parsers prefer month-level granularity.

Current role with "Present" or specific end. "March 2024 – Present" or "March 2024 – Current" both parse correctly. Avoid creative phrasings like "Ongoing" or "Now."

Formats that misparse

The misparsing rates vary, but a few patterns drop out as consistently problematic.

Apostrophe-year ("'22"). The single most common misparse. The apostrophe is read as a quote mark by some parsers, and the year drops out entirely. The role then appears in the ATS database with no end date, which sometimes silently drops it from search results. About 28% misparse rate in informal benchmarks across major parsers.

Season-year ("Spring 2022"). Most parsers don't map seasons to months. The result is either no date assignment or an incorrect default. Use months.

Slash format without leading zero ("3/22"). Ambiguous — could be March 2022, March 1922, or interpreted as a day/month. Some parsers guess wrong. Use four-digit years and leading zeros.

Non-standard separators (dots, em-dashes between dates). "2022.03" and similar variants are unconventional and parse inconsistently. Use a hyphen or "–" between the start and end dates.

Dates buried in paragraph text. Some parsers only scan the dedicated date column or area; dates mentioned in paragraph descriptions ("I worked at this company from 2022 to 2024") may not be picked up. Always have a dedicated date in the header line of each role.

For the underlying mechanics of how parsers work, see how-applicant-tracking-systems-work. For other format-related parsing issues, see resume-mistakes-that-auto-reject.

The consistency rule

The second-largest parsing failure mode after format choice is inconsistent format within a single resume. "January 2022 – March 2024" for the most recent role, "01/2022 – 03/2024" for the previous one, and "2018 – 2020" for the role before that.

Each format individually parses fine, but the mix confuses some ATS systems. They expect a uniform pattern. When they can't find one, they sometimes default to skipping entries or merging adjacent roles into one.

Pick one format and apply it uniformly. To every role, every certification, every education entry, every project with dates. The format you pick matters less than the consistency.

Edge cases worth knowing

A few specific situations have their own conventions:

• Concurrent roles. Two roles overlapping in time? List them with explicit dates and a parenthetical note: "(concurrent with role above)." Don't try to merge them visually.
• Short gaps. A two-month gap between roles is normal and doesn't require accounting for. A six-month-plus gap should be addressed explicitly — see resume-gap-explanation-strategies.
• Multiple roles at the same company. List the company once, with sub-bullets for each role and its date range. This parses better than three separate "Company X" entries with overlapping dates.
• Contract or temp work. Date the actual engagement, not the contract assignment period. "January 2022 – June 2022 (Contract via Manpower)" is clearer than the manpower agency's start/end.

Tenure calculation traps

ATS systems often calculate total experience by summing role tenures. Date format errors cause systematic miscalculations here:

• Missing end dates lead to roles being treated as still active (good or bad depending on context).
• Misparsed years lead to roles being assigned to wrong decades.
• Overlapping role dates that aren't flagged sometimes get double-counted (inflated) or merged (deflated).

If you've consistently formatted dates and the resume shows the correct sequence, this calculation usually works. If you've left ambiguity, the calculation drifts.

A specific trap: roles dated "2018 – 2020" parsed as "January 2018 – January 2020" (2 years) when the actual tenure was "October 2018 – November 2020" (over 2 years). The exact-month version is more accurate; the year-only version compresses the tenure.

When to use "Present"

The convention is "Present" for currently active roles. "Current" works in most parsers. "Now" and "Ongoing" are less standard — both will parse in most systems but introduce avoidable risk.

If a role ended very recently and you're applying soon, listing the actual end date is fine. "March 2024 – June 2024" for a role you left a week ago is more accurate than "March 2024 – Present." The exact-end version also signals you've moved on and aren't currently employed there.

What this isn't

A few clarifications:

• It's not the most important format choice on your resume. Section headers, bullet structure, and content matter more.
• It's not a guarantee against parsing errors. Some ATS systems have idiosyncrasies that even clean formatting can't avoid.
• It's not a substitute for a clean structure overall. A consistently-dated resume in a parsing-hostile layout still gets misread.

The short version: full month and four-digit year, or "MM/YYYY" with leading zeros. Use the same format everywhere on the resume. Avoid apostrophe-years, season-years, and dates buried in paragraph text. The format you pick matters less than applying it consistently.