11 min read
Recency weight lands when your top employer block parses with Month Year dates on the title line and a posting keyword in bullet one. If the parser drops your end date, misreads a gap, or stores Skills as a phantom job, older roles can look current and your latest proof never pairs with the search. That's how qualified files lose screens before a human opens them.
Check your resume for free with the posting pasted in. You'll often see green hits on Skills while Experience dates scramble in plain text. Don't mirror keywords until the timeline's clean.
You're not here for a lecture on why experience matters. You're here because your file looks fine in Word and falls apart after upload. Job searching is already draining enough without a silent date parse rewriting your career. The sections below show what parsers actually read, which exceptions are real, and what to change tonight.
Open your exported PDF, select all, paste into Notepad. If your current title isn't the first employer line with a clean end date or Present beside it, don't tweak keywords yet. You'll waste an hour on Skills while the timeline stays broken.
Quick Wins
- Put Month Year dates on the same line as title and employer for your current role.
- Move the posting's top keyword into bullet one under that employer, not Skills alone.
- Paste the export to plain text and confirm Present or an end date sits on the right line.
- Label any gap year with dated freelance, contract, or coursework bullets.
How ATS interprets recency in US resumes (and why it breaks)
US corporate hiring runs through parsers in Workday, Greenhouse, Lever, Taleo, and iCIMS before a recruiter skims six lines. Those systems don't read your file like a designer laid it out. They strip text, pair lines with neighbors, and store employer blocks in upload order. Recency is whatever dates attach to the first Experience entries the parser could label.
The pattern that passes: Job Title, Company, March 2022 to Present on one line, then bullets where bullet one repeats a posting must-have you used in that role. The parser ties keywords to the date range beside them. Skills listed without dates float outside that pairing.
When dates sit on a separate line below the company, or hide inside a right-aligned column, parsers often glue the wrong years to the wrong title. A 2019 to 2021 block can read as current while your real 2024 role loses its end date. Recruiters searching the posting then see a timeline that doesn't match your interview story.
Gaps make it worse. Two jobs with clean dates and a blank year between them sometimes collapse into one long stint in plain text. I've passed on files in Greenhouse where the only issue was a sidebar that trapped dates away from titles, so the system stored a 2018 employer as active while the real current role sat orphaned in Skills.
Functional layouts that lead with skills and bury dates make recency nearly invisible. Chronological Experience with newest job first is boring on purpose. Boring parses. Fancy doesn't.
Keyword recency is separate from job recency but feels the same in a search. Python in bullet one under a 2025 employer reads as active use. Python only in Skills with no dated bullet reads like a course you took years ago. Recruiters ctrl-f the posting against Experience first, not the skills rail.
Read resume keyword placement: skills vs experience when you're deciding where to park tools after you fix dates. A perfect timeline with keywords only at the bottom still loses to a messy timeline where bullet one already names the lever.
And if uploads keep failing before anyone reads bullet two, pair this page with resume rejected by ATS to separate layout failure from a true keyword gap.
What to do now: rebuild your top employer block
Work top down. Your current or most recent role is the recency signal every search leans on. Fix that block before you polish jobs from 2016.
Step 1: Stack title, company, and dates on one line
Use Month Year consistently. Same pattern on every job. No text boxes, no icons, no second column holding years.
Before: Acme Corp on line one, Senior Analyst on line two, 2022 to Present right-aligned in a margin column.
After: Senior Analyst, Acme Corp, March 2022 to Present on one line in the main column.
Step 2: Put the posting keyword in bullet one
Open the req. Circle the top tool or method. Rewrite bullet one under your current employer so the first eight words carry that term with scope you can defend.
Before: Responsible for reporting and stakeholder updates.
After: Built weekly pipeline dashboards in Looker for 28 enterprise AEs; cut forecast variance on deals above $50K in H1 2025.
Step 3: Date any gap with honest proof
Contract, freelance, caregiving, bootcamp, or certification study all count when you name dates and output. Two bullets beat a silent hole.
Before: Analyst role ends December 2022, next employer starts January 2024, nothing between.
After: Independent Consultant, Self-employed, January 2023 to December 2023, with bullets for two clients, tools, and deliverables.
Before/after: marketing manager recency fix
Before: SEO, Google Analytics, and HubSpot listed in Skills. Experience bullets say managed campaigns with no years beside tools.
After: Growth Marketing Manager, SaaS Co, June 2023 to Present, bullet one: Owned SEO content roadmap in HubSpot; lifted organic signups 14% in Q2 2025 with GA4 funnel tracking across 3 product lines.
Before/after: software engineer recency fix
Before: React and TypeScript in Skills. Most recent job title parses, but bullets describe a 2019 stack because older roles were copied forward.
After: Software Engineer, Fintech Inc, April 2024 to Present, bullet one: Shipped checkout UI in React and TypeScript on Next.js; cut client-side errors 22% after migrating auth flows in Q1 2025.
Before/after: operations lead with overlapping contract
Before: Full-time employer and a six-month contract stacked without dates, so the parser merged both into one block.
After: Two separate stacks: Operations Lead, Retail Co, January 2023 to Present, then Contract Warehouse Analyst, 3PL Client, July 2024 to December 2024, each with Month Year on the title line.
Copy-paste employer line template
Copy-paste this into Word for each role and replace bracketed lines. Keep one column. No tables.
[Job Title], [Company Name], [Month Year] to [Month Year or Present]
• [Verb] [posting keyword or tool] [scope]; [outcome with number you can defend].
• [Second lever tied to same employer dates].
• [Optional third bullet for depth].
Step 4: Trim the tail without hiding your story
Roles older than ten to fifteen years can shrink to one line with years only if space is tight. Never drop months on your current job. Never list Present on two employers at once unless you truly hold both and label hours in a cover letter when asked.
Multiple promotions at one company can stack as separate title lines with shared employer and distinct date ranges. That reads as progression parsers can sort. One blob that says various roles 2018 to 2023 does not.
Step 5: Plain-text and export
Select all, copy, paste into Notepad. Your current title should appear before older employers. Dates should sit on the same lines as titles, not orphaned at the bottom of the paste. Export DOCX from Word, then PDF from that same file when the portal allows.
Before: Canva resume with a timeline graphic and icons for each job.
After: Single-column Word file with the template above and bullets under the correct employer.
Step 6: Re-run the posting match on the fixed block
After dates parse, mirror remaining must-haves in bullet two and three under the same employer. Do not chase every synonym in Skills until Experience carries the dated proof recruiters expect on a first skim.
Edge case: you're still employed but the req wants confidential client work named generically. Keep real dates and scope; describe the client as Fortune 500 healthcare or Series B fintech when NDAs apply. Edge case: you were promoted in place last month. Split title lines with Month Year boundaries instead of one vague Present span across three different roles.
Exceptions: when the usual recency rules bend
Career change with a recent bootcamp or degree. Education can sit above Experience when the credential is the main proof and graduation is within the last two years. Still add Month Year on the program line and one project bullet with tools that match the posting.
Returning after a long gap. A dated volunteer or contract block between jobs beats pretending the gap doesn't exist. Recruiters notice holes in interviews anyway. Parsers handle labeled gaps more cleanly than mystery whitespace.
Concurrent part-time roles. Two Present lines are allowed when both are real. Put the role that matches the posting first. Note part-time in the title line if hours matter for the story.
Senior candidates with deep history. Two pages is fine when every line is dated proof. Recency still lives in page one. Trim ancient jobs to titles and years so your 2024 block stays above the fold in plain text.
Military or federal translation. MOS and series numbers belong in bullets with civilian equivalents in parentheses when the posting uses corporate language. Dates should still be Month Year on the title line after you convert to a standard Experience header.
Academic CV norms. Faculty postings may want publications with years in a separate section. Corporate US reqs still want a chronological Experience stack with recency on page one. Match the portal label, not a generic template you used in grad school.
Edge case: the posting asks for ten years of SaaS experience but your SaaS stint started in 2020. Lead with dated SaaS bullets and let older non-SaaS roles shrink. Don't invent earlier SaaS titles. Edge case: you left a toxic job without a new line yet. Use end Month Year on the old role and a short Consulting or Career Sabbatical block with dates if you did real project work while searching.
Edge case: company acquisition renamed your employer. One stack with a note Acme Corp, now part of BigCo, with continuous dates parses better than two half entries with a fake job change.
Parse before you keyword-stuff
Paste the posting into Score your job match after you fix the top employer line. You're checking whether must-haves moved from Skills into dated bullets, not chasing a perfect percentage.
Run a free ATS check on the exported PDF and read the plain-text preview. If dates detach from titles, fix stacks before you upload to Workday or Greenhouse again. When the portal also asks for a letter, generate a cover letter that cites the same dated proof from bullet one. Mismatched timelines between letter and resume trigger fast screens.
Make the current role unmistakable
How ATS interprets recency in US resumes comes down to dated employer stacks, not clever layout. Month Year on the title line, keyword in bullet one, honest gaps labeled, plain text that puts your latest role first. That's the file recruiters can search without guessing your timeline.
Open your current job block tonight. Fix the date line. Rewrite bullet one with the posting's top term. Paste to Notepad. Run a free check. This won't fix applying to roles where you're missing core scope. It stops qualified people from losing screens because a parser thought a 2019 job was still active.
Save a screenshot of your plain-text paste beside the posting must-have you matched in bullet one. When a recruiter calls, you'll cite the same dated line without digging through old exports.
When you're applying to multiple similar reqs this week, keep one master timeline and swap bullet one per posting. Same dates, different keyword in the first eight words. Ten minutes per apply on the top block beats an hour polishing a summary recruiters skip.
Read more
Frequently asked questions
Most US corporate parsers read employer blocks top to bottom and attach dates to the title line they sit beside. When your current role parses with Month Year dates and a posting keyword in bullet one, that block reads as active proof. When dates drop off or land on the wrong line, the system may treat an older employer as current or skip your gap entirely. Recruiters then ctrl-f the posting against a timeline that does not match your real career.
Month Year on the same line as job title and employer is the safest pattern: Senior Analyst, Acme Corp, March 2022 to Present. Avoid seasons, quarters only, or year-only ranges when you can add months. Present or Current is fine for an active role. Keep the same format on every block so Workday, Greenhouse, Lever, and Taleo do not split one job into two phantom entries.
Do not leave a silent hole between dated jobs if you did contract, freelance, caregiving, or coursework during the gap. Add a labeled line with Month Year dates and two bullets of real output. A gap with no dated activity forces recruiters to guess, and parsers sometimes stitch the job above the gap to the job below it. Honest dates with proof beat a mystery timeline every time.
Skills without a dated employer line rarely carry the same weight as the same term inside bullet one under your current job. Posting searches often pair keywords with the most recent Experience block the parser could read. Park must-have tools in the bullet where you used them last, then echo them in Skills if you have room. A Skills cloud alone does not prove you used the tool recently.
Keep the last ten to fifteen years in full with Month Year dates and trim earlier roles to one line each or drop them when they no longer support the posting. Recency signals live in your top one or two employer blocks. A long tail of undated early jobs can push your current title below the fold in plain text and bury the keyword match recruiters need on page one.