Mobley v. Workday: 3 Resume Markers That Leak Your Age

If you got a Workday rejection at 1:50 AM the same night you applied, you already know the feeling that Derek Mobley turned into a federal case. The docket in Mobley v. Workday is now on a track to a March 9, 2027 class-certification hearing, and the record names the exact resume signals plaintiffs say Workday's AI uses to infer applicant age. This piece translates those allegations into three specific rewrites you can make tonight.

What the Mobley docket actually says about your resume

The case is a live disparate-impact challenge under the ADEA (Age Discrimination in Employment Act), and it names three resume data points as the alleged mechanism of harm: employment gaps, tenure length, and skills that correlate with age. That is the framing to use when you edit your own CV.

Key facts from the record:

• Case number 3:23-cv-00770, N.D. Cal., before Judge Rita F. Lin.
• On March 6, 2026, the court refused to dismiss the ADEA claims, ruling the statute reaches job applicants, not just employees.
• Workday disclosed that its tools rejected applications numbering in the billions during the opt-in period. One legal-tech analysis puts the figure near 1.1 billion.
• Roughly 14,000 people opted into the collective by the March 7, 2026 deadline.
• Class certification motion is due September 14, 2026; opposition November 10, 2026; hearing March 9, 2027.
• The court's own certification order acknowledged the collective could number in the "hundreds of millions" if Workday's own speculation is right.

The "1:50 AM rejection" is not just a viral anecdote. The court leaned on the fact that Mobley received rejections outside business hours and within an hour of submitting, writing that "the sheer number of rejections and the timing of those decisions" supported a plausible inference of algorithmic screening on a factor other than qualifications. If you are still applying through Workday, screenshot every timestamp. That is the same evidence class that survived a motion to dismiss.

One important caveat: the March 7, 2026 opt-in deadline has passed. You cannot join Mobley now. Any injunctive relief the court eventually orders will reshape screening for everyone, but until then, rewriting your resume is defense, not remedy.

Marker 1: The graduation year, and why hiding it is only table stakes

Removing your graduation year is now the minimum, not the edge. Career experts have told applicants over 40 to strip the year for a decade, and CNBC's consensus advice is to cut it between ages 40 and 50, so a bare "B.S., Computer Science, University of Michigan" now reads as generic rather than evasive, even when a Gen-Z cohort submits clean 2022 dates next to yours.

Ranked hierarchy of what to strip from the education block:

1. Graduation year. Between ages 40 and 50, the consensus (CNBC, AARP) is to cut it.
2. High school. If it is still there, remove it.
3. Early certifications with dates. A 2003 MCSE line date-stamps you even if the degree line does not.
4. GPA and honors from more than 10 years ago. Keep the honor, drop the year.
5. Study-abroad and undergrad clubs. Nobody hiring for a senior role reads them; they age you.

The non-obvious move: keep the school, cut everything around it. Human recruiters glance at the education line for prestige and to confirm the degree exists. ATS parsers often skip the education block entirely for senior roles, which means the graduation-year gambit is more about the human review step than the algorithm. That is fine. It still matters. It is just not where the plaintiffs' theory says the model is scoring you.

Marker 2: Tenure length and the 10-year cutoff

Trim to the last 10 years of work history and cap detailed bullets at the last 5 to 7 years. Older roles compress to a single "Earlier Experience" line with company and title only.

Jobscan's baseline advice is the same: focus on the last 5 to 7 years, do not go further back than 7 to 10 total. The reason is not that older work is worthless. It is that every extra year of chronology gives an inference model one more feature to correlate with age. A resume that starts in 2014 tells a screener nothing about whether you graduated in 1988 or 2010.

Practical tenure rewrites:

• Compress pre-2016 roles into a single line. "Earlier: Senior Engineer, IBM; Engineer, Sun Microsystems" is one row, no dates.
• Drop the first job. If your first title was "Junior" or "Associate," the fact that you had a junior role at all reads as chronologically early.
• Reframe long tenures. A 12-year stint at one employer becomes two entries: "Director, 2019-present" and "Senior Manager, 2013-2019." Same company, two rows, two role scopes. Reads as growth, not stasis.
• Kill the objective and the "20+ years of experience" summary. Volunteering your year count is the algorithmic version of yelling your birthday across the office.

The gap problem is bigger than the age problem

The plaintiffs' mechanism-of-harm theory in Mobley names employment gaps specifically: "tools which rank, evaluate, and recommend candidates produce disparate impact by penalizing data points like employment gaps, which correlate with protected characteristics such as disability-related medical leave or age."

Read that carefully. A 55-year-old with continuous employment is, on the plaintiffs' own theory, at lower algorithmic risk than a 42-year-old with a 2020-2022 caregiving gap. The defense is gap-framing:

• Register an LLC and label the gap "Independent Consultant, [LLC Name]" with two or three real project bullets.
• If you did contract work, list it as one role with the contract portfolio underneath, not as separate 3-month jobs.
• If you took a year to care for a parent, "Family Sabbatical" is honest and readable. It is also, per current EEOC guidance, protected context you do not owe an employer up front.

Rewriting every gap and every bullet against a specific posting is the exact grind that eats a weekend. It is also the work Refolk takes off you: paste the posting, get your own resume back rewritten for it, with the gap framed the way that particular employer's screener is most likely to score cleanly.

