← Back to Directory

Figma

Mid-sized

Screna has 13 Figma interview write-ups. The most reported round is the technical phone screen (7).

13 interview notes · updated Jun 2026

Figma·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Figma ML Engineer interview had a coding round with a grid traversal problem. Pretty standard stuff but worth knowing cold if you're going in.
  • Given a 2D grid where each cell is either land or water, count the number of distinct islands, where an island is a group of land cells connected in four directions.

“Classic grid traversal.”

View Post

Figma·Machine Learning Engineer·Onsite - System Design / Architecture

Jun 2026
Figma ML Engineer system design round, one big open-ended question about building a natural-language-to-HTML generation service. Pretty deep technically, they wanted you to go end to end from model choice all the way through serving and evaluation. Left feeling like I covered the surface but probably undersold some of the harder tradeoffs.
  • Design a system that accepts a natural-language description of a webpage and generates the corresponding HTML (and optionally CSS and JS).

“This one sprawled in every direction.”

View Post

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·Machine Learning Engineer·Onsite - System Design / Architecture

Apr 2026
Figma ML engineer interview with a meaty system design problem centered on document state and undo functionality. The kind of question that sounds straightforward until you actually have to think through the trade-offs.
  • You're given a layer-based document model (think design tool) that supports add, delete, move, and property change operations. Implement an undo feature that reverts the most recent operation. Walk through how you'd record operations and compare inverse-operation logging against full document snapshots.

“I started with snapshots because it felt safe, and the interviewer let me talk for a bit before asking what happens when the document is large.”

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·Machine Learning Engineer·Onsite - System Design / Architecture

Apr 2026
ML system design round at Figma for an MLE role. The whole session was one big open-ended question about building a home feed recommendation system from scratch, covering everything from retrieval to serving. Dense but actually pretty interesting if you've done this kind of work before.
  • Design a home feed recommendation system for a large consumer app. Walk through how you'd frame the problem, generate candidates, rank them, and serve the results at scale.
  • How would you handle candidate generation at scale? What retrieval approaches would you consider and what are the tradeoffs?
  • How would you structure the ranking model, and how do you handle real-time versus batch features in that pipeline?
  • Once you have ranked results, how do you re-rank them before serving? What factors beyond the model score matter?
  • How would you set up the serving infrastructure and measure whether the system is actually working in production?

“This is basically the canonical ML system design question and I still fumbled parts of it.”

View Post

Figma·Product Manager·Hiring Manager Screen

Apr 2026
Hiring manager behavioral panel at Figma, four questions, pretty standard BQ territory but the AI one kept me on my toes. No technical component, just a lot of talking about yourself.
  • Tell me about the most challenging project you've worked on. What was the scope, what was your role, and what did you take away from it?
  • Why Figma specifically? What draws you to the company and the product?
  • What are you looking for in your next role?
  • What's your take on where AI products are heading?

“I had a story ready but I over-indexed on scope and timeline and kind of buried the personal takeaway at the end.”

View Post