Résumé Formats Explained: Chronological vs. Functional

TL;DR — Use the reverse-chronological format. It's what most employers expect, it's what résumé parsers read cleanly, and it solves nearly everything the functional format is supposed to solve. Keep it to one page until you have roughly ten years of experience, and keep the layout boring: single column, standard section headings, common font, no photo, no charts, no text boxes. The decorative template is far more likely to sink you than your writing is.

Most format questions people agonize over have real answers. Not "it depends" — actual answers, backed by what career centers publish, what the federal government requires, and what the research on résumé parsing shows about which layouts survive the trip into a hiring database. This guide covers the three formats, which one you should use, and the six layout decisions that come up every time: length, file type, columns, photos, fonts, and section order.

The three résumé formats, side by side

Every résumé is a variation on one of three structures. The difference is what the document organizes itself around: your timeline, your skills, or both.

Format	Who it's actually for	What it signals	The risk
Reverse-chronological — jobs listed newest first, each with title, employer, dates, and bullets	Almost everyone: students, new grads, career-builders, and anyone whose next job resembles the work they've already done	Steady progression, verifiable history, nothing hidden	Makes gaps and unrelated roles visible, and it won't compensate for a thin skills story on its own
Functional (skills-based) — accomplishments grouped under skill headings, work history compressed to a list at the bottom	A narrow case: a hard career pivot where almost no prior job title maps to the target role	Skills over sequence	Reads as evasion; several career centers warn employers dislike it, and it breaks the title-employer-dates grouping parsers depend on
Combination (hybrid) — short skills or summary block up top, full reverse-chronological history below	Career changers, military-to-civilian transitions, and people whose transferable skills need naming before the job titles make sense	Relevant capability, plus a full timeline	Eats space fast; on one page the skills block can crowd out the evidence that proves it

The James Madison University career center is blunt about which one wins by default: the chronological résumé "is the most common resume format and the one most employers prefer," and it works best when your experience is "closely related to your job or opportunity objective." Its stated weakness is real, though — it "may show gaps in your career path."

Which résumé format should you use?

Reverse-chronological, unless you can name a specific reason it fails you. For students, new grads, and anyone staying in a related field, this isn't a close call. It's the expected shape, it's the easiest to skim, and it's the format every résumé template and parser is built around.

Use a combination format when the job titles don't tell the story. If you're moving from teaching into instructional design, or from military service into logistics, a four-to-six-line skills block at the top does the translation work that your job titles can't — and you still keep the dated history underneath. The NJIT career development office frames it as covering both bases: it "allows you to demonstrate your skills (i.e., the functional resume) and your work history (i.e., the chronological resume) all in one concise document."

Skip the pure functional résumé. The University of Alabama career center names the problem directly: "Not all employers like functional resumes because they prefer to see the details of accomplishments with each position held." There's a mechanical problem too. A parser's job is to bind a job title to an employer to a date range. A functional résumé deliberately separates those three things — accomplishments in one block, employer names in another, dates maybe nowhere — so what lands in the hiring database is a set of orphaned skill phrases with no work history attached. Whatever you were hoping to de-emphasize, you've de-emphasized your entire career along with it.

If you're using a functional layout because your experience is thin rather than because you're pivoting, that's the wrong tool. A reverse-chronological résumé built from coursework, projects, clubs, and part-time work reads far better — we walk through exactly that in how to write a résumé with no work experience.

Should a résumé be one page or two?

Here is an actual recommendation instead of a shrug.

