How a functional resume is laid out
Instead of listing jobs one by one, a functional resume groups what you have done under skill headings. A typical structure:
- Name and contact details
- Summary
- Skills sections, for example “Project management”, “Customer service”, “Training”, each with three or four achievement bullets
- A short employment history: just titles, employers and dates, or sometimes nothing at all
- Education
Training and coaching
- Designed a two-week onboarding programme used for 60+ new hires
- Coached five junior staff into team-lead roles
- Ran monthly workshops on the new booking system
The achievements are real, but the reader can’t tell which job each one came from.
Who it can suit
People usually reach for a functional resume when their timeline is awkward:
- Career changers, whose most relevant skills come from a different field. See career change.
- People with a long gap, for example after caring for family or illness. See employment gap.
- Freelancers with many short projects that look messy as a list of jobs.
- Returners and early-career candidates whose best examples come from volunteering or studies.
In each case, the goal is to put what you can do ahead of where you did it. That goal is sound. The format is the problem.
Why it often backfires
- Recruiters are suspicious of it. Hiding the timeline is a well-known way to cover gaps or job-hopping, so a functional layout can draw more attention to exactly what you hoped to downplay.
- It’s hard to verify. “Led a team of eight” means more when the reader knows it was at a real company, last year.
- Software reads it badly. An applicant tracking system builds your profile from jobs and dates. With skills floating free of jobs, your experience can be misread or partly lost.
Better alternatives
For most people with an unusual path, a combination resume works better: a short skills section at the top to frame your story, followed by a normal, dated work history. You keep the focus on skills without hiding anything.
If your history is fairly steady, a plain chronological resume is still the safest choice. And whichever you pick, be open about gaps with a one-line explanation. A clear, honest timeline almost always reads better than a clever format.
If you already have a functional resume, converting it is mostly a matter of moving things around. Keep your best two or three skill groups as a short section at the top, then rebuild a dated job list underneath. Take each achievement bullet from the skill sections and place it under the job where it happened. Anything that doesn’t fit under a job, such as volunteering or a personal project, can get its own small section with dates.
FAQ
Do recruiters like functional resumes?
Many don't. Because dates and employers are hidden or minimised, recruiters often assume something is being covered up, such as a gap or a short job. It is also harder for them to see where and when you used each skill.
Is a functional resume ATS-friendly?
Not very. Applicant tracking systems expect job titles, employers and dates together. When skills are separated from jobs, the system may not be able to connect them, and your profile can come out incomplete.
Who should use a functional resume?
Very few people need a pure functional resume today. It can make sense for some career changers, people returning after a long break, or those with many short freelance projects, but a combination resume usually does the same job with less risk.
Should I list any jobs on a functional resume?
Yes. Even a functional resume should end with a short employment history (title, employer, dates). Leaving it out entirely raises more questions than it answers.
