Two questions get Googled before nearly every application: how long should my resume be, and how do I explain the gap. Both arrive wrapped in panic and bad advice. The honest answers are calmer than the forums suggest. A recruiter spends about 7.4 seconds on the first pass (The Ladders), so length is really a question of respecting that scan, and gaps matter far less than the silence you have built up in your head about them.
How long, really
There is no universal page-count law, but there is a strong default that maps to how resumes are actually read.
| Experience | Length | Why |
|---|---|---|
| 0–7 years | One page | Everything relevant fits; padding shows |
| 7+ years | Two pages max | Recent work weighted, old roles trimmed |
| Anyone | Never three | Past two pages, nobody is reading |
Length is not a virtue in itself. It is about the seven-second scan and what survives it. A tight one-pager that leads with results beats two pages of responsibilities every time, because the recruiter is hunting for signal and you have buried it under volume. The instinct to list every project from every job works against you. Anything older than about seven years gets compressed to two lines or cut entirely, unless it is directly relevant to the role you want now. The test for every line is simple: does this earn its space in a seven-second read? If not, it goes.
A note specific to engineers: a wall of every technology you have ever touched is not "thorough," it reads as undifferentiated. Curate to the stack the role wants. One page that screams "backend engineer who ships" outperforms two pages that whisper "person who has done many things."
The gap nobody actually cares about
Here is the part the anxiety gets wrong. Employment gaps are normal. A MyPerfectResume report found that nearly half (47%) of US workers have a career gap, and roughly one in four job seekers has a gap of twelve months or longer. You are not an anomaly. The recruiter reading your resume has one too, or hired plenty of people who did.
The mistake is not the gap. It is hiding it. A blank stretch between two dates makes a recruiter's mind fill in the worst explanation, and the evasiveness reads louder than whatever you were actually doing. So name it, in one plain line: 2024 — career break (family / travel / caregiving / upskilling). No apology, no paragraph of justification. A gap you explain in five words is a non-issue; a gap a recruiter has to reverse-engineer from a date jump is a quiet red flag.
If you did anything during it that touches your field, a course, a freelance project, an open-source contribution, a side build, name that too, briefly. It reframes the time as continued momentum rather than a stop. But even a gap with nothing job-related in it is fine when stated plainly. Confidence is what closes the topic; the recruiter takes their cue from you. Treat it as normal and they will too.
Key takeaways
- One page under seven years, two beyond, never three. Length serves the 7-second scan, not a rulebook.
- Gaps are common: 47% of US workers have one, so you are the norm, not the exception.
- Name a gap in one plain line; an explained gap is a non-issue, a mystery gap is a flag.
- Curate to the role; a tight, results-first page beats a padded one.
FAQ
Should my resume be one page or two?
One page under about seven years of experience, two beyond, and never three. Recruiters scan for roughly seven seconds, so a tight, results-first page beats padded length. Trim anything older than seven years to a line or two unless it is directly relevant.
How do I explain an employment gap?
State it in one line with the reason: "2024 — career break." Hiding it reads as evasive and invites the worst assumption. Naming it plainly closes the topic, and adding anything you learned or built during the time reframes it as momentum.
Do employment gaps hurt your chances?
Rarely, when explained. They are common, with about 47% of US workers having one, so recruiters are used to them. The damage comes from unexplained date jumps a recruiter has to decode, not from the gap itself.
Is a two-page resume ever okay for a senior engineer?
Yes. Beyond about seven years, two pages is standard, as long as the most recent and relevant work is weighted up top and older roles are compressed. The cap is two; a third page signals you have not prioritized.
Get the length and content right: run your resume through PassTheBot.