Write dates as month and year: Mar 2023 – Present. Month-year is what ATS parsers expect, what recruiters trust, and what prevents a false gap: year-only dates make a job ending in January and one starting in November look continuous, and some screeners read years-only as gap-hiding. Consistency across every role matters as much as the format.
Parsers build a timeline from your dates, and month-year strings — Jan 2022, 03/2022, March 2022 — map cleanly onto it. Recruiters read the same timeline for tenure math: how long you actually held each role, whether you have a pattern of short stays, whether the story is continuous. Month-year answers those questions precisely, which is exactly why the format earns trust.
Years-only compresses information in a way experienced screeners have learned to distrust. 2021 – 2023 could be 36 months or 14. Used on every role it reads as a stylistic choice at best and gap camouflage at worst, and background verification will surface the real months anyway — creating a mismatch you then explain from a defensive position. If you have gaps, the stronger play is month-year dates plus a one-line explanation where needed.
Pick one rendering and use it everywhere: Mar 2023, March 2023, or 03/2023 all parse, but mixing them looks careless and can confuse cruder parsers. Use an en dash or hyphen with spaces between dates, and Present for a current role — not now, not ongoing, not today. Right-aligning dates in a simple tab layout is fine; placing them in a separate table column can scramble reading order in older parsers.
Education dates need only the graduation year, and dropping even that is standard past 15 years to blunt age inference. Certifications carry the year earned plus expiry where relevant. The precision hierarchy is deliberate: work history needs months because tenure is scrutinized; credentials need only existence and rough recency.
Month-year dates will expose real gaps — that is not a reason to blur them. A gap over three months gets one plain line where it falls: career break for caregiving, 2023, or sabbatical, structured study. Screeners are used to gaps; what they penalize is the feeling of concealment, and precise dates plus a calm label removes it entirely.
Overlapping dates from concurrent roles — freelancing alongside a job, two part-time positions — are fine and parse fine, but make each entry self-explanatory so the overlap reads as deliberate. Very short stints attract questions regardless of format: a three-month role you would rather not defend can sometimes be omitted entirely, but if listed, give it honest months. The one unforgivable move is inventing dates; employment verification checks exactly this field and nothing else so reliably.
You can, but experienced screeners read year-only dating as potential gap camouflage, and verification surfaces real months anyway. Month-year plus a short explanation of any gap is stronger than blurring the timeline.
Start month-year, en dash, Present: Mar 2023 – Present. Every parser and recruiter reads it instantly. Update it the day you leave — a stale Present discovered in an interview is an avoidable credibility scratch.
Gaps under about three months read as normal transition time and need nothing. Longer ones deserve one matter-of-fact line — caregiving, study, layoff, relocation — placed in the timeline where they occur, not buried or explained defensively.
The free scorer rebuilds your employment timeline the way an ATS does — see what gaps and date problems a machine finds in seconds.