Marker 3: The dated tech stack that telegraphs 20 years in

The skills section is where the plaintiffs' theory has the most bite, because it is a structured, machine-parseable field where legacy technologies act as near-perfect proxies for career start date. Strip anything on your resume that is more indicator-of-when-you-started than indicator-of-what-you-can-do.

In Refolk's index of professional profiles (US engineers and developers, queried September 2026), the ratio of legacy to modern skills tells the story:

A candidate whose skills section leads with jQuery and COBOL sits in the intersection of two shrinking talent pools that together imply a career start somewhere between 1995 and 2003. In the same Refolk sample, 16 of 25 profiles listing COBOL had a hyperscaler (Google, Meta, or Microsoft) as a recent employer, which means listing COBOL on a mid-market application is not just an age signal but also a market-fit mismatch signal. The screener does not need to know your birthday when your stack tells it.

The dated-stack rewrite, step by step

1. List modern equivalents first. React before jQuery. Kubernetes before "Solaris administration." TypeScript before "Perl scripting."
2. Cut anything you have not touched in 3 years. If a recruiter asks about it, you will fumble. If a model sees it, it slots you into a cohort.
3. Move certifications with dates into a single "Certifications" line, no years. AWS Solutions Architect is fine. AWS Solutions Architect (2011) is a birth-year proxy.
4. Rename legacy work. "Maintained ColdFusion e-commerce platform" becomes "Modernized legacy web platform to Node.js/React." Same role, forward-looking framing.
5. Match the job posting's stack, in order. If the JD lists Go, Postgres, and gRPC in that order, your skills line does too.

Doing that once is a chore. Doing it for every one of the 40 postings you plan to hit this month is where most over-40 candidates give up and blast the same resume everywhere.

Why "just apply direct" is not a real workaround

You cannot route around Workday by targeting smaller companies. Workday serves more than 65% of the Fortune 500, over 70% of the top 50, and more than 11,000 organizations across 175 countries. Mid-market Workday deployments are common, so the "apply direct to the hiring manager" advice fails at the scale most people are searching.

What actually helps, in rough order of leverage:

• Rewrite the resume against the specific posting. Generic resumes are what the screeners are tuned to reject fastest.
• Apply through employee referrals when you can get them. Referred candidates typically bypass the top of the funnel entirely.
• Screenshot rejection timestamps. If Mobley wins injunctive relief, applicants with contemporaneous records will be in the best position.
• Diversify channels. Direct company career pages, Greenhouse-hosted postings, and non-Workday ATS are still meaningfully different funnels.

The court also ruled that Workday's HiredScore AI features are inside the collective and required Workday to identify customers using them. If a posting lands in HiredScore, the same resume-signal analysis applies, because HiredScore is what Workday bought to do exactly this kind of ranking.

The precedent that makes this real: iTutorGroup

Before Mobley there was iTutorGroup. The EEOC reached a $365,000 settlement with iTutorGroup over software configured to automatically reject applicants aged 55 or older (women) and 60 or older (men). It is the first known federal AI-hiring age enforcement action, and it establishes that automated age-based rejection is legally actionable, not just distasteful.

Mobley is the same theory at roughly 3,000 times the scale. A 2024 Resume Now survey cited in Fortune found about 90% of workers over 40 report having experienced ageism. The current wave of resume-trimming (10-year caps, dropped graduation years, LinkedIn history hidden) is a rational response to a screening layer that plaintiffs say is quietly scoring against them.

The opt-in window has closed. Your leverage now is a resume that stops feeding the model the features it uses to guess your age. Refolk drafts that resume from your real history, tailors it to the posting, and scores how well you actually fit before you burn the application. Use the case as motivation. Use the rewrites as defense.

FAQ

Should I lie about my graduation year or work history to beat an ATS?

No. Do not fabricate dates, degrees, or employers. What you can do, without lying, is omit the graduation year, compress pre-2016 roles into a single "Earlier Experience" line, and drop legacy technologies you no longer use. Every one of those edits is a truthful subset of your history, and each one removes a data point that the Mobley plaintiffs argue is being used as an age proxy.

Can I still join the Mobley v. Workday collective?

No. The opt-in deadline was March 7, 2026, and roughly 14,000 people made it in. If the court certifies the class and grants injunctive relief at the March 9, 2027 hearing, the remedy would affect Workday's screening going forward for everyone. For now, treat resume rewrites as defense, not as a substitute for legal standing.

Is the "1:50 AM rejection" actually evidence, or just a meme?

It is evidence. Judge Lin's court cited the timing of Mobley's rejections (outside business hours, within an hour of submission) as part of the reason a plausible inference of algorithmic decision-making survived the motion to dismiss. Screenshot every rejection timestamp you get. Save the confirmation and the rejection side by side.

If I strip jQuery and COBOL, do I look under-experienced?

Only if you replace them with nothing. The move is to list modern equivalents first (React, TypeScript, Kubernetes) and reframe legacy work as modernization. "Migrated ColdFusion e-commerce platform to Node.js and React" tells a screener you have both the depth and the forward stack, without leading with a skill that in Refolk's index sits on 3.45 times more profiles than React and correlates strongly with a 1990s career start.