Listen to this article
A friend of mine spent a weekend rebuilding her CV around a "Core Competencies" section — three bold headers, bullet points grouped by skill, no dates in sight until page two. She was proud of it. Two recruiters never opened it past the first screen; the ATS that scanned it for a third role couldn't find a job title to match against the posting at all. The format wasn't the problem she thought it solved.
That's the real answer to chronological vs functional resume: use chronological by default. Functional (skills-based) formats are a niche tool, not a neutral alternative, because both ATS parsing and recruiter habits are built around a timeline, not a set of skill headers.
What the two formats actually are
A chronological resume lists your work history job by job, most recent first, each with dates, title, employer, and results. It's the format every ATS was designed to read and every recruiter was trained to skim.
A functional resume format (also called a skills-based resume) drops that structure. Instead of jobs, it opens with categories like "Leadership," "Project Management," or "Client Relations," each followed by bullet points pulled from across your career — with dates and employers pushed to the bottom, shortened, or left out entirely.
The pitch for functional resumes, repeated across most resume advice sites, is that it lets you "highlight skills over sequence." That's true. It's also exactly what makes both software and people distrust it.
Why chronological wins by default
Applicant tracking systems parse resumes by looking for recognizable patterns: a job title near a date range, near a company name, in a repeating block. That's how they build your work-history timeline and match it against a posting's requirements. Our ATS-friendly CV format guide covers parsing behavior in more depth, but the short version is: strip out the dated, repeating job blocks, and the parser has nothing reliable to hang your experience on.
Recruiters read the same signal by eye. A chronological CV answers their first three questions in seconds — what do you do now, how long have you done it, is your career moving forward. A functional one makes them dig, and a recruiter with 150 CVs in a queue does not dig. Reordering by skill instead of employer reads less like "efficient" and more like "something is being avoided here" — usually a gap, a demotion, or job-hopping.
This is a different decision from page layout — whether you use one column or two is a design choice we cover separately in CV layout: single vs two column. Chronological vs functional is about what content goes where, not how it's arranged on the page, and it matters more for getting past the first screen.
The narrow cases where functional still makes sense
There are real situations where a skills-based resume vs chronological trade-off tips the other way — but they're narrower than most advice pages admit:
- You're applying somewhere with no ATS in the loop at all — a referral straight to a hiring manager, a very small company, or a niche craft field where the CV is read by hand.
- Your relevant experience is genuinely scattered across unrelated roles and a strict timeline would bury it — for example, moving between industries where the skill, not the job title, is the through-line. Even here, career-change CVs usually do better reframing chronological bullet points around transferable skills than abandoning the timeline entirely.
- You've been told directly, by someone hiring for the role, that they want a skills summary.
Outside those cases, a functional resume is solving a visibility problem by creating a bigger one.
Resume format for gaps: the honest alternative
Functional resumes get recommended constantly as a resume format for gaps, on the logic that hiding dates hides the gap. It doesn't — it just makes the gap look intentionally concealed, which reads worse than the gap itself. If you have a break in your history, a chronological CV with one calm, factual line about it does more for your credibility than a format built around avoiding the question. We wrote a full breakdown in how to explain a career gap on your CV without apologizing.
The safer middle ground, if you genuinely need to lead with skills, is a hybrid resume: a short skills or summary section at the top, followed by a complete, dated, chronological work history underneath. It gives a skimming recruiter the headline and gives the ATS the parseable timeline it needs. It is not the same as a pure functional format, and it's the version worth using if you're tempted by "skills-first."
Checklist: which format does your CV actually need
Run your own work history against this before you pick a structure:
- Will this CV likely pass through an ATS before a person sees it? If yes, chronological (or hybrid) is the safer default.
- Do you have a consistent, forward-moving job history with no more than a short gap? Chronological, no exceptions.
- Is your career story genuinely built on cross-industry skills rather than job titles? Consider hybrid — skills summary on top, full timeline below.
- Are you hiding dates because a specific stretch feels uncomfortable to explain? That's a sign to write one honest line about it, not to restructure the whole document.
- Has an actual person at the hiring company asked for a skills-first format? Then, and only then, a pure functional resume is worth the risk.
If you run through that list and you're still not sure which way your CV should go, that's exactly the kind of judgment call worth a second pair of eyes. Kaeros's free CV review has a real person look at what you've built and tell you plainly whether your structure is helping or working against you — no account needed, and no cost either way.