There are three resume formats. Chronological lists roles newest first with the work under each. Functional lists skills with the work grouped under them and the roles in a short list at the end. Combined does both, skills first and then the roles. Use chronological. The functional format exists to hide something, every recruiter knows that, and the parser cannot read it anyway. The combined format has one real use, a career change, and the guide on that covers it.
Key points
- Chronological, unless you have a specific reason. Most people do not.
- Functional hides the timeline. Recruiters read it as a gap or a job hop, and parsers read it as nothing.
- Combined is chronological with a skills block on top. It helps a career changer and nobody else.
- The parser decides the format before the person does. Headings in plain words, dates on every role.
- The format is not where a resume wins. The bullets are.
The three formats
| Format | Order | Who it serves | What a parser makes of it |
|---|---|---|---|
| Chronological | Summary, roles newest first, skills, education | Everyone with a timeline | Reads it cleanly |
| Functional | Summary, skill groups with bullets, a role list without bullets | People hiding a timeline | Cannot attach bullets to roles. Dates often missing. |
| Combined | Summary, skills block, roles newest first | Career changers | Reads it, if the skills block is short |
Why chronological
A recruiter reads a resume for the last role first. What did you do most recently, for whom, for how long. The chronological format answers in the first ten seconds. Everything after that is detail.
A hiring system reads the same way. It looks for a role heading, a company, a date range, then bullets, and it files each bullet under the role above it. That is how Match on this site reads your resume too, and how any screener's search works. Chronological is the format the machines were built around.
The reader wants to know what you did last. Tell them first.
Why functional fails
The functional format groups bullets by skill instead of by role. "Leadership: led a team of eight. Managed a budget of two million." Then "Design: redesigned the checkout." Then, at the bottom, a list of employers with dates and no bullets.
Two things happen. The recruiter sees the format and reads it as a signal: there is a gap, or a job hop, or the last role was a step down, and this person does not want me to see it. They then go to the role list and look for the thing, which takes longer than it would have taken to read it in order.
The parser does worse. It cannot attach "led a team of eight" to an employer, so the bullet has no date and no company. A search for "team lead at a logistics company in the last three years" finds nothing. The resume has become a list of claims with no evidence attached.
The things people use the functional format to hide have better answers. The guide on employment gaps has the one sentence that handles a gap. The guide on a career change resume has the reframing. Both keep the timeline.
When combined helps
A combined resume is chronological with a short skills block between the summary and the first role. Six to ten skills, grouped, in the posting's words.
It helps when the roles do not say what you can do. A career changer whose last three titles were in retail management and whose next role is in operations analytics uses the block to say "data analysis, SQL, dashboarding" before the reader meets the word "store". The roles then back it up.
It does not help when the roles already say it. A senior designer with three design roles does not need a block that says "design". The block costs the reader three lines and gives nothing.
Keep the block short. A parser reads it as skills, which is right, and then reads the roles, which is where the evidence is.
What the parser needs from any format
Whatever the order, four things make a resume readable to a hiring system.
- Headings in plain words: Experience, Education, Skills. Not "Where I have been".
- Each role as title, company, dates, on one or two lines, before its bullets.
- Dates in a form with a month and a year, or a year alone. "2021 to 2023", "Mar 2021 to Jun 2023".
- No tables for layout, no text in images, no two-column pages that a parser reads across.
The guide on ATS-friendly resumes has the rest, and the score on this site shows what the parser saw.
Questions
Is a two-column resume a format problem?
Yes, for the parser. Many read the page across, so the left column's skills and the right column's roles get interleaved into nonsense. One column, always.
What about a creative format for a design role?
The portfolio is where the design goes. The resume is read by a parser and a recruiter before a designer sees it. A clean one-column resume with a link to the portfolio wins both reads.
Do I list roles oldest first?
No. Newest first, always. The one exception is an academic CV, which the guide on CV versus resume covers.
Can I leave dates off?
Off the education, yes. Off a role, no. A role without dates reads as a role that was short. If the dates are the problem, the gaps guide has the fix.
Is "combined" the same as "hybrid"?
Yes. Two names for one format: a skills block on top of a chronological resume.