Search this question and the answers converge on a span of years, ten to fifteen being the figure repeated most often, to the point that one of the articles ranking for it puts the rule in its title. It is a reasonable default and it is answering a slightly different question than the one being asked. A fixed span assumes every history has the same shape, and the histories that send people looking for this answer are exactly the ones that do not: the long single tenure, the career change, the gap, the early role that is still the most relevant thing on the page.
Your dates are display text, not score input
I can speak precisely about one scoring system, ours, and what it does with your dates is nothing.
A parsed resume here carries a start and an end string on every role and every degree. Both are read in exactly one place in the codebase, the renderer that lays the document back out, where they are joined with a dash and printed. No scoring path touches either field.
The score itself is a weighted blend of six things: keyword and skill coverage, experience relevance, impact and quantification, action-verb strength, seniority alignment, and format hygiene. There is no dimension for the age of your history and no term for the number of years it spans. Experience relevance is the one you would expect to punish an old role, and the instruction that judges it asks how well your roles and bullets align with the posting's core responsibilities. Alignment, not recency. A role from a dozen years ago that matches what the job asks for is treated the same as one from last year.
So cutting a role to land under a year count buys nothing on our scorer, and costs whatever relevance that role carried. Other systems are not obliged to behave the same way, which is the honest caveat: you cannot inspect them, so writing to an imagined rule about years is a bet you have no way to check.
The reason people actually ask
Most people asking this are not asking about parsers. They are asking whether a date will get them screened out for being older, and whether dropping the early roles or the graduation year helps.
The legal position in the United States is worth knowing exactly rather than roughly. The Age Discrimination in Employment Act protects applicants as well as employees who are 40 or older, and it applies to private employers with 20 or more employees, to federal, state and local government, and to employment agencies and labor organizations. It covers hiring, not only what happens once you are hired. What it does not do is require anyone to leave dates off a resume, or make a date on a resume a problem in itself. The EEOC also notes that asking an applicant's age is not flatly prohibited, but that such requests are closely scrutinised because they may deter older applicants or indicate intent to discriminate.
Two things follow. The protection is real but it is enforced after the fact, through a charge, which is a slow remedy for a screening decision you never saw happen. And that is an argument for controlling what you can control on the page, not for concealment: a history that begins abruptly in the middle with nothing said about it reads as a gap, and a reader who notices the omission has been handed the very thought you were trying to avoid.
Set the cutoff per block, not per resume
- The recent work, in full. Bullets, detail, figures where you have them. This is the part a reader is deciding on.
- Anything older the posting asks for, kept. If the job names a system you last touched fourteen years ago and nobody since, that role is the strongest thing you have, not the oldest. Keep it and say what you did.
- Anything older the posting does not ask for, reduced to a line. Title, employer, dates. Continuity preserved, almost no space spent.
- Roles so old and so unrelated that even a line misleads, folded up. A single "Earlier experience" line naming the field and the period covers them without listing four employers.
The block-level test is the one that also decides page count: would a person hiring for this specific job be worse off for not reading this block? If the answer is no, it goes, whatever its date. How long should a resume be covers what that does to your length, which is usually less than people expect.
Working out which old roles the posting still wants
Read the posting for this one purpose and it goes quickly. Paste it into our resume keyword generator to get the terms the job actually names, then go down your history and mark which roles touch any of them. The roles touching none are your candidates for compression, and they will not all be the oldest. A recent position in an adjacent field routinely fails that test where something from three employers back passes it.
Once the cuts are made, run the result through our ATS resume checker to confirm the file still parses and the sections you kept are still being read as sections. Trimming a history usually means restructuring the document, and restructuring is where formatting quietly breaks.
A span of years is a summary of a decision, not the decision. Make it per block against the posting in front of you and the number falls out by itself, which is why the same person can honestly arrive at a different cutoff for two different applications. For the editing pass that follows, tailoring a resume to a job description covers what to change and what to leave alone.