• Students and new grads: one page. USC's career center states it plainly: "In the U.S., one-page resumes are standard practice." JMU adds that résumés for new graduates and entry-level job seekers "are usually limited to one page."
• Under about ten years of experience: one page. Same USC guidance — two pages become acceptable at "10+ years of work experience." Before that, a second page is usually padding, and padding is visible.
• Ten or more years: two pages, and use them. Once you have a decade of relevant work, compressing it into one page means cutting the accomplishments that actually differentiate you.
• Federal jobs: two pages, hard stop. This one isn't advice, it's a rule. USAJOBS states that "Federal agencies only accept resumes up to two pages in length to comply with the Merit Hiring Plan," and that "USAJOBS will not allow you to upload or build resumes longer than two pages."
• Graduate students and academics: it varies by field, and a CV is a different document. Yale's Office of Career Strategy expects an undergraduate résumé "to fit on one page," master's students at one to two, and PhDs and postdocs at two to three pages maximum.

Two rules make the call easy in practice. First, never let a second page hold less than about half a page of content — a two-page résumé with three lines on page two reads as a formatting accident. Second, a few fields have their own conventions worth checking; JMU notes that "some industries, such as education and health, expect two pages."

Should you submit a PDF or a Word document?

Submit exactly what the application asks for. That instruction overrides everything below, every time.

When there's no instruction, either works if the layout is clean — and note that authoritative sources genuinely split on the default. USAJOBS recommends "saving and uploading your resume as a PDF to maintain formatting and number of pages." The University of Minnesota Duluth career center goes the other way, advising you submit in ".docx unless the job posting specifies PDF as required." USC accepts both, recommending "a MS Word document or PDF (converted from Word) instead of any other software."

The split tells you the file extension is not the real variable. Two things are:

• The PDF must be text-based, not an image. A scan, a photo, or a design-tool export that rasterizes your text produces a file with no extractable text. Research on production résumé parsing notes that PDFs "still include challenges such as embedded images, non-standard fonts, and custom encodings that hinder reliable text extraction." If you can't select and copy a line of text out of your own PDF, no parser can either.
• Export from a word processor, not a graphic design tool. Design tools layer text into shapes and boxes that reconstruct badly.

Do columns really break applicant tracking systems?

Yes, often enough that it's not worth the risk — and this is the one layout claim with hard evidence behind it.

A 2025 study of production résumé extraction, Layout-Aware Parsing Meets Efficient LLMs, found that résumés "contain important information embedded in images or use complex, multi-column formats that disrupt standard reading order, making consistent parsing difficult." Their measurement: "approximately 20% of resumes employ non-linear, multi-column layouts that break the standard top-to-bottom, left-to-right reading flow." The fix required building a dedicated layout-reconstruction stage — and adding it lifted extraction F1 on their real-world résumé set from 0.919 to 0.959, roughly halving the error rate. That's with a current frontier model doing the reading. Older non-LLM parsers on the same benchmark scored as low as 0.49.

The failure mode is specific and ugly: the parser reads straight across the page. Your sidebar skills interleave with your job bullets, and what gets stored is a scrambled sentence that matches nothing. As UMN Duluth puts it, avoid "tables, text boxes, or columns" because "ATS reads left to right across the page even with tables and columns."

This matters because the parse is usually the first thing that happens to your application. Harvard Business School's Hidden Workers: Untapped Talent found that "more than 90% of employers used their RMS to initially filter or rank potential middle-skills (94%) and high-skills (92%) candidates."

The layout rules that follow from this:

• Single column, left-aligned. One reading order, no ambiguity.
• No tables, no text boxes. UMN Duluth notes text-box content may not be read at all.
• Contact info in the body, not the header or footer. Headers and footers "may get dropped completely."
• No graphics, logos, charts, or skill bars. "ATS is not able to pull information from these." A five-star rating next to "Python" carries no text and conveys nothing to a database.
• Standard section headings. Use "Education," "Experience," "Skills." Clever headings map to nothing.
• Common fonts only. Downloaded or decorative fonts can encode text in ways the extractor mangles.

USC's list of what an ATS doesn't recognize is the same list from a different campus: "columns, graphic resumes, photos, or fancy fonts." For the keyword side of the same problem — which terms to include and how to pull them from a posting — see résumé keywords and beating the ATS.

Should you put a photo on your résumé?

