On this page
Written and reviewed by the Resumarc team · Last reviewed 28 July 2026How we write our guidance
At a glance
Functional
Most people who want this should use a combination resume
We would rather be straight with you than sell you a format that gets your application filtered out. Recruiters tend to read a missing timeline as concealment, and hiring software struggles to extract experience it cannot find dates for. The idea behind this format is sound. Keeping a short dated history costs you a few lines and removes almost every downside, and that is a combination resume.
Best for
- A genuine pivot with no adjacent work
- Returning after a long deliberate break
- Portfolio or project-led work
- Applying direct to a human, not a portal
Avoid if
- You are applying through a large portal
- You have any relevant dated history
- The field is traditional or regulated
What is a functional resume?
A functional resume opens with an objective, then devotes most of the page to skill groups, each supported by examples drawn from wherever you have them: work, study, volunteering, freelance projects, or personal ones. The work history section still exists but is short, often just titles, employers, and dates with no detail beneath.
The appeal is obvious. If your experience is scattered, unrelated, or thin, arranging the page around capability rather than chronology lets you lead with your strongest material. For a small number of people that is genuinely the best available argument.
The cost is equally real, and most guides understate it. Recruiters see this format often enough to have formed a view, and that view is usually that something is being kept from them. The reaction is not to the skills but to the missing timeline, and it tends to arrive before anyone has read your evidence.
There is a technical cost too. Hiring software is built to break a resume into roles with employers and dates. When there is little dated history to find, the system may store an incomplete profile or fail to compute your years of experience, which quietly pushes you down the list in searches you would otherwise appear in.
None of this makes the format useless. It makes it a specialist tool. Use it when your circumstances genuinely match the cases below, and be aware of what you are trading away.
The functional stack
Top of page to bottomSelect a block to see why that section sits where it does.
Most of the page. Three or four themes, each with concrete examples underneath. Without evidence this section reads as a list of claims.
See it rendered
A real Resumarc template, arranged in this format by the same engine the builder uses. Nothing here is a mock-up.
What to look for. Skills take the page and education moves above the history. Notice that the work history keeps every job and date but loses its detail. That thinning is what a parser struggles with.
Templates that suit this format
Every Resumarc template can be arranged in any of these formats. You drag a section to move it, so switching format later never means starting again.
When to use it
- You are making a genuine pivot into a field where none of your paid work is adjacent.
- You are returning after a long, deliberate break and your skills are more current than your job titles suggest.
- Your strongest evidence is projects, a portfolio, or open-source work rather than employment.
- You are applying directly to a person, at a small organisation, where no automated screening sits in the way.
- You are early in your career with internships, coursework, and volunteering but little formal employment.
- In every one of these cases, check the combination format first. It usually does the same job with less risk.
Pros and cons
What works
- Your capability leads the page, which helps when your job titles work against you.
- It gathers evidence from anywhere: study, volunteering, freelance, and personal projects all count equally.
- It reduces the visual weight of a broken or unusual timeline.
- For portfolio-led work, it puts what you can make ahead of who employed you.
- It is genuinely useful when you are handing a resume to a person rather than a system.
What to watch
- Recruiters commonly read it as concealment, and that reaction usually lands before your skills are read.
- Hiring software parses it least reliably of the three formats, because there is little dated history to extract.
- Skills without context are easy to doubt. "Leadership" means nothing until it is attached to a situation.
- It hides career progression, which removes an argument that would otherwise work in your favour.
- Traditional and regulated industries tend to expect a timeline, and its absence stands out.
- It rarely solves the problem people hope it will. A gap is usually less conspicuous than a missing history.
How to write it, step by step
- 1
Write the header, and make your portfolio easy to find
Standard contact details, with one adjustment. This format leans harder on work you can show, so if you have a portfolio, repository, or body of published work, give it a prominent line rather than burying it.
Header
Rina Okada
UX Designer
rina.okada@email.com · +81 90 1234 5678 · Osaka, Japan
Portfolio: rinaokada.design · linkedin.com/in/rinaokada
- 2
Open with an objective, not a summary
A summary looks backward at a career; an objective states where you are going. Name the role you want, the skills you are bringing, and the reason the move makes sense. Three or four sentences, written for the specific job.
Career objective
Seeking a junior UX design role where research and prototyping skills matter more than years in the industry.
Two years designing interfaces for community and volunteer organisations, including a booking system now used by 4,000 people a year.
Trained in user research, wireframing, and usability testing through the Interaction Design Foundation programme.
Moving from front-of-house hospitality management, where the work was already about watching people struggle with a process and fixing it.
- 3
Build three or four skill groups, each with real examples
This is the whole resume, so it has to carry weight. Choose themes straight from the job advert. Under each, give two or three specific examples with the situation, what you did, and what resulted. Say where each example comes from, whether that is a job, a course, a volunteer role, or a personal project. Naming the source is what turns a claim into evidence.
Skill group
User research and testing
Ran 12 moderated usability sessions for a food bank's booking tool, cutting failed bookings by roughly a third. (Volunteer, Osaka Food Network)
Built and analysed a 200-response survey on scheduling frustrations that set the redesign priorities. (Volunteer)
Completed the Interaction Design Foundation user research course, 2025. (Certification)
Any line you cannot attribute to a real situation should be cut. Unattributed skills are what make this format read as thin.
- 4
Keep a short work history. Never remove it
This is the step most guides get wrong. Even in a functional resume, list every role with its title, employer, and dates. You can drop the bullets, but the dated entries themselves have to stay. They are what lets software build a profile for you and what stops a reader assuming the worst about what is missing.
Work history
Front of House Manager · Kitajima Dining · Osaka · 2021 to 2025
Senior Server · Kitajima Dining · Osaka · 2019 to 2021
UX Design Volunteer · Osaka Food Network · 2024 to present
If you find you can write real achievements under these roles, you should be writing a combination resume instead. That is a good problem to discover.
- 5
Move education up
In this format education is doing more work than usual, because it is often your most solid dated evidence. Place it above the work history. Include relevant coursework, projects, and honours where they support the skill groups above.
- 6
Before you send it, check you still need this format
Look at the finished page and ask whether you could write two or three real achievements under your recent roles. If you can, move them up into a full work history and you have a combination resume, with the same skills-first opening and far less risk of being filtered out.
How applicant tracking systems read it
Most applications pass through software before a person sees them. These are the details that decide whether your experience lands in the right fields.
- This is the format's weakest point. Parsers build a candidate profile from dated roles, and a resume that minimises them gives the system very little to store.
- Keep every job title, employer, and date even when you drop the detail beneath them. This single habit recovers most of the lost parsing reliability.
- Some large employer portals ask you to re-enter your work history manually after upload. A thin history means a thin application form, which the recruiter sees directly.
- Head the section "Work Experience" even when it is short. Renaming it "Background" can stop it being recognised as a history block at all.
- Where a system computes years of experience from your dates, a minimal history can read as a junior candidate regardless of your skill groups.
Compare the three formats
Same sections, different order and different emphasis. This is the whole difference between them.
| Chronological | Combination | Functional | |
|---|---|---|---|
| Leads with | Your work history, newest first | Grouped skills, each backed by evidence | Grouped skills, with the timeline pushed down |
| Best for | A steady history in the field you are applying to | Career changers and skills-led or technical roles | A genuine pivot with no adjacent experience |
| ATS reliability | Highest. Built exactly the way parsers expect | High. Keeps the dated history parsers need | Lowest. Little dated history to extract |
| Recruiter familiarity | Universal. Needs no decoding | Well understood and increasingly common | Often read as hiding something |
| Main risk | Gaps and career changes are plain to see | Repeating your work bullets in the skills block | Being screened out before anyone reads the skills |
| Typical length | One page, two if you are senior | Runs long. Both sections need discipline | One page. There is less to say |
Frequently asked questions
Key takeaways
- A functional resume organises the page around skills and pushes the timeline into the background.
- It suits a narrow set of situations: a real pivot, a long deliberate break, or portfolio-led work.
- Recruiters often read the missing timeline as concealment, and that reaction arrives before your skills are read.
- It parses least reliably of the three formats, so it is a poor fit for large employer portals.
- Always keep job titles, employers, and dates even when you drop the detail beneath them.
- If you can write real achievements under your recent roles, write a combination resume instead.
Build it without fighting the layout
Every Resumarc template supports all three formats. Drag a section to reorder it, and your resume stays readable for both people and software.
Not sure how your resume scores?
Upload it and get an ATS compatibility score with section-by-section feedback, free. Fix what the score flags, then apply.
Check my resume