Resume format: chronological vs functional vs hybrid
Before a single word of content, the format of your resume decides how easily a recruiter — and an applicant tracking system — can read it. There are three, and choosing wrong can quietly sink an otherwise strong resume. Here's exactly what each is, who it's for, and how it fares in an ATS.
Lists your work history newest-first, each role with dates, company and outcome-led bullets. It's what recruiters expect, it shows career progression at a glance, and it parses cleanly in every major ATS because dated Experience entries map straight to database fields.
✓ Use this unless you have a specific reason not to.
Groups your abilities under skill headings and downplays or hides a dated work history. The intent is to mask gaps or a career switch — but recruiters read the missing timeline as ‘what are they hiding?’, and ATS parsers that expect dated roles often mangle it. It's the format most likely to get you screened out.
✗ Avoid — use a hybrid instead if you're worried about gaps.
The best of both: a short skills-forward summary and a core-skills block at the top, sitting above a full reverse-chronological history with dates. You get to foreground transferable skills for a pivot without hiding your timeline — so it stays recruiter- and ATS-safe.
✓ The right choice when a pure chronological doesn't tell your story.
Whichever you pick, keep it parser-safe
- ✓Single column of real, selectable text — no tables, text boxes or images of text.
- ✓Standard headings: Summary, Experience, Skills, Education.
- ✓Consistent MM/YYYY dates; a clean, text-based PDF.
Build any of these free in Resume Studio with ATS-safe templates, then check it against a real job with TrueFit.
Build my resume free →How parsers and recruiters actually read your format
Two-column layouts look polished but break in parsing. An ATS reads left-to-right, top-to-bottom within a single stream — it doesn't understand the visual column boundary. Your side-by-side Skills and Achievements turn into a jumbled sequence where achievements, skills, dates, and company names interleave in the wrong order. Recruiters opening your PDF on their screen see the layout as you designed it, but the parsed data (the version that goes into their database and filters) is unreadable.
Tables and text boxes suffer the same fate. Tables destroy the linear reading order; a parser might catch the cell content but loses the row and column relationships. Text inside images vanishes completely — ATS systems do not run optical character recognition, so any resume content embedded as a graphic (a chart, a logo, decorative elements) is invisible to parsing. Headers and footers are wildly inconsistent across PDF readers; some platforms skip them entirely.
Unusual section names trip up mapping logic. A recruiter's database expects fields named Experience, Skills, Education. If you label your section 'Core Competencies' or 'Key Projects,' a rule-based parser might fail to recognise it and leave that field empty in the database. Stick to the standard names and you stay unambiguous. Non-standard names are not forbidden — they just carry risk that the data lands in the wrong place.
File format: when PDF beats DOCX and every system has an opinion
PDF locks your layout — what you see on your screen is what a recruiter sees on theirs. Formatting doesn't drift. DOCX is editable across systems, but fonts, margins, spacing, and line breaks can shift depending on the recipient's Word version, OS, or even their default font substitutions. If a recruiter opens your DOCX in an older version of Office or on a different operating system than you used, your careful spacing collapses.
ATS parsing strongly prefers PDF. Most major platforms have mature PDF handlers; DOCX support is newer and less reliable across the industry. If you have a choice, PDF is the safer bet. That said, some older systems might struggle with modern PDF specifications — if a recruiter reports parsing errors, ask them if they'd prefer DOCX, then regenerate from your source (never just save a PDF as DOCX; it produces corruption).
The submission platform's instructions matter most. If they say 'PDF preferred,' use PDF. If they say 'DOCX only,' use DOCX even if you prefer PDF. If they don't specify, default to PDF. Never ignore the application system's guidance to follow a general rule. And one detail: never submit a DOCX with tracked changes enabled, comments, or edit history. Export a clean, final version. Old metadata (author names, edit dates) can leak information you didn't mean to share.
Length by career stage and date formatting precision
Your resume's length is tied to your experience, not to advice you found online. A graduate applying for your first role: one page, no exceptions. You don't have 10 years of work to show. One page forces you to cut filler, which is a feature. Mid-career (5–10 years experience): one to one-and-a-half pages. Two pages is defensible only if every single line adds weight — significant achievements, leadership, scope that took time to describe. Senior or specialist (10+ years): two pages is credible only if the depth is there. Many senior candidates fit a strong one page; two is not the default just because of tenure.
Geography shifts the norms. In the UK, Ireland, and most of Europe, one page is standard across all levels. Two pages is rare and reserved for executive roles or those with extensive published research. In the US and Australia, two pages is expected for mid-career and above. If you're applying internationally, match the norm of the country where you're applying, not where you live. A one-page resume sent to a US hiring manager who expects two won't be penalised — it just signals different norms.
Date formatting must be consistent because parsing relies on pattern-matching. Use MM/YYYY (03/2024) or Month YYYY (March 2024) throughout. Do not mix 3/2024, 03/2024, and 'March 2024' in the same document — a parser looking for a date pattern will miss the inconsistent ones. A one-month gap (you left in January, started again in February) barely registers — most recruiters don't comment on it. A six-month to one-year gap does get noticed. You don't owe a detailed explanation, but naming the reason briefly ('medical leave', 'family responsibility', 'skill transition') is safer than leaving it blank. Gaps older than three years matter less to most employers — a break from 2020 is now ancient history in most fields.
Frequently asked questions
Should I use a two-column layout to fit more content?
No. Two columns look professional on screen but parse unpredictably — an ATS reads top-to-bottom, left-to-right in a single stream and will jumble your skills and experience. A recruiter sees the layout correctly, but your parsed data is corrupted. Use one column, real text, standard section names. If you need to fit more in, cut weaker bullets instead.
Is PDF or DOCX safer for an ATS?
PDF is safer because it locks formatting — what you see is what they get. DOCX is editable but can shift across systems and Word versions. Most ATS platforms parse PDF more reliably. If the application says 'PDF preferred,' use PDF. If they say 'DOCX only,' use DOCX. Follow their instruction first.
How far back should my work history go?
Include all roles in the past 10–15 years. Older roles are less relevant unless they're important context for a big achievement or a career pivot. A role from 20 years ago rarely affects hiring decisions now. For entry-level, three years is enough. Don't leave out key experience to save space; you're not space-limited.
How should I format dates to make sure an ATS reads them correctly?
Use MM/YYYY (03/2024) or Month YYYY (March 2024) and be consistent throughout. Don't mix formats. Avoid abbreviations like 'Mar' or numeric-only styles. Use the same pattern for every date on your resume so parsers can identify them reliably.
How should I explain a one-year gap in my employment?
A gap of 1–6 months barely matters to recruiters; skip an explanation and move on. For gaps of six months to a year, a brief label ('skill transition', 'medical leave', 'family responsibility') is helpful without needing detail. Older gaps (three-plus years ago) now matter very little — hiring is focused on your recent work.