A skills-based (functional) resume leads with what you can do instead of where you worked. It exists for one situation: your most relevant evidence is scattered across roles, projects, or fields, and a strict timeline would bury it. Used well, it reframes a non-linear path as a coherent skill set. Used badly, it looks like you are hiding something — so this guide is as much about the guardrails as the template.

When to use it — and when not to

• Use it when you are changing fields, returning after a gap, consolidating freelance work, or early in your career with strong project work but thin job history.
• Avoid it when your last two roles already match the target job — a chronological format will always read stronger there. Recruiters trust timelines; only trade that trust away when the timeline works against you.
• Never drop the work history entirely. A functional resume with no dates reads as evasive. Keep a compact history section at the bottom.

Section order

1. Header — name, target title, location, email, phone, one link.
2. Positioning summary — three lines that name the target role explicitly.
3. Skill clusters — two to four clusters, each with proof-point bullets.
4. Selected projects (optional) — when project work is your strongest evidence.
5. Work history — compact: title, company descriptor, dates. No bullets.
6. Education and certifications.

The fill-in skeleton

{{Full name}} {{Target title}} · {{City, Country}} · {{Email}} · {{Profile link}}

Summary: {{Target role}} candidate combining {{Skill area 1}} and {{Skill area 2}} built across {{Contexts, e.g. agency, freelance, and volunteer work}}. {{One sentence naming your strongest measurable proof}}.

{{Skill cluster 1, e.g. Client communication}}

• {{Proof bullet: verb + what + measurable outcome, naming the context it came from}}
• {{Proof bullet 2}}
• {{Proof bullet 3}}

{{Skill cluster 2, e.g. Data analysis}}

• {{Proof bullet 1}}
• {{Proof bullet 2}}

Work history

• {{Job title}}, {{Company descriptor}} — {{Years}}
• {{Job title}}, {{Company descriptor}} — {{Years}}

Proof-point patterns

Each cluster bullet must anchor the skill in a real context, or it reads as self-assessment. Three patterns that work:

Choosing your clusters

Take the job posting for your target role and pull out the three or four capabilities it repeats. Those are your cluster names — use the posting's own vocabulary, not your internal labels. Every bullet under a cluster should make a skeptical reader say: fine, that counts as evidence.

Guardrails

• Keep dates honest. The compact history must account for your time; explain gaps in the cover letter or summary, not by omission.
• Maximum four clusters. More reads as a skills inventory, not a positioning.
• Quantify inside every cluster. The format already costs you some credibility with traditionalists; numbers buy it back.
• One page. A functional resume that spills to two pages has lost the argument for its own existence.