What the field experiment measured
In their February 2017 San Francisco Fed summary, David Neumark, Ian Burn and Patrick Button describe more than 40,000 fictional applications sent to over 13,000 openings. The age bands were 29–31, 49–51 and 64–66. They studied administrative assistant/secretarial positions using female applicants, janitor/security positions using male applicants, and retail sales using both. These selected occupations do not represent every labor market.
| Observation | Population or outcome | What it does not establish |
|---|---|---|
| 7.6% versus 14.4% callbacks; a 47% relative difference | Women aged 64–66 versus 29–31 applying to administrative jobs in this experiment | A universal penalty for older applicants, a job-offer rate or an individual rejection cause |
| Differences varied across groups | Male-applicant findings were less consistent; some differences were not statistically significant | An identical effect across genders and occupations |
| Constructed applicant profiles were compared | The outcome was an interview callback | A test of changing one real person's resume or of employer AI software |
The published study reports evidence of age discrimination, especially against older women, while explaining design limitations in comparisons between age groups. It does not show that omitting graduation dates, limiting career history or choosing a different email provider improves outcomes. Do not treat every age-related detail as a tested cause of rejection.
Optional resume choices, without an age-proofing promise
Decide what belongs in an application by the role and the employer’s instructions. An older project can be essential evidence; a recent but unrelated task may need less space. Use the same relevance standard across your history instead of removing material automatically after a fixed number of years.
| Choice | When it may be useful | Accuracy check |
|---|---|---|
| Omit a graduation year from the resume | The qualification matters, while its date adds little and is not requested | Keep the credential name and completion status accurate; provide dates on a form that requests them. |
| Condense earlier experience | Its details repeat evidence established in more relevant roles | Retain important qualifications and distinguish separate jobs; do not change employment dates. |
| Keep an older role in detail | It demonstrates a specific requirement absent from recent work | Explain the relevant contribution rather than presenting an automatic history cutoff. |
| Refresh a skills list | The application needs a clearer view of tools and methods you can use | List actual capabilities. Do not add current tools you have not used. |
| Clarify an employer rename | A historic employer name needs context | Preserve the name used during employment and add an accurate clarification instead of replacing the record. |
Constructed editing example
Fictional facts: a marketing candidate has worked across print and digital campaigns and is applying for an integrated-campaign role. A summary could say “Marketing professional with 25 years of experience” or “Marketing professional coordinating print and digital campaigns.” The second version emphasizes the relevant work. Neither wording has been tested here for age bias, and the work-history dates remain accurate in both versions.
An introductory section is optional, and a centered name or an objective is not evidence of an applicant’s age. Choose readable formatting, decide how much relevant history fits, and retain a complete private chronology for application questions. Do not invent recent activity or turn an earned credential into a different qualification.
What an ATS or a fast rejection can tell you
Do not assume every applicant tracking system has the same fields, inputs or inference capabilities. A resume, application answers and other records can be processed differently by different employers. Seeing a date field—or not seeing one—does not establish the criteria used in a decision. The ATS workflow guide separates storage, extraction, search, rules and optional matching.
A quick rejection, an overnight email or silence after applying does not establish that an algorithm inferred your age. Nor does an unsuccessful application show which human reviewed it. Keep the posting, submitted documents and relevant communications if you need to ask about a decision.
Legal protection and allegations are different from study findings
The EEOC explains that the ADEA prohibits age discrimination against applicants and workers aged 40 or older in covered employment, including hiring. Coverage and the legal evaluation of a policy depend on the circumstances; a study difference is not an automatic finding about a particular employer. The EEOC provides information about contacting the agency and applicable time limits.
The Workday lawsuit guide distinguishes allegations involving screening software from court findings and procedural decisions. A lawsuit’s allegation does not establish that every tool uses the same mechanism or that the cited correspondence experiment tested that software.
Review your application on facts you can control
- ▸Read the posting’s requested qualifications, dates and application fields before selecting content.
- ▸Keep relevant seniority and specialist knowledge visible when they help explain your fit.
- ▸Check employer names, official titles, dates and credential status against your records.
- ▸Treat optional omissions as relevance decisions; answer required application questions accurately.
- ▸Review generated drafts yourself. Resume Leap does not test for employer discrimination or independently verify your history.
Resume Leap’s keyword overlap and AI assessment describe its own methods. They do not establish whether a hiring system will use age-related information, whether a particular edit reduces bias or whether you will receive an interview.