Figma on your resume: what you shipped in it, not that you opened it

The direct answer

Yes, list Figma if design or design-adjacent work is part of the job, and link work you are allowed to share. Figma appears on 2.86% of the 72,068 resumes RezScore analyzed from November 15, 2025 through July 15, 2026, ranking #40 among 89 reviewed technology skills. For design work, a tool line needs a flow, prototype, component system, or other artifact behind it. For engineering or product work, define whether your Figma use involved review, collaboration, or handoff.

Be specific about which of those you are claiming. Designing a component system is not the same as commenting on a prototype, and both are honest to describe when you name them accurately.

How to present Figma on your resume

Give the skills section context

Say what you do in Figma: Figma (component libraries, prototyping, Dev Mode handoff) for designers, or Figma (design handoff, spec inspection) for engineers and product managers. That second phrasing is honest, useful, and does not overclaim.

Prove it in your experience

Then show one thing you shipped. Fill in this pattern with your own work:

Designed [flow or component system] in Figma for [product or team], which shipped as [result].

That connects the file to a real product. If you have an honest measure, such as a support-ticket drop or a research finding that changed the design, use it. If not, name what shipped. Do not attach an invented conversion lift to a screen you drew.

Use verbs that show the work

Designed, prototyped, componentized, specified, and tested describe Figma work. Familiar with Figma does not define a responsibility. Built and maintained a component library used across a product team describes ownership.

Be honest about thin experience

If your Figma experience is coursework, a bootcamp capstone, or a redesign of an app you do not work on, label it as personal or academic work. That label gives the artifact honest context. Presenting a concept as client work makes the rest of the claim difficult to trust.

Leave Figma off when you have never opened a file and only ever saw screenshots pasted into a document. For non-design roles, one honest line about reading specs is enough, and a skills list implying design ownership collapses at the first interview question about how you handled feedback on a real flow.

Skills that appear with Figma

Figma rarely appears alone. In this sample, the skills most often found on the same resumes were:

• HTML appears on 51.4% of the resumes in this sample that mention Figma (1057 resumes).
• CSS appears on 49.9% of the resumes in this sample that mention Figma (1027 resumes).
• JavaScript appears on 39.7% of the resumes in this sample that mention Figma (816 resumes).

If you use these with Figma, list them together. Design plus front-end markup reads as someone who can carry an interface from file to browser rather than hand it over a wall.

Questions people ask about Figma on a resume

Should engineers list Figma on a resume?

Yes, if you work from Figma files regularly. Describe it as design handoff or spec inspection rather than design ownership. That is honest and it tells a hiring manager you can work with a design team without hand-holding.

How many resumes list Figma?

Figma appears on 2.86% of the 72,068 resumes RezScore analyzed from November 15, 2025 through July 15, 2026. That is 2,058 resumes and a #40 rank among the 89 reviewed technology skills in this analysis.

Do I need a portfolio if my resume lists Figma?

For design roles, pair Figma with work a reviewer can inspect when possible. Link a portfolio or shareable flow that you can discuss in depth, and do not link confidential client or employer files.

Where should Figma go on my resume?

For design work, use the skills section with context, such as Figma (component libraries, prototyping), and an experience or project bullet naming what you produced. For other roles, describe only the Figma collaboration or handoff work you actually did.