By Peter Miller · Published March 24, 2026 · Last updated: October 4, 2026
7 min read
Question first: you took nine months between roles on purpose, wrote an honest summary about it, and still see a glaring gap flag in a job portal. That sting is real, and the mechanics are simpler than the shame spiral suggests.
You're not crazy if the portal feels harsher than the recruiter on the phone. Machines don't read nuance. They read months.
The ATS isn't judging your character. It's counting months where no employer row covers the calendar. Check your resume for free and compare parsed end and start fields to the PDF you intended. You'll often find a missing end month, not a moral failing.
The sections below answer the sub-questions candidates ask once they learn gaps are date math, not essay contests.
Quick Wins
- Add end months on the job before a break, not Present by habit.
- List consulting or contract work as one employer row when it fills the calendar.
- Paste the PDF to text and count months between parsed end and start.
How parsers define a gap
Gap = next start minus prior end when no other parsed row covers those months.
Workday, Greenhouse, Lever, and similar tools build a list of jobs with Month Year boundaries. Anything uncovered reads as unemployed time for filters and recruiter sorts.
Summaries and cover letters live outside that list unless the employer pastes them into a notes field manually.
That's why two candidates with the same real-world break can show different gap length in Workday when one file dropped an end month and the other didn't.
What usually is not an ATS gap
Same-month transitions often show zero gap when end March and start April parse cleanly. A few weeks between paychecks rarely registers if months touch.
Concurrent roles are overlaps, not gaps. Two employers with overlapping ranges mean double activity, which recruiters verify rather than ignore.
Internal promotions inside one employer stay one row if dates continue under the same company name. That is continuity, not unemployment.
When the gap is a parsing mistake
Year-only dates stretch or shrink months. End 2022 and start 2024 can imply a full year hole when you left in November and started in February.
Missing end dates sometimes default to Present on an old job, which hides the real break and then snaps wrong when you edit the profile.
Omitted short roles leave phantom gaps. Deleting a three-month contract to look cleaner often backfires in Taleo imports.
Read how ATS detects stability when the issue is hop count plus gap length together.
What counts as an employment gap in ATS filters
Recruiters can set rules that hide or deprioritize profiles with more than X months between jobs. X is employer-specific; you won't see the threshold on the job ad.
Some teams sort by most recent start date, which indirectly punishes long breaks even without a formal filter.
Contract-heavy careers can show micro-gaps between gigs that humans understand but machines still count unless dates touch or you group clients under one header.
Education blocks only shrink the gap when school dates parse as covering the same months. A degree line with graduation year alone will not bridge a missing employment year in most corporate imports.
Where humans still matter
In Lever I've moved candidates forward after a long gap because the parsed timeline was finally clean and the recent role matched the req, even when a filter would have hidden them.
Humans read context in screens and notes. Machines read months. Your job is to make months honest and parsing accurate so the human argument is about fit, not whether you worked in 2021 at all.
For narrative support without confusing parsers, see why career gaps are not always bad from the recruiter psychology side, not the date math side.
Parsing mistakes that inflate gaps
Leaving the end date blank on an old job while you list a new start date creates a phantom break that never existed on your calendar.
Using Present on two jobs at once without labeling part-time work makes overlap noise, then gap confusion when you finally close one end date.
Practical moves on the resume
Add Month Year on every role end, including internships you still list.
Before: 2021 to 2023 on job one and 2024 to Present on job two with no months shown.
After: Nov 2021 to Jul 2023, then Aug 2023 to Present so the parser sees a single missing month, not a year hole.
If you consulted during a search, one employer line beats six silent months.
Before: blank experience between Mar 2023 and Jan 2024 with explanation only in summary text.
After: Independent Consultant · Mar 2023 to Jan 2024 with two bullets on client deliverables.
Copy-paste: gap check line
Prior role end: Aug 2023
Next role start: Sep 2023
If text view shows a year between them, fix months before you apply.
Optional one-line leave entries are for human clarity; they do not erase gap math but stop sideways questions about blank years.
Verify the timeline you submit
Upload the PDF you will use on the application and read gap length between imported jobs. Fix dates before you spend an hour on keyword density.
Score your job match once the experience block reflects real months, so match scores attach to the right employers.
Gaps are calendar math
What counts as an employment gap in ATS is uncovered time between parsed jobs. Explain your story in the screen, but fix the dates on the page first. You'll argue about fit instead of fighting a phantom twelve-month hole.
A short note can still help humans after the dates are clean. Draft it in the cover letter generator without repeating dates that contradict the resume block.
Frequently asked questions
Cover letters are usually a separate document in the packet. Gap logic on the profile view comes from parsed experience dates. A thoughtful paragraph helps humans in interview, but it does not subtract months from the timeline the system calculated.
If education is parsed with start and end dates that cover the months between jobs, some views show continuous activity. If school dates are missing or only the degree year appears, the experience timeline can still show a hole between the last job end and the next start.
Overlaps usually signal two active employers, not a gap. The risk is the opposite: recruiters question full-time overlap unless one role is labeled part-time or contract. Fix labels before you worry about gap length.
You can add a single line with honest dates if you want humans to see the window, such as Family Care Leave with Month Year to Month Year. Parsers still treat it as another row, not as erasing the gap math. Keep it truthful and short.