Interviewers know about anchoring bias and name-based discrimination. Recency bias is less discussed, but it affects nearly every resume review. Reviewers weight what a candidate did most recently much more heavily than what they did earlier, even when earlier experience is more directly relevant to the role.
Why recency dominates
The mechanism is cognitive, not malicious. When we read a resume top-to-bottom, the most recent role is at the top and reads first. It's vivid and specific. Older roles are further down the page, often with less detail, and read after cognitive load has already built up. We spend less time on them and weight them less.
This creates a systematic distortion. A candidate who spent six years doing highly relevant work and has spent the last year in a tangentially related role will be evaluated primarily on the last year. The six years gets a passing read, if that.
The distortion is compounded by how resumes are typically written. Candidates know their most recent role will be read most carefully, so they invest more detail there. Earlier roles often receive one or two bullet points because candidates assume reviewers won't spend much time on them. That assumption is usually correct, which means the resume format itself reinforces the recency bias that already exists in how it's being read.
Where recency bias does real damage
Career changers are the hardest hit. A candidate transitioning from engineering into product management may have spent years building the exact product intuition and systems thinking you need, but their current role title is "Senior Software Engineer." Recency bias means their resume opens on the wrong signal and may never recover.
Industry transitions are the second major case. A candidate moving from healthcare to fintech may have directly applicable analytical and regulatory experience, but their recent employer is in a different space. A reviewer pattern-matching on industry keywords will underweight experience that would read clearly as relevant to someone evaluating it against the actual role criteria.
The third case is candidates who took a deliberate pause -- a parental leave, a sabbatical, a period of caregiving. Their most recent role by date may be a brief position taken for financial reasons during a transition. That role appears first on the resume and becomes the frame through which everything else is interpreted, even when the substantive work history is entirely different.
Structured rubrics as the correction
Rubric-based evaluation corrects for recency bias structurally. When a reviewer scores each candidate against specific criteria (built production data infrastructure, managed cross-functional projects above a certain scope, etc.), they're forced to search the full resume for evidence of each criterion rather than reading top-to-bottom and forming a gestalt impression.
This doesn't require special technology. A structured scoring sheet applied manually corrects for recency bias. The friction of applying the rubric is the friction of actually reading the resume against what you care about, not just what's at the top.
AI screening has a natural advantage here when designed correctly. A system that evaluates all roles in a candidate's history against a rubric -- not just the most recent one -- applies the criteria across the entire work history by design. It doesn't have a "I just read the first section" state. The whole resume contributes to the evaluation, weighted by relevance to the criteria rather than by recency in the document.
When recency is actually the right signal
The correction for recency bias isn't to ignore recent work. For roles where current technical skills matter -- security engineering, data infrastructure, any field where the tooling changes fast -- recent experience is genuinely more relevant than what someone did five years ago. The question is whether you're weighting recency because it's actually predictive for this specific role, or because it's cognitively easy.
The rubric design step forces this question explicitly. When you're deciding what to weight, you have to consider whether recency matters for each criterion. For some criteria it does. For others -- like "has managed a cross-functional project from kickoff to delivery" -- the experience from four years ago is just as relevant as experience from last year. Making that distinction consciously is the difference between structured evaluation and recency bias dressed up as rigor.
Building the habit of reading backward
One practical change that has an immediate effect on recency bias in manual review: read the resume backward before forming a final judgment. Review the oldest relevant experience first, then work forward to the most recent. This reversal counteracts the primacy effect of the reverse-chronological format. What you read first shapes how you interpret everything that follows; reading the oldest roles first means the candidate's foundation and trajectory inform your reading of their current state rather than the other way around.
For team-level consistency, pairing this reading practice with a structured scoring sheet -- where reviewers document evidence for each criterion before forming an overall impression -- further reduces the recency effect. When a reviewer has to write down evidence for the "managed complex cross-functional projects" criterion across the full resume, they're less likely to weight the most recent project description exclusively. The structured approach forces completeness and surfaces evidence that a top-to-bottom intuitive read often buries.
