Skip to content
Job Search· QueryQuarry Team

Should You Put Dates on Your Resume? What They Reveal

Illustration of a pickaxe striking a blank document embedded in a rock wall surrounded by small icons of a clock, folder, person, house, and arrows.

Dates on your resume answer a question nobody should be asking. A graduation year is simple arithmetic away from your age; two decades of employment dates tell the same story twice. And age is only the loudest of the signals a standard resume volunteers — your name, your address, even your photo in some markets, all feed judgments that have nothing to do with whether you can do the work. Before deciding what to trim, it's worth being precise about what each field actually leaks, and what it costs you.

What the Research Actually Measured

This isn't a hypothetical-bias conversation; it's one of the most replicated findings in labor economics. In the landmark field experiment, researchers sent thousands of otherwise-identical resumes to real job postings and found that white-sounding names received about 50% more callbacks than identical resumes with Black-sounding names. A decade later, a study of "whitened" resumes found that applicants who scrubbed racial signals roughly doubled their callback rates — including at employers who advertised themselves as pro-diversity.

Age tells the same story. In one of the largest resume field experiments ever run — more than 40,000 applications — callback rates were markedly lower for older applicants, especially older women, despite identical qualifications. The Age Discrimination in Employment Act has protected workers 40 and over since 1967; the callback data shows how much screening happens before any law can see it.

The mechanism is mundane. Nobody convenes a meeting to reject older candidates. A screener skims 200 resumes, arithmetic happens ("graduated 1998, so..."), and a pile forms. The signal does the discriminating on its own.

What Each Field Leaks

  • Graduation years: your age, to within a year or two. The single highest-leak, lowest-value data point on the page — no hiring decision improves by knowing it.
  • Employment dates: your age again (a career that starts in 2003 says plenty), plus gap-hunting material. As we've written before, most hiring managers admit they have no framework for evaluating employment gaps — the dates invite scrutiny nobody knows how to do well.
  • Your name: race and gender inference, per the callback studies above.
  • Street address: commute-distance screening and neighborhood inference — a socioeconomic signal dressed up as logistics.
  • Photos: every bias at once. Standard advice in the US is to omit them, and it's correct.

The Trap: Stripping Signals Yourself Can Backfire

Here's the honest tension. If you simply delete dates from a traditional resume, many screeners read the absence as evasion — "what are they hiding?" — and the resume can score worse, not better. Recruiters are trained to flag undated work history. Removing your address helps less when the first phone screen asks where you're based. You can whiten a name, and the research shows it works, which is its own indictment — the fix that works best is the one nobody should have to perform.

That's the trap in most resume advice: it treats a structural problem as a formatting problem. The individual candidate can only choose which risk to carry — leak the signal, or look evasive for hiding it. Both options tax the candidate, and neither fixes the screen.

The Infrastructure Fix

The signals leak because the document that proves your experience and the document that identifies you are the same piece of paper. They don't have to be. This is one of the reasons we built QueryQuarry the way we did: recruiters evaluate a structured, anonymous profile — skills, seniority, what you actually did — while the platform withholds the rest by default. Your name is scrubbed from every field recruiters see. Education appears without years. Employment dates are sealed; recruiters see a total years-of-experience figure you control, not the calendar math behind it. Identity is exchanged only when you respond to a real offer. The practical upshot for your resume is covered in our candidate docs: several things standard advice agonizes over, you can simply leave off — and uploading one is free and takes about a minute.

Whether or not you ever use our corpus, the principle travels: the more evaluation happens on evidence of capability rather than on demographic signals riding along with it, the more the callback data starts looking like the qualification data. Forty years of field experiments say the resume, as a format, can't deliver that on its own.

Frequently asked questions

Should you put your graduation year on your resume?
In traditional applications it's expected for recent grads but optional after a few years of experience — and omitting it is the standard defense against age screening. Field-experiment data shows callback rates drop for older applicants with identical qualifications, and graduation year is the easiest age signal to remove.
Is it OK to leave employment dates off a resume?
Risky in traditional channels — screeners often read missing dates as hiding something, so most advisors recommend keeping at least years. That's the structural trap the post describes: leak your age or look evasive — a choice platforms can remove by withholding dates while showing total experience.
Can employers really tell your age from your resume?
Yes — graduation year plus the start of your work history dates your age within a year or two, no birthday required. That arithmetic is why age-bias field experiments could measure lower callbacks for older applicants using resumes alone.