Resume Date Format: How to Write Dates on a Resume (With Examples)

Recruiters filter candidates by "years of experience" all the time. Many systems calculate that number from your job dates. If your dates are formatted in a way the parser doesn't understand, your "years of experience" field comes back blank, and you don't appear in those filtered searches. This is one of the most fixable, most ignored ATS issues.

Resume date format examples at a glance

The short answer: month and year, the same way on every line. Here is how that looks for each part of a resume or CV.

Three formats are equally safe: January 2021, Jan 2021 and 01/2021. Pick one and use it everywhere. Join the two dates with an en dash (–), a hyphen (-) or the word "to", with a space on each side, and use the same joiner in every line.

When I look at what our scanner reads from real resumes, dates are one of the quieter problems: in the 1,540 scans we logged between 18 and 22 October 2026, about 7% had dates the checker flagged as ambiguous. That is small, but it is 7% of people whose "years of experience" may come out wrong without them ever knowing.

The 4 standard date formats

These four formats are the standard advice, and month-and-year dates are the safest of them. Our own scanner reads month-and-year ranges reliably:

1. Full month, year, full month, year
   January 2021 – Present
March 2018 – December 2020
2. Abbreviated month, year, abbreviated month, year
   Jan 2021 – Present
Mar 2018 – Dec 2020
3. MM/YYYY format
   01/2021 – Present
03/2018 – 12/2020
4. Year-only (acceptable for older roles or when months are vague)
   2021 – Present
2018 – 2020
   Use this sparingly: with years alone, a parser cannot work out tenure to the month, and our scanner flags a resume that dates every role this way.

Pick one of these four and use it consistently across all roles in your resume. Mixing formats (one role uses "Jan 2021 – Present" and another uses "01/2021 – present") confuses some parsers.

Date formats that frequently break ATS parsing

1. Apostrophe-shortened years

Don't use: Jan'21 – Present or '21 – '24

The apostrophe-and-two-digit-year pattern was popular in 1990s and 2000s resume templates. Many parsers do not recognise it reliably. The "21" can extract as a standalone number, the apostrophe can drop, and the parser may conclude there's no valid date in this position.

2. Period-separated dates

Don't use: 1.2021 – 5.2024 or 01.2021 - 05.2024

European date formatting using periods between day/month/year is less standard for ATS systems. A parser may read "1.2021" as a decimal number rather than a date. Use slash separators (01/2021) or hyphenated month-year format (Jan 2021) instead.

3. "Now" or "Currently" instead of "Present"

Don't use: Jan 2021 – Now or Jan 2021 – Currently

Use: Jan 2021 – Present

"Present" is the word parsers most commonly recognise for "currently in this role." Other words like "Now," "Currently," "Today," or "Ongoing" may work in some systems and not others. Always use "Present."

4. Reverse year order

Don't use: Present – Jan 2021

Some candidates write dates from most-recent-first to emphasize their current role. Parsers expect start date first, end date second. Reverse-ordered dates can be read as a single string with no valid date span.

5. Spelled-out months in non-English

Be careful with: dates spelled in non-English (e.g., German "Januar," French "Janvier," Arabic January)

If you're applying to an English-language ATS, write dates in English. Even bilingual resumes should keep dates in English.

Special cases

Multiple roles at the same company

If you've held multiple positions at the same company, format the company-level date range and individual roles like this:

CATERPILLAR INC.
Dubai, UAE | March 2019 – Present

Assistant Finance Controller, Middle East
March 2019 – July 2025
• Bullet 1
• Bullet 2

Senior Analyst, FP&A
March 2017 – March 2019
• Bullet 1
• Bullet 2

Each sub-role should have its own clean date range. Don't try to be clever with date overlaps or shared header dates, parsers handle them in different ways.

Gaps in employment

If you have a gap in employment, you have three options:

1. Leave the gap unexplained, the dates speak for themselves, and a parser does not penalise a gap on its own
2. Fill the gap with a relevant entry (consulting, freelance, education, sabbatical), use real dates honestly
3. Group early career roles by year only, 2014 – 2016: Various Accounting Roles

Don't fudge dates to hide gaps. Background checks and reference calls often reveal mismatches and that's an instant disqualifier.

Future-dated roles

If you have a job offer that starts in the future:

• If the role hasn't started yet, leave it off your resume, don't put dates from the future
• If you've signed but haven't started, you can include it as Joining September 2026 in a single line, but most candidates leave this off entirely

Concurrent roles

If you held two roles concurrently (e.g., consulting on the side while employed):

• List them as separate entries with their own date ranges
• Don't try to combine them into a single overlapping entry

Education, graduation and certification dates

Education is where most people hesitate, so here are the common cases:

• A finished degree: the year you graduated is enough (BSc Accounting, University of Leeds, 2018). Months add nothing here.
• A degree in progress: write Expected May 2027, or show the range with "(in progress)". Never write a future year on its own: it reads as if you have already graduated.
• Leaving out the graduation year: allowed, and some experienced candidates do it to avoid signalling their age. A parser simply records no date. If the employer asks for it later, give it honestly.
• Certifications and licences: the year you earned it, plus the expiry year if it lapses (PMP, 2022 (valid to 2025)). For professional memberships, "Member since 2015" works well.

Where to put the dates

Put each date range on the same line as the job title or employer, usually aligned to the right. What matters for the software is that the dates sit in the main body of the page, next to the role they belong to. Avoid putting them in a separate column, a table or a text box: those layouts are the most likely to come out of the extraction detached from the job, so the system cannot tell which dates go with which role.

How dates affect "years of experience"

Systems that calculate experience typically add up the duration of each work entry. Some may count overlapping periods once, others twice. You can't control how the ATS calculates, but you can ensure each role has a clean, parseable date range so it gets counted at all.

If your resume has 8 work entries and the parser successfully extracts dates for only 5, your "years of experience" may be calculated from those 5 entries, making you look less experienced than you are.

Quick checklist

• ☐ Every role has a date range visible (not "see CV" or "since college")
• ☐ Date format is consistent across all roles (don't mix "Jan 2021" and "01/2021" in the same resume)
• ☐ End date for current role says "Present" (not "Now" or "Today")
• ☐ No apostrophe-shortened years ("'21")
• ☐ Year is full 4-digit (2021, not 21 or '21)
• ☐ Dates joined the same way in every role: a hyphen (-), an en-dash (–) or the word "to"
• ☐ Months are in English

Test it

The fastest way to see if your dates are parsing correctly is to run your resume through an ATS-style parser and look at what it extracts. ATS Verification shows you whether each work entry was parsed correctly, including the date range, job title, company, and bullets.

If a role's dates show as blank or wrong, that's a date-format issue you can fix in 30 seconds. If multiple roles are showing date issues, your overall date format probably needs to be standardized.

Dates are one part of the experience block. How the title, employer and dates sit together, including promotions and contract work, is covered in how to write the work experience section.

→ Run a free ATS scan to check that all your dates parse correctly

Correction, 17 October 2026. Earlier versions of this article said four date formats parse correctly "in 100% of the ATS engines we've tested". We have not tested employers' ATS products, so we have removed that claim. We also removed advice against writing "Jan 2021 to Present", which contradicted the answer at the top of this article; our own parser reads that format fine. The advice now rests on how date parsing generally works and on what our own scanner reads.