Dates and employment gaps: what parsers extract

What ResumeTune does and does not check

ResumeTune's free check scores four things: how many of your terms match a pasted job description, how many recognized section headings it found, a format assessment, and whether your bullets begin with accomplishment verbs. Dates are not among them.

There is no date extraction, no tenure calculation, and no gap detection anywhere in the free scorer. A resume with immaculate dates and one with no dates at all score identically on that dimension, because that dimension does not exist.

This is worth saying clearly because a guide on a scanner's own site has an obvious incentive to imply its tool measures whatever the article is about. It does not, and the advice below is useful for reasons independent of any score ResumeTune produces.

Why dates are hard to extract reliably

A date on a resume is a short string with enormous format variation and no surrounding markup declaring what it is. "03/04/2021" is the third of April or the fourth of March depending on where it was written, and nothing in the document says which convention applies.

Ranges add a second layer. A parser has to recognize that two dates near each other form a single span, identify the separator between them, and attach the whole span to the correct role — which requires knowing where that role block begins and ends. Each of those steps can fail independently.

Layout is what usually breaks it. Dates are commonly right-aligned against a job title, or placed in a narrow sidebar column. Both survive visual reading perfectly and both are exactly the arrangements that extraction reorders, producing text where a date sits next to an employer it does not belong to.

A date format that survives extraction

The most robust choice is an unambiguous month and a four-digit year, written the same way every time: "March 2021" or "Mar 2021". A spelled month cannot be misread as a day, and a four-digit year cannot be misread as a month.

Numeric-only formats are where ambiguity enters. "03/2021" is readable but invites the day-versus-month question; "03/04/21" compounds it with a two-digit year. If you must use numerals, ISO ordering — 2021-03 — is the least ambiguous, though it reads coldly to a human.

Consistency matters as much as the format itself. A resume mixing "March 2021", "03/2021", and "Spring 2021" gives an extractor three patterns to recognize instead of one, and gives a reader the impression of carelessness.

• Use a spelled or abbreviated month with a four-digit year.
• Use the same format for every date in the document.
• Avoid two-digit years entirely.
• Avoid seasons — "Spring 2021" is not a date any parser resolves.

Separators, ranges, and the en dash problem

A range needs a separator a parser recognizes. A plain hyphen surrounded by spaces — "March 2021 - June 2023" — is the safest option, because it is a plain ASCII character that survives every encoding path.

Typographic dashes are the common trap. Word processors silently convert a hyphen into an en dash or em dash, and while most extraction handles these correctly, some paths render them as a replacement character or drop them. When that happens the range collapses into two adjacent dates with nothing joining them.

The word "to" is a reliable alternative — "March 2021 to June 2023" — and is immune to the substitution problem entirely. It costs two characters and reads naturally.

Marking a current role

For a job you still hold, "Present" is the widely understood convention: "March 2021 – Present". It is unambiguous to a reader and is the term most commonly recognized where software looks for one.

Avoid leaving the end open with a trailing dash and nothing after it. "March 2021 –" reads as unfinished, and an extractor has no way to distinguish an intentionally open range from a truncation.

Avoid "Current" and "Now" as substitutes. They are understood by people but are less conventional, and there is no benefit to the variation.

Where dates get separated from their jobs

The most damaging date problem is not the format — it is a correctly formatted date attached to the wrong employer after extraction. This happens through layout rather than wording.

Right-aligned dates are the usual cause. Visually the date sits on the same line as the job title; in the extracted text, depending on how the alignment was produced, it may land on its own line, before the title, or merged with the previous role's final bullet. Tabs and long runs of spaces are the fingerprint of this, and ResumeTune's format check does flag those as a possible column or reading-order issue.

Placing the date on the same line as the title, separated by a comma or a pipe, or on its own line directly beneath the title, avoids the problem. Both are conventional and neither depends on alignment surviving extraction.

• Keep each role's title, employer, and dates adjacent in reading order.
• Avoid right-alignment achieved with tabs or repeated spaces.
• Avoid putting dates in a separate column from the roles they describe.
• Check the plain-text paste of your resume — the dates should still sit with their own jobs.

Employment gaps: what is actually known

Here the honest answer is narrower than most advice suggests. A system that successfully extracts your dates can compute the intervals between roles, and some recruiting software surfaces tenure or continuity information to recruiters. Whether a specific employer's system does this, whether anything is flagged automatically, and whether a recruiter ever sees it are configuration details those vendors do not publish.

So claims that "the ATS will automatically reject you for a gap" are not verifiable, and the confident versions circulating online are not evidence-based. What is reasonable to assume is that a gap is visible to anyone reading your dates, whether that reading is done by a person or a machine, and that it may prompt a question.

That reframes the problem usefully. The goal is not to defeat a detection mechanism whose behaviour you cannot know — it is to make sure a reader encountering the gap has enough context not to guess.

Handling a gap without distorting the record

The approach that holds up is accuracy with brief context. Keep the real dates, and where the gap is substantial, give it a short honest label in the same structure as any other entry — "Career break — full-time caregiving", "Career break — medical leave", "Independent study and contract work" — with the dates it covers.

This works because it answers the question at the point it arises rather than leaving it open. It also keeps your timeline continuous, which is easier to read than a sequence with an unexplained hole.

What does not work is manipulating dates to close the gap. Stretching an end date, dropping months to leave only years, or omitting a role entirely creates a record that contradicts what a background check or a reference conversation will produce. That is a materially worse position than the gap itself, and it is the reason the year-only trick is bad advice despite being widely repeated.

• Keep real start and end dates for every role.
• Label a substantial break briefly and factually.
• Do not switch to year-only formatting to disguise a gap.
• Do not extend a role's end date to overlap the next one.