Of all the things you agonized over on your resume, the dates probably got the least thought. They are just dates. You put them where the template put them and moved on. Here is the uncomfortable news: dates are one of the few places on a resume where the software does actual math, and when the math goes wrong, years of your working life can silently evaluate to zero.
The fix costs you ten minutes and requires no talent, just knowing the rules. This guide covers how tenure is computed from your dates, the formats every parser reads, the honest way to write a current role, and the specific mistakes that make real experience vanish.
Dates are where the ATS does math
Most of your resume is read as text: keywords matched, phrases extracted, sections filed. Dates are different. Parsers convert your employment dates into actual date values and compute with them. From your date ranges, the system derives:
- Tenure per job. March 2020 to March 2023 becomes 36 months.
- Total years of experience, by summing ranges, sometimes per skill or per title.
- Gaps, the spaces between one job's end and the next one's start.
- Recency, how current your relevant experience is.
That derived data feeds filters and rankings directly. When a recruiter sets a filter for "minimum 3 years of experience," no human counts anything: the system compares its computed number against the threshold, as part of the broader scoring described in how ATS scores and ranks resumes.
Now the failure mode is obvious. If a date range fails to parse, that job contributes zero months to the total. Your resume still looks complete to every human who opens the file, but the record says you have less experience than you do, sometimes none at all. A ten-year veteran can fail a three-year filter without anyone, including the recruiter, ever knowing why.
The format that always works
Here is the entire safe zone, and it is comfortably roomy:
- Month-year, written out or abbreviated: March 2021 to March 2023, or Mar 2021 - Mar 2023.
- Month-year, numeric: 03/2021 - 03/2023.
- Separators parsers understand: the word "to," a hyphen, or an en-dash produced by your word processor. All fine.
- Current roles: start date, then "Present." As in: June 2022 to Present.
And the rules that matter more than which variant you pick:
- Be consistent. One format for every job on the document. Mixing "March 2021" on one line with "3/21" on another invites exactly the ambiguity that breaks parsers.
- Never use two-digit years. "03/21" could be March 2021 or the 21st of March. Some parsers guess wrong. Four-digit years, always.
- Put dates on the same line as the job, or the line directly below. The parser attaches dates to job entries by proximity. Dates floating in a side column or grouped in a separate block can get attached to the wrong employer or dropped, one of several ways work history parsing goes sideways.
- Keep dates as text, not graphics. A timeline visual with dots and bars is invisible after text extraction. If your dates live only in the graphic, they do not exist.
Month-year versus year-only: the honest trade-off
Some people write "2021 - 2023" with no months, sometimes to save space, sometimes to soften a short stint or a gap. Know exactly what this buys and costs.
What it costs with the software: precision. "2021 - 2023" might be 13 months (December 2021 to January 2023) or 35 months (January 2021 to December 2023). Parsers handle year-only ranges, but they must estimate, and estimates are typically conservative. You may be credited with less tenure than you earned.
What it costs with humans: trust, sometimes. Recruiters know why people drop months. A resume that is year-only across the board reads as a possible pattern, and an experienced screener will simply ask for the months in the phone screen. If the year-only format was hiding something, you now get to explain it live, on the spot, having also signaled that you hoped not to.
The honest playbook is the effective one: use month-year everywhere, and handle gaps in the open. A gap named and briefly explained is routine; recruiters see them constantly. There is a full guide to explaining employment gaps on your resume with wording for the common situations. Hiding a gap behind vague dates converts a normal circumstance into what looks like a red flag, which is a terrible trade.
One legitimate exception: jobs from 15+ years ago that you compress or summarize. Year-only is fine in an early-career summary line, because nobody is filtering on your tenure from 2009.
Writing your current job
Three rules for the role you are in now:
- Use "Present," capitalized, after your start date. "June 2022 - Present." Every parser is trained on it. "Current" also works. "Now," "Ongoing," or a blank end date are shakier.
- Never write a future end date. If you know you finish in August, the resume still says Present until you have finished. A future date confuses parsers and reads oddly to humans.
- If you were laid off recently and the job just ended, end-date it honestly. Leaving a finished job as "Present" is a fact error that surfaces in background checks. An end date last month with an active job search is completely normal; recruiters process it without blinking.
Education dates and other small cases
- Degrees: graduation month and year is standard, or year alone, which is safe here because nobody computes tenure from your diploma. If the degree is in progress, "Expected May 2027" parses and reads correctly.
- Certifications: issue year, plus expiry if your field cares. "PMP, 2024" or "PMP (2024, expires 2027)."
- Overlapping jobs: list both with true dates. Parsers handle overlaps fine, and honest overlap (a side contract during a full-time role, two part-time jobs) needs no disguise.
- Same company, multiple roles: give each role its own dates under one employer heading. This preserves both your total tenure and your promotion story in the parsed record.
Look at your dates the way the filter will
Every failure in this article shares one property: invisible from the document, obvious in the parsed record. The resume looks fine. The record says two years where you lived seven. The only reliable check is to look at the record side.
The free Bounce scan at careerbounce.io shows you exactly that: what the bots extracted from your file, including how your employment dates came through and where a range failed to parse. It is free, there is no signup, and it runs entirely on your device, so your resume never leaves your machine.
Run it before your next application. Ten minutes of date hygiene will not get anyone a job, and no honest tool will promise that. What it does is narrower and real: it makes sure that when a filter asks how much experience you have, the answer is the truth, not zero.