Figma interview prep

See what Figma asks, then get a plan for it

Real Figma frontend questions and candidate reports, turned into a week-by-week prep plan.

~2 min · free preview

Company prep

Figma Front End Interview Guide

The Figma frontend interview process, real questions, and candidate reports.

Questions
159
Reports
Solved
—

Verified by FrontendLead

Practice questions159

From the community

Interview reports

Figma frontend interviews lean on the product itself: canvas geometry, styled text ranges, and undo and redo. Here is what members report and how to prepare.

This guide is built from 1 Figma interview report that a FrontendLead member posted in October 2026, the 12 coding questions members have tagged with Figma, and what Figma publishes about its own hiring process. That is less evidence than we have for larger companies, so each section says whether a detail comes from a member or from Figma. The exact prompt from the member report is in the members-only section below.

The biggest pattern: Figma questions look like small pieces of an editor. You order shapes on a canvas, edit ranges of styled text, or keep an undo history correct. Figma also says its coding interview is language-agnostic and focused on data structures and algorithms, so plain problem-solving skill matters as much as React.

By Shivam Bhalla · Updated

01

Figma frontend interview at a glance

Process
Application, recruiter screen, a skill assessment for some roles, then a virtual onsite (Figma careers site)
Coding interview
Language-agnostic, focused on data structures and algorithms (Figma careers site, early-career roles)
Phone screen
One coding question, per the one member report (mid-level, October 2026)
Recurring themes
Canvas geometry and ordering, styled text ranges, undo and redo
Design round
Map out an architecture, then write the code for it, in a FigJam board (Figma engineers, 2021)
Behavioral
One behavioral interview with a member of the team (Figma careers site)
Evidence
1 member report and 12 member-tagged coding questions
02

Figma frontend interview process

Figma lists four stages on its careers site for early-career roles. Member data covers only the phone screen so far, so the later stages are Figma’s own description. Ask your recruiter how the loop differs for your level.

  1. 1

    Recruiter screen

    Source: Figma careers site

    A recruiter reaches out to learn about your background and skills. Prepare a two-minute summary of your most recent project: what you built, the hardest technical decision, and the result. Know which part of Figma you want to work on and why.

  2. 2

    Skill assessment

    Some roles only

    Figma says some roles require a portfolio review, take-home activity, or online assessment, and that your recruiter shares the details. No member has reported one for a frontend role yet.

  3. 3

    Phone screen

    One coding question, per one member report

    A mid-level full-stack candidate with 2.5 years of experience got a single coding question about arranging rectangles on a 2D canvas. It had an easy first case and a harder second case, which is the usual shape: get a correct simple version working, then handle the input that breaks it.

  4. 4

    Virtual onsite

    Technical and non-technical interviews

    Figma says to expect both technical and non-technical interviews, and that you will walk through your background with a potential mentor or manager. For software engineering it names a language-agnostic coding interview on data structures and algorithms, plus a behavioral interview with a member of the team. No member has reported a full onsite loop yet, so the number of rounds is not confirmed here.

03

What Figma coding questions have in common

The 12 questions members tagged with Figma fall into four groups. None is a pure trick question. Each one is a simplified version of something a design tool has to do.

Interviewers in this style of question are checking three things: whether you state the rule before you code it, whether your first version is correct on the simple case, and whether you find the edge case yourself before they point it out.

04

Coding questions Figma candidates were asked

The first prompt comes from a member report. The others are the question groups members tagged with Figma.

Sort rectangles in display order

Mid-level full-stack, phone screen, October 2026

You get a list of rectangle nodes, each with x, y, width, and height on a 2D canvas. Write a function that sorts them in display order, from top-left to bottom-right, the way a person would read them in rows.

The simple case has three rectangles side by side with slightly different y values, and the answer is left to right. The harder case adds a rectangle far below the others, so the function has to recognize a second row.

The member’s advice: the tricky part is deciding when two rectangles are in the same row, because their y values are not identical. Group rectangles by vertical overlap first, then sort each row by x. Say that rule out loud before you write code, and ask what should happen when a tall rectangle overlaps two rows.

