A One-Page Resume is Not Just a Constraint—It's Powerful 'Product Planning'

Whether it's game product planning or a web service, every great product is born from 'constraints'. The same goes for resumes. The real reason a one-page resume is useful is that it forces you to make ruthless decisions.

It's not because every career magically fits perfectly onto one page. Nor is it because recruiters throw away the second page on principle. The value is much simpler: the one-page constraint elevates resume writing from mere "form-filling" to fierce "editing."

If you try to include everything in your career, nothing becomes a priority.

You have to coldly ask yourself and decide: which project outcomes will capture the recruiter's eye, how to compress old history, and whether there are sentences left just because it feels like a waste to delete them. Hanjang is designed on this very pressure. The markdown source focuses on the essence of the text, the preview focuses on the printed paper, and the public link focuses solely on the 'result' without any distracting UI.

Most civilian job-seeking resumes should aim for one page. The only time spilling over to a second page is acceptable is when your recent core achievements are so overwhelming that they can change the logic of the hiring decision. If it's just to preserve your past history, compress it boldly.

The one-page rule is actually a 'priority test'

The biggest reason to stick to one page isn't because it's the unconditional right answer. It's because it serves as the most transparent indicator of how sharply focused your career story is.

The Harvard career guide views a resume as a selective summary of abilities, education, and experience tailored to the reader's needs.¹ The MIT resume guide advises choosing experiences that demonstrate the skills needed for a specific job.² Neither tells you to "keep everything."

The hidden question in a resume is always the same:

What is the core value about me that this reader needs to know first?

If the answer is blurry, the resume becomes long like an excuse. Having spent nearly 10 years in the industry and reviewing countless resumes of team members as a Project Director (PD), I've found that long, boring resumes usually share the following failure patterns:

• Giving equal weight to core and secondary roles.
• Outdated past projects shoved in just because it feels like a waste to delete them.
• Appealing the exact same skillset repeatedly across 3 or 4 different projects.
• Bullets that lengthily list "tasks" you did, instead of "outcomes" proven by numbers.
• Formatting that only shrinks the font size to forcefully fit onto one page without actually cutting content.

This isn't a matter of character count or length. It's a matter of information hierarchy.

The second page isn't the enemy. 'Equal weight' is.

Of course, two pages might be appropriate for some applicants.

Senior researchers with numerous papers, academics, medical professionals, or those with deep publishing histories will need more space. Federal applicants must follow the posting and current USAJOBS guidelines. Federal agencies only accept resumes up to two pages for that posting, and USAJOBS advises adjusting the resume to fit the posting.³

However, for most practical resumes—like those of product owners, planners, and developers—simply allocating more space to every experience never makes it more attractive.

A resume only becomes powerful when the most relevant evidence is stripped to its skeleton and becomes crystal clear. CareerOneStop, sponsored by the U.S. Department of Labor, recommends keeping resumes clean, readable, and usually within 1 to 2 pages.⁴ This range eliminates fake debates. The issue isn't whether a second page is illegal. It's whether that second page has a justifiable reason to exist.

Apply this test to yourself:

The goal isn't blindly whittling it down to one page. It is eliminating lazy whitespace and redundancy.

The first screen dictates everything

Whether it's a PDF, a web link, or a printed paper, the very top section must dictate the direction of the whole document.

This doesn't mean mindlessly stuffing keywords in. It means optimizing the first screen so the reviewer can grasp your value as quickly as possible.

• Intuitive name and contact info.
• A clear, short headline that pierces through who you are.
• The most recent, and most highly relevant core role.
• The strongest evidence data that matches your target position.
• Actual domains and performance metrics that created business impact.

NACE's career readiness competencies framework is a useful lens for choosing the evidence to place at the top. Competencies include career/self-development, communication, critical thinking, equity/inclusion, leadership, professionalism, teamwork, and technology.⁵

These core competencies appear in various forms: launching a new project, setting up and managing a global remote team, data-driven backlog optimization, or automated system migrations.

