Should a resume be one page?

"One page" is the most repeated piece of resume advice there is, and the most carelessly repeated. It is a real convention with real force in some places and none at all in others, and the honest answer depends on who is reading. Here is where the rule came from, where it genuinely applies, and what to do when your career does not fit.

Where does the one-page rule come from?

It is not an ATS constraint. Parsers are indifferent to page count, and no system rejects a file for having two.

It comes from the reading. A recruiter working a requisition looks at a resume for something between six and thirty seconds on the first pass. In that window they are checking a handful of things: roughly the right seniority, roughly the right domain, no unexplained gaps, some evidence you have shipped. A second page does not get read on that pass — at best it gets read later, if the first page earned it.

So the rule is really a claim about editing, not about paper: the most important third of your career should be findable in ten seconds. One page enforces that by removing the option of burying it.

Does it apply at Google, Apple and Meta?

For most engineering candidates, yes — and it is stated openly. Google's own hiring guidance has recommended roughly one page per ten years of experience. Recruiters at large technology companies say some version of the same thing constantly, and interview-preparation advice aimed at those companies, including Cracking the Coding Interview, has pushed one page for years.

The reasoning is volume. A popular requisition at a large company can draw hundreds of applications, and a referral round can draw thousands across the organisation. Under that load brevity is not a stylistic preference, it is the only way the pipeline functions.

There is a real exception even here. Research roles — anything where a publication record is part of the qualification — expect a CV, and a CV is as long as your publication list. If you are applying to a research organisation rather than a product engineering team, the convention is different and nobody will hold three pages against you.

When is more than one page correct?

Being specific about this matters, because "always one page" is bad advice too.

• Academic and research positions. A CV is a record, not a pitch. Publications, grants, teaching and talks all belong on it.
• Government, defence and some regulated industries. Several ask for exhaustive employment history, sometimes in a prescribed format with unexplained gaps accounted for. Follow their instructions, not this convention.
• Senior leadership outside engineering. At executive level resumes get longer as a norm; the reader is a search consultant, not a screener.
• Fifteen-plus years of genuinely distinct work. Two pages are commonly accepted, and in parts of Europe — Germany and the Netherlands especially — a two-page CV is ordinary for experienced hires.
• When a posting explicitly asks for more. Always follow the posting.

Notice what is not on that list: "I have six years of experience and a lot to say." Six years fits on one page. So does twelve, usually, once you stop listing everything you have ever touched.

How do you actually fit a career onto one page?

The instinct is to shrink the type. Do that last, not first.

Cut the sections that carry no information. An objective saying you are a motivated professional seeking a challenging role can go. So can "References available on request", your full postal address, your date of birth, a photo, and — after your first couple of jobs — your school.

Cut early jobs to a single line. Your first internship needs a title, an employer and a date range. It does not need three bullets. Seniority is communicated by the shape of the page as much as by its content: a lot of detail recently and little detail long ago reads as progression.

Cut the skills inventory. A list of forty technologies is not evidence; it is a claim you would struggle to defend in all forty. Twelve you can discuss, grouped, is stronger and shorter.

Merge repeated roles. Three promotions at one employer is one entry with a list of titles and dates, not three entries with three sets of bullets about the same system.

Then rewrite the bullets. This is where the space actually is. "Was responsible for the maintenance and improvement of the payment processing pipeline, working closely with stakeholders to identify opportunities for optimisation" is twenty-eight words that say nothing measurable. "Cut payment pipeline p99 latency from 1.2s to 340ms; absorbed Black Friday at 4× volume with no incidents" is twenty words that say what you did and how big it was. Ruthless bullet editing typically recovers a third of a page, and it improves the resume independently of length.

Only then adjust the typography. That is the part most people cannot do in a word processor, which brings us to the next section.

Should you keep a longer version too?

Yes, and it costs nothing. Keep a full record of everything — every role, every project, every talk — in a private document you never send. It is the source you edit down from, it means you never have to reconstruct a job from memory two years later, and it is what you want open when a form demands exhaustive history or an interviewer asks about something from 2019.

What you send is a cut of that record, aimed at one reader. The private version is for you; the one page is for them.

Why typesetting decides whether it fits

Two documents with identical words can differ by fifteen or twenty per cent in length, purely from how they are set. The variables are the typeface's width at a given size, the leading between lines, the measure, the margins, and — most of all — how well the system breaks lines.

This is where a proper typesetting system earns its place. LaTeX breaks paragraphs by optimising the whole paragraph at once rather than filling one line at a time and moving on, so it produces fewer half-empty lines and fewer awkward hyphenations. Across a full page of bullets that difference is measured in lines, and lines are exactly what you are short of. The same content set well fits where set badly it spills.

That is the whole design of this library. Every template is one page by construction, and they differ in how much they hold: Interview serif is the airiest and holds the least, Compact sans is the densest and holds roughly a third more on the same sheet, and Signal sits between them with tightened leading and a two-column skills block. If the page is comfortable, pick for the reader. If you are two bullets over, change the plate before you cut the bullets.

Either way, the useful move is to stop estimating. Put your real history in, compile it, and look at the page.

The short version

• One page is a rule about editing, not about paper.
• For product engineering roles at large technology companies, treat it as binding.
• For research, academia, government and some European markets, it is not.
• Fit it by cutting weak content first, merging roles second, rewriting bullets third, and changing the typography last — but do change the typography, since it is worth more lines than people expect.