Not in the United States. Two independent reasons converge.

The legal-practice one: the EEOC's guidance on prohibited employment policies states that "employers should not ask for a photograph of an applicant," and that "if needed for identification purposes, a photograph may be obtained after an offer of employment is made and accepted." Employers who take that seriously don't want an unsolicited photo in their file. The federal application system is explicit about it — USAJOBS lists "Photos of yourself" and "Personal information, such as age, sex, religious affiliation, etc." among the things not to include. Yale lists "including pictures or personal information" as a common résumé error.

The mechanical one: a photo is an image. It occupies prime space at the top of page one and contributes zero parseable text.

The same reasoning applies to the rest of the decoration — icons beside section headings, a colored banner, a donut chart of your language proficiency. None of it survives extraction.

What fonts, sizes, and margins should you use?

Boring and consistent. The published specs cluster tightly:

• Font: a common, universally installed face. Yale suggests "Times New Roman, Helvetica, Garamond"; USC says "Times New Roman or Arial"; USAJOBS recommends a sans-serif and names Lato, Calibri, Helvetica, Arial, Verdana, Open Sans, Source Sans Pro, Roboto, or Noto Sans.
• Size: 10–12 point body text (Yale and USC agree). USAJOBS suggests "14-point size font for titles and 10-point for the main text."
• Margins: USC recommends one inch; Yale sets the floor at "no smaller than 0.5inch"; USAJOBS specifies 0.5 inches. Half an inch is the compression limit — below that the page reads as cramped.
• Emphasis: bold and italics in moderation, underline for headings and links only, and one or two colors at most, since color carries no meaning after extraction.

If you're fighting for space, cut words before you cut margins or font size. A tighter bullet beats a 9-point one.

What order should the sections go in?

Yale's recommended sequence is a good default: header, education, work experience, leadership and community involvement, publications or presentations if relevant, skills, then licenses and certifications.

The one variable worth adjusting is education versus experience. Students and recent grads put education first — it's your strongest credential and the reason you're qualified. Once you have a few years of relevant work, experience moves above it and education shrinks to two or three lines. Within every section, list newest first.

Everything else follows from relevance: whichever section makes the best case for this job goes highest. That's a per-application decision, not a permanent one, and it's the cheapest tailoring move there is — more on the rest in how to tailor your résumé with AI.

The five-minute format check

Before you send anything, run these four:

1. Copy-paste test. Open the file, select all, paste into a plain text editor. If the reading order scrambles, if bullets vanish, or if your contact info disappears, that's what the hiring database receives. Fix the layout, not the text.
2. Header test. Confirm your name, email, and phone sit in the body of the document, not in a header or footer region.
3. Heading test. Read only your section headings. Would a stranger know what each block contains?
4. Second-page test. If page two exists, is it at least half full, and does the second page repeat your name?

Formatting is the part of a résumé you can get objectively right, and it's worth exactly one afternoon — then never again. The content is what actually differentiates you, and it deserves the rest of your time; if you're starting from scratch, work through how to write a résumé next.

Sources

• U.S. Office of Personnel Management / USAJOBS Help Center — How do I write a resume for a federal job?
• U.S. Equal Employment Opportunity Commission — Prohibited Employment Policies/Practices
• James Madison University Career Center — Choosing a Résumé Format
• The University of Alabama Career Center — Special Resumes
• New Jersey Institute of Technology Career Development Services — The Combination Resume
• University of Minnesota Duluth Career Center — Applicant Tracking System (ATS) Tips
• University of Southern California Career Center — Resume Format Guidelines
• Yale University Office of Career Strategy — Resume Formatting and Common Errors
• Zhu et al. (2025) — Layout-Aware Parsing Meets Efficient LLMs: A Unified, Scalable Framework for Resume Information Extraction and Evaluation
• Fuller, Raman, Sage-Gavin & Hines, Harvard Business School Project on Managing the Future of Work — Hidden Workers: Untapped Talent