Practice: Sticky Note Order and Scanned Receipt Lines.

Styled text range edits

Tagged by members

Four tagged questions deal with formatted text. Three store the text as a plain string plus a list of style ranges: you patch a style onto a range, replace text and shift or split the ranges around it, or slice the string and clip the ranges to match. The fourth stores formatting as runs of a given length and asks you to apply a style to a range of them.

Practice: Patch Text Styles, Replace Styled Text, Slice Styled Text, and Paint Style Runs.

Undo and redo history

Tagged by members

Three tagged questions ask for a history that supports undo and redo. Between them they cover the hard parts: treating rapid changes as a draft so one drag is one undo step, grouping several commands into a single step, restoring a removed item to its original position, and keeping the history within a memory limit.

Practice: Undo Redo History, Command Undo Stack, and Undoable User Table.

State and data utilities

Tagged by members

The remaining tagged questions are utilities an editor relies on: copying nested objects so changes stay isolated, applying an update described as a spec to immutable state, and a key-value store with nested transactions plus undo and redo.

Practice: Deep Clone, Spec Driven Update, and Transactional Record Store.

05

Figma frontend system design

No member has reported a Figma system design round yet. The best public description is from 2021, when Figma engineers said they want to understand how a candidate would collaborate with them in an architecture or system design exercise. They described sharing a prompt in a FigJam board, asking the candidate to map out a hypothetical architecture, and then asking for the code that would make it work, in the same board.

That description is several years old, so confirm the current format with your recruiter. If you do get a design round, expect it to stay close to what Figma builds. These are the closest practice problems:

In each one, be ready to explain how the document is stored in the client, how an edit travels to other users, and what happens when two people change the same object.

06

Behavioral interview at Figma

Figma’s careers site says software engineering candidates have a behavioral interview with a member of the team, and that the onsite includes walking through your background with a potential mentor or manager.

Prepare three stories you can tell in two minutes each: a project you drove from idea to launch, a disagreement about a technical or product decision and how it was settled, and a mistake in production and what you changed afterward. For each, be specific about what you did, not what the team did.

07

How to prepare for the Figma frontend interview

Spend most of your time on the three themes that show up in the tagged questions, and keep general data structures fresh because Figma names them directly.

Days Focus Practice
1 to 2 Canvas geometry and ordering Sticky Note Order, Scanned Receipt Lines
3 to 5 Styled text ranges Paint Style Runs, Slice Styled Text, Patch Text Styles
6 to 7 Undo and redo Command Undo Stack, Undo Redo History
8 to 9 Nested state and copying Deep Clone, Spec Driven Update
10 to 12 System design Design Figma, Design a Whiteboard App
13 to 14 Behavioral stories and a timed mock One full question out loud in 45 minutes, then your three stories

If you have interviewed at Figma, add your report. Each new report makes this guide more specific.

08

Figma frontend interview FAQ

What does Figma ask in frontend interviews?

The questions members have tagged with Figma are small editor problems: ordering shapes on a canvas, editing ranges of styled text, and undo and redo. Figma itself describes its coding interview as language-agnostic and focused on data structures and algorithms.

Does Figma ask LeetCode-style questions?

Figma says its software engineering coding interview focuses on data structures and algorithms, so yes, that skill is tested. The one member report and the tagged questions suggest the problems are framed around design-tool tasks, not abstract puzzles.

What language should I use in a Figma coding interview?

Figma describes the coding interview as language-agnostic. For a frontend role, JavaScript or TypeScript is the natural choice. Confirm with your recruiter if a round expects a specific framework.

Is there a system design round at Figma?

No member has reported one yet. In 2021, Figma engineers described an exercise where candidates map out an architecture in FigJam and then write the code for it. Ask your recruiter whether your loop includes it.

How many rounds are in the Figma interview?

Figma lists an application, a recruiter screen, a skill assessment for some roles, and a virtual onsite with technical and non-technical interviews. The exact number of onsite rounds for frontend roles is not confirmed by member reports yet.