Figma Software Engineer interview questions

6 Software Engineers have shared notes from their Figma interviews, with the questions they were asked in each round. That is 46% of the 13 Figma interview notes on Screna AI.

6 Software Engineer interview notes

Figma·Software Engineer·Technical Phone Screen

May 2026
Figma coding interview with two parts to the same problem, starting with a rectangle resize distribution algorithm and then extending it to handle y-coordinate preservation. The second part is where things get interesting and probably where most people trip up.
  • You have multiple rectangles each with a height (minimum height is 1). Given a resize value, if positive distribute it evenly across all rectangles. If negative, reduce heights as evenly as possible while keeping each height at or above 1. For example: resize=-12 with heights [3,5,10,9] should produce [1,1,7,6].
  • Extend the previous solution: each rectangle now also has a y-coordinate. After resizing, the relative positions between rectangles must be preserved. Note that relative position is not just the difference in y values but needs to account for rectangle heights.

“The positive case is basically free, just divide and add.”

View Post

Figma·Software Engineer·Technical Phone Screen

May 2026
Figma SWE interview focused on designing a layered drawing editor with full undo/redo support. Pretty deep on data structures and edge case handling, more than I expected for what sounded like a scoped coding question.
  • Design and implement a layered image editor that supports adding, removing, reordering, and editing layers, plus undo and redo functionality. How do you handle edge cases like undo with an empty history or a new operation invalidating the redo stack?

“I started with the obvious command pattern and two stacks, which was fine, but then they pushed on the snapshot vs reverse-op tradeoff and I kind of fumbled it.”

View Post

Figma·Software Engineer·Technical Phone Screen

May 2026
Figma software engineering interview focused on a stateful API design problem, specifically extending a document layer object with undo/redo functionality. The question had real depth to it and required thinking carefully about data structure invariants and edge cases rather than just writing code.
  • You're given an existing document layer API with apply(), batch(), and undo() methods. Design and implement a redo() method, and reason through the expected behavior for edge cases like undo-then-redo, undo-then-new-apply, and multiple consecutive undo/redo calls.

“This took me longer to get right than I expected.”

View Post

Figma·Software Engineer·Technical Phone Screen

Apr 2026
Figma coding screen for a software engineer role. The problem was about extending a document layer object with batch and undo functionality, and the memory-efficiency constraint is what made it actually interesting.
  • You're given a Document Layer object with apply(key, value) and get(key) methods. Implement batch() to mark the start of a tracked batch, and undo() to revert all changes made since the last batch() call. The constraint is memory efficiency: for each key touched in the batch, only store the original value it had before the batch started, not every intermediate change.

“The naive approach I almost went with was just logging every single apply() call in order.”

View Post

Figma·Software Engineer·Technical Phone Screen

Apr 2026
Figma software engineer interview focused on designing a document layer with a clean property API, then pushing the design further into batch operations, undo/redo, and history compaction. More of a systems thinking exercise than a pure coding one, which I wasn't fully expecting.
  • Design and implement a Document Layer object with apply(key, value) and get(key) methods, where apply sets or overwrites a property, deletes it when value is None, and get returns the current value or None if absent.
  • How would you extend this design to support batching multiple property changes atomically, implementing undo/redo via an operation log, and compacting history to save memory?

“The core implementation wasn't bad.”

View Post

Figma·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Figma SWE system design round focused on building an async job scheduler, with a big emphasis on fault tolerance and exactly-once execution semantics. The interviewer was pretty relaxed and conversational, and the question felt manageable if you'd done any prep on distributed job queues.
  • Design an async job scheduler that supports two job types: one that executes immediately and one that executes after a specified delay (e.g., after 1 hour).
  • How do you guarantee exactly-once execution for jobs in a distributed scheduler?
  • What happens when a worker node fails partway through executing a job?

“Had seen a similar problem in prep materials so the basic structure came quickly.”

View Post