11 min read
You're here because a portal preview shaved years off your timeline or stuck 2019 on the wrong company. That's common, and it's fixable. You don't need a new career story. You need dates the parser can read.
Short answer: To stop ATS from misreading dates on US resumes, use one Month Year pattern everywhere, put employer | title | dates on a single line per role, write Present for current jobs, and drop slashes, seasons, and table layouts. Parsers attach dates to the nearest text block, not the prettiest column on your PDF. You won't fix that with bolder fonts.
You're not fighting a secret algorithm. You're fixing layout habits that make Workday and Greenhouse grab March 2022 and stick it on the wrong employer. If preview shows six years of experience when you've got nine, the timeline is broken even when the PDF looks fine to you. That's fixable tonight if you'll standardize one date line pattern.
Check your resume for free after you normalize dates, not while you're still mixing 01/2020 and Jan 2020 on the same page. Below: why parsers stumble, the exceptions that still work, what to change tonight, and copy-paste lines you can drop into Experience. You won't need a new template. You'll need one boring pattern repeated on every job block.
Quick Wins
- Pick Mar 2021 to Present and use it on every role.
- Move dates onto the employer line; delete right-column date tables.
- Replace Now, Current, and Q3 2022 with Month Year or Present.
- Paste PDF into Notepad and confirm each date sits beside its job name.
Why US ATS products misread employment dates
Workday, Greenhouse, Lever, Taleo, and iCIMS import resumes by scanning left-to-right text blocks. They do not see your visual columns the way you do. When dates live in a sidebar, a table cell, or a footer timeline, the importer pairs them with whichever employer name appeared last in the raw text stream.
Mixed formats trigger the worst errors. A file that uses 03/2020 on one job, March 2020 on another, and 2020 alone on a third gives the parser three different rules. Numeric slashes read as ambiguous in US uploads because some systems still flip day and month on import.
Recruiters filter on years of experience and recency. When dates attach to the wrong role, you can fail a five-year requirement while holding eight years of real work. The failure is mechanical, not a judgment on your career. Fix the string layout and the same profile often passes the filter.
Edge case: contract roles with overlapping client dates. List each client as its own employer block with non-overlapping Month Year ranges when possible. If two contracts truly overlapped, note contract in the title line so humans understand parallel work without stacked identical start months on one row.
Edge case: you're military or academic with year-only degree dates. Year-only is acceptable in Education when month is unknown. Still use Month Year for every paid job in Experience. Do not downgrade employment entries to year-only just because school used 2020.
Edge case: short-term retail or gig roles you omit for space. Missing months create false gaps as badly as wrong months. If you leave a role off, ensure surrounding dates still read continuous. Recruiters notice six-month holes faster than six-month stints at a grocery chain.
A composite nurse practitioner resume listed travel contracts with only years in a sidebar. Workday calculated four years instead of eleven. Moving each contract inline with Month Year fixed the filter without changing clinical bullets.
Read US resume dates Month Year guide when you want a deeper format reference. This page focuses on stopping misreads, not re-explaining every calendar edge.
How to stop ATS from misreading dates: fix the timeline tonight
Work top to bottom on Experience. One pattern, one column, one line per employer. You'll know you're done when portal preview and Notepad paste agree on order and years.
Pick one Month Year pattern and delete the rest
Mar 2021 to Aug 2024 or March 2021 to August 2024 both work if you're consistent. Abbreviate months without a period: Jan, Feb, Mar. Use Present for current roles, not Now or Current. Search the file for slashes and replace every employment date that still uses them.
Before: Product manager resume mixes 01/2019, Jan 2019, and 2019 on three jobs; Workday preview shows overlapping ranges on the oldest employer.
After: Every role reads Company | Title | Jan 2019 to Mar 2021 in one line; preview totals nine years across three employers.
Put employer, title, and dates on the same line
Parsers treat line breaks as weak hints. Dates floating under a logo or in a right-aligned column detach from titles. Move them inline: Harbor Retail | Operations Analyst | Mar 2022 to Present, then bullets below.
Before: Designer resume lists company names left and years right in a table; Greenhouse maps 2020 to 2022 on the freelance row that had no dates in the left cell.
After: Single column with Studio North | Visual Designer | Jun 2020 to Feb 2022 on one line; bullets follow immediately.
Remove duplicate timelines in headers and footers
Icon timelines and footer bars repeat dates the parser reads as mystery employers. Delete them. Experience should be the only place employment dates appear. Education keeps its own Month Year or year-only lines under the degree.
A composite data analyst kept a footer strip reading 2018 to 2024 across logos. iCIMS created a phantom employer block with no title. Removing the strip fixed total experience without changing a single bullet.
Handle gaps and Present without overlap
End prior role Aug 2022. Start next Mar 2023. If you took time off, one honest gap line beats fake overlap. Present belongs on one current job only. Two Present ranges make parsers think you hold two full-time roles today.
Read how to explain a career break on your US resume when the gap needs one sentence recruiters understand.
Run Notepad paste and portal preview together
Export PDF, select all, paste into Notepad. Each employer name should appear before its dates in plain text. Upload to the application, open parsed preview, and compare. Mismatch means layout still wins over content. Fix the file before you submit knockout answers tied to years of experience.
When preview still misreads after inline dates, check for hidden text boxes in Word. Dates inside boxes often import last, pairing with the footer instead of the job title. Convert boxes to plain paragraphs, re-export, paste again. If two roles at one company share one start date, split promotions so each title change gets its own Month Year range recruiters can follow.
Exceptions that still parse cleanly
Year-only in Education when month is unknown. One Present role. En dash or the word to between start and end on the same line. Those are safe when Experience uses full Month Year everywhere else.
Before: Resume uses Present, Now, and Current on three freelance clients at once.
After: One primary client marked Present; other two show Mon YYYY end dates on separate lines with contract in the title.
Copy-paste employment date lines
Current role:
[Company] | [Job Title] | [Mon YYYY] to Present
Prior role:
[Company] | [Job Title] | [Mon YYYY] to [Mon YYYY]
Career gap (optional one line):
Career break | [Mon YYYY] to [Mon YYYY] | [one neutral reason]
Contract (parallel work):
[Client Co] (contract) | [Title] | [Mon YYYY] to [Mon YYYY]
Date formatting habits that break US ATS imports
Numeric slashes like 03/04/2020. Ambiguous and easily attached to the wrong block. Spell the month or use a three-letter abbrev.
Seasons and quarters. Fall 2022 and Q1 2023 import as blank or as literal words without reliable year attachment.
Two Present jobs. Pick the primary W-2 or main contract as Present. End dates on side consulting with Month Year.
Right-column date tables in Canva or Word templates. Pretty on PDF, scrambled on import. Inline dates only.
Repeating the same range on multiple titles at one company. One employer block with internal promotions uses one start and one end, or separate blocks with non-overlapping ranges and distinct titles.
Hiding older jobs in a summary sentence. Dates in prose paragraphs rarely map to Experience fields. If the work matters, give it a full block.
Using international day-first numeric dates on US reqs. 04/03/2021 reads as April or March depending on parser defaults. Spell the month.
Stacking promotions under one date range without clarifying title changes. Split promotions into separate blocks with distinct Month Year ranges when titles changed materially. One range with three titles confuses both humans and import.
Verify dates before the next upload
Paste the posting into the free ATS checker after you fix dates. Required years-of-experience language should match what your normalized timeline supports. The checker won't fix layout, but it surfaces when must-have terms never appear in dated bullets.
Rebuild dated sections in the free resume builder if your template hides dates in tables. Export plain PDF, rerun Notepad paste, then upload once to Greenhouse or Workday.
Need a letter for the same req? Sketch it in the cover letter generator after the resume timeline matches preview. A cover letter cannot repair misread dates on the attachment.
Pair the checker with one manual pass through every Experience line. Read dates aloud with the employer name. If the sentence sounds wrong to you, the parser will trip too. Fix those lines before you trust any score.
What to do now
How to stop ATS from misreading dates on US resumes comes down to boring consistency. One Month Year pattern, inline with employer and title, Present on a single current role, no slash dates, no sidebar tables. Preview and Notepad paste should tell the same story.
Open your latest PDF tonight. Fix the worst three date lines first. Re-export, paste, upload, preview. I've watched qualified files fail years-of-experience filters because 2019 stuck to the wrong company, not because the candidate lacked tenure.
Job searching is hard enough without a timeline that lies about your work. Make the dates plain text. Let the parser do the easy part. Then move on to the next req with a file you trust.
Read more
Frequently asked questions
Month Year spelled out or abbreviated without a period, on the same line as employer and title. Example: Mar 2021 to Aug 2024 or March 2021 to August 2024. Use Present for current roles. Avoid numeric-only strings like 03/21 or 3/2021 that parsers can read as day/month or attach to the wrong job.
Mixed formats, table layouts, or dates floating in a right column often map to the nearest text block, not the job you intended. Parsers also treat footer timelines as separate employers. Rebuild single column, one pattern everywhere, employer | title | dates on one line per role, then re-upload and open preview again.
No for US corporate ATS uploads. Fall 2022 and Q3 2021 parse inconsistently. Pick the month you started or ended, or use year only when you truly lack month detail. Recruiters prefer honest Month Year over creative season labels that import as blank fields.
Keep chronological order with honest Month Year ranges. One neutral line for the gap is fine: Career break, Jan 2023 to Jun 2023, family caregiving. Do not stack overlapping ranges on the same line. Gaps fail filters less often than overlapping dates that make parsers think you held two full-time jobs at once.
Yes when the header repeats employment ranges or uses slashes. Headers should hold name and contact only. Every employment date belongs under Experience beside the matching employer. Footer timelines and icon timelines duplicate dates and confuse import order on Greenhouse and iCIMS.