Figma Interview Questions — Page 1

Figma·Machine Learning Engineer·Technical Phone Screen

Apr 2026

Figma ML engineer interview with a coding problem centered on undo/redo behavior in a layer editor. The problem was deceptively tricky once batched operations entered the picture.

You're building a layer/document editor (think Figma-like) that supports mutating operations and an Undo command. Implement Redo such that it re-applies the most recently undone operation, handles batched operations as atomic units, and invalidates the redo stack whenever a new mutation occurs after an Undo.

“The basic redo stack wasn't bad, two stacks, push to redo on undo, pop from redo on redo, clear redo on new mutation.”

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 had some teeth to it. Nothing technically demanding but you need to actually know why you want to work there or it shows.

Tell me about the most challenging project you've worked on. Walk me through the scope, your role, and what you took away from it.
What specifically draws you to Figma and its products?
What are you looking for in your next role?
How do you think about AI products right now and where do you see them going?

“I had a story ready but I rambled on the scope part way longer than I should have.”

View Post

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

Apr 2026

Figma ML engineer interview with a meaty system design question around building a text-to-HTML generation service. Covered a lot of ground, from model training to serving infrastructure, and I felt pretty good about some parts and totally lost on others.

Design a service that takes a natural language description of a webpage and generates the corresponding HTML (and optionally CSS and JS). Walk through the full system: model choice and training, alignment, evaluation, and serving.

“This one had a lot of layers.”

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 recommender from scratch, and they really wanted you to drive the whole thing end to end without much prompting.

Design a home feed recommendation system for a large consumer app. Walk through the full pipeline from problem framing to serving infrastructure.
How would you frame the ranking problem as a multi-task learning setup, and what targets would you optimize for?
How do you handle freshness and diversity in the re-ranking stage without tanking relevance scores?
What does your serving pipeline look like, and how do you meet latency requirements across the retrieval, ranking, and re-ranking stages?

“This is the kind of question where you can either go broad and shallow or try to go deep on one layer and run out of time on everything else.”

View Post

Figma·Software Engineer·Technical Phone Screen

Apr 2026

Figma software engineering interview focused on a stateful API design problem. The core challenge was extending an existing document layer with undo/redo semantics, which sounds manageable until you start thinking through all the edge cases around batch invalidation.

You're given an existing Document Layer API with apply(), batch(), and undo(). Design and implement a redo() method, and reason through the full interaction between all four operations including edge cases like consecutive undos, redo after new mutations, and state invariants.

“This one took me a while to get off the ground.”

View Post

Figma·Software Engineer·Onsite - Behavioral / Leadership

May 2026

Behavioral round at Figma for a software engineer role. Four questions, all pretty standard conflict and leadership territory, but the trade-off one tripped me up more than I expected.

Tell me about a time you resolved a conflict with a teammate or stakeholder.
Describe a situation where you had to lead or influence a team without having any formal authority over them.
Walk me through a professional failure and what you took away from it.
Tell me about a time you had to make a difficult trade-off. How did you decide?

“I had a decent story ready but fumbled the outcome part.”

View Post

Figma·Software Engineer·Onsite - System Design / Architecture

May 2026

Figma system design round focused on building a document property layer from scratch. The core problem was deceptively simple but the follow-up discussion about extensibility is where things got interesting.

Design a Document Layer object that supports applying property changes to a document. It needs an apply(key, value) method that sets or deletes properties, and a get(key) method that returns the current value or None if absent. Then discuss how you'd extend it to support atomic batch updates, undo/redo, and history compaction.

“The basic apply/get part took maybe five minutes and I was feeling pretty good about myself.”

View Post

Figma·Software Engineer·Onsite - Behavioral / Leadership

May 2026

Figma software engineer interview with a behavioral question that sounds straightforward until you're actually in it trying to figure out how much to say without coming across as either a know-it-all or someone who has nothing to offer.

Tell me about a time you deliberately held back your expertise and followed the hiring manager's or stakeholder's lead. How did you read the room, calibrate how deep to go, and still show you were worth hiring?

“This one is sneaky because your instinct is to prove yourself, and the whole question is asking you to describe a time you didn't do that.”

View Post

Figma·Data Scientist·Technical Phone Screen

May 2026

Prep material for a Senior Data Scientist screen at Figma, focused almost entirely on the self-introduction pitch. The content is essentially a structured 90-second script template with specific metric targets and narrative beats to hit.

Give a structured 90-second self-introduction covering your background, two product analytics wins with concrete metrics, a cross-functional collaboration example, why you want to work at this company specifically, and what you plan to accomplish in your first 90 days.

“This is the classic opener but the version they seem to want here is way more loaded than usual.”

View Post

Figma·Software Engineer·Onsite - System Design / Architecture

May 2026

Figma system design round focused on building an async job scheduler from scratch. The reliability and failure handling portion was where things got interesting, and honestly a bit uncomfortable.

Design an asynchronous job scheduler that supports both immediate jobs and delayed/scheduled jobs, where delayed jobs run as soon as their scheduled time arrives.
How does your design handle worker crashes, scheduler failures, retries, and duplicate execution? Can you actually achieve exactly-once execution?

“I started with the obvious stuff: a queue for immediate jobs, a separate store for delayed ones with a polling loop to promote them when their time comes.”

View Post