The first page must show this core evidence before the reviewer even has to look for it. If you have a second page, abandon the expectation that it will save a poor first page.

Before touching the layout, structure the story first

When a resume gets long and complex, modifying the design or formatting is the very last lever you should touch. Just like rapid prototyping, you must solidify the core logic first. Follow this sequence instead:

1. Set the target. Which company and position (e.g., Planning PD for a New Business Team) is this version aimed at?
2. Rank the evidence. Out of your many experiences, which project and bullet defends you the strongest?
3. Compress old experience. Leave only the 'signal' that you did the work, and boldly strip away the record-keeping details.
4. Remove redundant evidence. There is no need to prove the same skill three times.
5. Sharpen the bullets. Leave only your 'action', the 'context' at the time, and the 'result' in numbers.
6. Adjust the layout last. Once the content is perfect, adjust margins and density without compromising readability.

University career centers say similar things. Resumes must be clear, concise, relevant, and easy to scan.⁶ Tiny text and dense formatting directly fight the primary rule of readability.

A one-page resume that looks like nobody wants to read it can never win. Hanjang's paper preview transparently shows this trade-off before you shrink the text. If it only barely fits on one page after you've squashed it to the point of being unreadable, your planning and editing are not yet finished.

A resume doesn't need to get bloated; it needs 'Versions'

The most honest counterargument I hear about the one-page rule is this: "But I have multiple career stories to tell."

That is correct. If so, you shouldn't build one fat document, but rather build multiple versions.

If you are applying for a Head of Development or PD role, you'll need a version that puts your Hanoi remote team management, live service operations, and experience leading a team of 8+ members front and center. However, if the same person is applying for a position that appeals to new planning (New Team) or solo development capabilities, a version that highlights rapid prototyping using Unity 6, development using AI agents (Vibe Coding), and early roadmap design evidence is appropriate.

You shouldn't cram these two things into one bloated document.

They should be role-specific versions derived from the same markdown source (Single Source of Truth). This is the workflow Hanjang wants to make a daily reality: maintaining the resume in markdown, duplicating versions, changing the emphasis, previewing on a printed paper screen, exporting to PDF, or publishing a clean link stripped of service UI.

The base source data is always stable. Only the sequence and emphasis change according to the target.

Forcing Function

A one-page resume is not a moral rule you must unconditionally keep. It is a forcing function that sharply hones your career.

Open the editor and ask yourself:

• What exactly does the job I'm applying for demand?
• What is my strongest weapon to meet that demand?
• What are the sentences the HR manager can skip without any impact?
• What content should I boldly cut from this version and put into another?
• When pressure questions come in an interview, what outcomes can I confidently defend?

If you answer these questions honestly and pare things down, surprisingly, one page becomes entirely possible. If a second page is still necessary even after that, that page will be excellent data with a clear reason for existing that must survive.

The true standard of a resume isn't 'how long or short it is.' It is 'how fiercely it has been selected and edited.'

Footnotes

1. Harvard FAS Mignone Center for Career Success, "Create a Resume/CV or Cover Letter," https://careerservices.fas.harvard.edu/channels/create-a-resume-cv-or-cover-letter/ ↩

2. MIT Career Advising & Professional Development, "Resumes," https://capd.mit.edu/resources/resumes/ ↩

3. USAJOBS Help Center, "How do I write a resume for a federal job?", https://help.usajobs.gov/faq/application/documents/resume/what-to-include ↩

4. CareerOneStop, U.S. Department of Labor, "Resumes," https://www.careeronestop.org/JobSearch/Resumes/resumes.aspx ↩

5. National Association of Colleges and Employers, "What is Career Readiness?", https://www.naceweb.org/career-readiness/competencies/career-readiness-defined/ ↩

6. UC Davis Career Center, "Resumes," https://careercenter.ucdavis.edu/resumes-and-materials/resumes ↩