Figma Interview Process 2026: CoderPad, Design Critique & Timeline
Figma interview process 2026: recruiter and hiring manager calls, a 1-hour CoderPad screen, portfolio review, design critique, the onsite loop and USD pay.
Last updated: October 2026
TL;DR
The Figma interview process is a 30-minute recruiter screen, a hiring manager call of about 45 minutes with a values component, a 1-hour technical screen (CoderPad for engineers, a portfolio review for designers, a product case for PMs), then a virtual onsite of about four to five interviews, with an extra director or executive round for staff-level and some final candidates. Candidates report about 2-5 weeks from recruiter call to decision. Rehearse the hiring manager, project deep dive and portfolio rounds in OphyAI Interview Practice, drill Figma-style coding and collaborative-editing design prompts in OphyAI Coding Interview, and use OphyAI Interview Copilot for real-time answer suggestions on the live calls.
Quick Answer: Figma Interview Process
| Stage | What to prepare |
|---|---|
| Recruiter screen (about 30 minutes) | A specific “why Figma” answer tied to a product you use (Design, FigJam, Dev Mode, Slides, Make) and a 60-second career story. |
| Hiring manager call (about 45 minutes) | Two deep project stories with numbers, plus examples that map to Figma’s values. |
| Technical screen (about 1 hour) | Engineers: a practical, Figma-flavored CoderPad problem (layers, state, undo and redo). Designers: a portfolio review. PMs: a product case. |
| Virtual onsite (about 4-5 interviews) | Applied coding, system design, a project deep dive and a behavioral round for engineers; case study presentation, design critique and cross-functional rounds for designers. |
| Director or executive round (some candidates) | A behavioral conversation with a director, VP or C-suite leader about scope, judgment and why this team. |
| Offer | Level, base, equity (Figma is public since July 2025) and the posted hub pay range. |
Action Plan: Prepare for Figma by Round
| Round | What Figma tests | What to do before the interview |
|---|---|---|
| Recruiter screen | Motivation, role fit, logistics, communication | Use the product for a week, pick two features you would change and say why |
| Hiring manager call | Ownership, impact, values, how you work with designers or engineers | Prepare six STAR stories, two with a clear metric and one about feedback you acted on |
| CoderPad screen | Clean, working code on an applied problem, narrated out loud | Build a layer store with undo, redo and batched edits in 45 minutes, talking throughout |
| Portfolio review | Craft, process, and whether your story includes trade-offs and failures | Cut to two or three case studies, each with problem, constraints, decisions and outcome |
| System design | Real-time collaboration, sync, conflict resolution, large-document performance | Practice a multiplayer editor and a comments system on a whiteboard, trade-offs first |
| Project deep dive | Depth on something you built, with numbers | Prepare one project you can defend down to the data model and the mistakes |
| Design critique / app critique | Taste, structured feedback, user empathy | Critique two apps out loud in 10 minutes each: user, goal, what works, what you would change |
| Behavioral / values | Collaboration, initiative, humility, feedback | Map one story to each value: Build community, Run with it, Love your craft, Grow as you go, Play |
If you only have one week, engineers should split it between applied coding with undo and redo state and one collaborative-editing design prompt; designers should rebuild the portfolio presentation and rehearse one live critique. Most rejections in candidate reports come from long, under-specified coding prompts that ran out of time, or from portfolio stories that showed final screens without the reasoning.
What Makes Figma Different
Figma makes the collaborative design platform that much of the software industry uses to design and hand off products, and it now spans FigJam, Dev Mode, Slides and AI tools. It priced its initial public offering at $33.00 per share on July 30, 2025 and listed on the New York Stock Exchange as FIG, according to Figma’s own announcement. Its Form 10-K reports about 1,886 full-time employees at the end of 2025, up from 1,646 in its S-1 as of March 31, 2025, so it is still a mid-sized company where interviewers often meet candidates for teams they know well. Built In lists hub offices in San Francisco, New York City, Berlin, Paris, Tokyo and London, with remote employees across the US.
The company’s product shapes the interview more than at most software employers. Interview prep guides consistently describe coding prompts built around Figma-like problems (layers, properties, history) and design rounds about real-time collaboration, and designers are expected to show deep fluency in the tool they are applying to build.
Traits that shape what interviewers look for:
- Five stated values. Figma’s careers page lists Build community, Run with it, Love your craft, Grow as you go, and Play. Its Code of Conduct frames Grow as you go around giving and receiving direct feedback with humility and curiosity. The hiring manager call reportedly includes an explicit values component.
- Collaboration as a test, not a slogan. A Paraform analysis of Figma’s hiring says it favors live, collaborative sessions over solo tests, including pair programming with a Figma engineer and design sessions where candidate and interviewer analyze an existing product together.
- Craft. “Love your craft” shows up as detailed questions about why you made a specific choice, whether that is a data structure, a type scale or a pricing slide.
- Interviewers drawn from a pool. According to one prep guide, panelists are randomly selected from a trained pool, except the hiring manager and any executive screen, so every round must stand on its own.
OphyAI Interview Copilot gives real-time answer suggestions and a live transcript during Zoom, Microsoft Teams and Google Meet interviews. In the desktop app its window is excluded from screen sharing, though not from your webcam or a person in the room.
Interview Process Overview
Figma has not published a round-by-round schedule. The table combines third-party prep guides with candidate reports on Glassdoor and 1Point3Acres, which vary by team, level, office and year.
| Stage | Format | Duration | Timeline |
|---|---|---|---|
| Recruiter screen | Video or phone call | About 30 minutes | Week 1 |
| Hiring manager call | Video call, experience plus values | About 45 minutes | Week 1-2 |
| Technical screen | CoderPad (engineering), portfolio review (design), product case (PM), mock pitch prep (sales) | About 1 hour | Week 2 |
| Virtual onsite | 4-5 interviews, sometimes split across 2-3 days | About 4-5 hours total | Week 3-4 |
| Director or executive round | Behavioral, with a director, VP or C-suite leader | About 30 minutes in one report; varies | Week 4-5 |
| Offer | Recruiter call, then written offer | Varies | Week 4-6 |
Candidate-reported timelines range from about two weeks (one London engineering report) to six weeks (a product manager report). One prep guide puts the average for software engineers at about 24.5 days, and Glassdoor shows an average difficulty of about 3 out of 5, with roughly 46% of candidates rating the experience positive (candidate-reported, undated aggregate).
Recruiter screen. Expect “Why Figma?”, your background, and logistics. Generic praise for the tool is the weak answer; name a workflow you use, a feature that changed how your team works, and the team you are applying to. Record a 60-second introduction in OphyAI Interview Practice and cut anything that does not connect to the role.
Hiring manager call. About 45 minutes going deeper into your experience, plus questions about how you work and Figma’s values. Prepare a mock with follow-ups in OphyAI Interview Practice so the second and third “why?” questions do not catch you out.
Technical screen. For engineers, a one-hour CoderPad session. Prep guides describe Figma-flavored practical problems at roughly LeetCode medium difficulty, often involving complex state, tree structures or undo and redo logic, and some candidates say the prompts were long for the time. Rehearse an applied problem end to end in OphyAI Coding Interview. In the live session, Coding Copilot in the desktop app snaps the CoderPad problem and shows the code, a dry run and the Big O. Our Figma CoderPad interview guide works through the undo and redo layer problem with a code sketch and a time plan.
The Portfolio Review and Design Critique
The stage most specific to Figma is the design loop, because candidates are being judged by the people who build the design tool itself. Third-party guides describe about five rounds for product designers: a portfolio review with the recruiter screen, a hiring manager screen, a design exercise done in Figma (a whiteboard-style prompt or a product problem, usually not a take-home), and a virtual onsite with a case study presentation to a panel, a design critique session, a cross-functional interview with a PM or engineer, and a values interview. Paraform’s write-up describes the collaborative format: candidate and interviewers analyze an existing product or use case together, or the candidate presents a design statement and a solution. That is effectively an app critique, so prepare for one even if the invite calls it something else. Our Figma product designer interview guide covers each design round, the posted pay range and example prompts in more depth.
Figma’s own recruiting blog gives the portfolio brief: lead with strong work, tell complete stories, include obstacles you faced, your process, what you learned and what you might have done differently, and note that unshipped concepts can reveal a lot about how you think.
What they test: craft (layout, type, interaction detail), the reasoning behind each decision, how you respond to pushback, tooling fluency (components, variables, auto layout, prototyping) and how you work with PMs and engineers. Red flags: case studies that show only final screens, no metric or outcome, blaming partners for constraints, defensiveness when the panel challenges a choice, and a critique that is a list of opinions with no user or goal. How to prepare: pick two or three case studies and present each in 10-12 minutes with a clear problem, constraints, options you rejected and the result; then critique two products out loud using the same frame (who is the user, what is the goal, what works, what you would change first and why). Run the presentation as a timed mock in OphyAI Interview Practice and answer its follow-up questions without slides.
Role-Specific Breakdowns
Software Engineer
Reported loops include two applied coding interviews, one or two system design interviews, a technical project deep dive and a behavioral interview, sometimes with an engineering manager. One prep guide describes the onsite as about four hours; a July 2026 report from a candidate on an AI team described five rounds over three days. Staff and some senior candidates get a behavioral round with a director after the onsite.
What they test: applied coding over puzzle-solving, state management, real-time collaboration architecture (CRDTs or operational transforms, sync, presence, rendering large documents), and depth on your own work. Red flags: coding silently, jumping to code before clarifying the prompt, a design answer that ignores conflict resolution or offline edits, and a deep dive where you cannot explain why the system was built that way. How to prepare: practice a layer store with undo, redo and batched edits; design a multiplayer editor, a comments system and a “most popular files” feature; and pick one project you can defend down to the data model, using our system design interview guide. Run timed coding and design rounds in OphyAI Coding Interview.
Product Designer
See the portfolio and critique section above. Designers should also expect a hiring manager screen about scope and seniority, and a cross-functional interview where a PM or engineer asks how you handled disagreements, scope cuts and handoff. Bring one story about a design you changed after engineering or research feedback. Practice that cross-functional round as a behavioral mock in OphyAI Interview Practice.
Product Manager
One guide and a Glassdoor technical program manager review describe a recruiter screen, a hiring manager call, a panel round, then a final C-suite round for the top candidates. Other guides add a product case and a design partner interview, and one claims many PMs fail when they cannot discuss Figma’s own features in depth (unverified, single source). Glassdoor reviewers mention preparing for business, product and people sense questions.
What they test: product sense for a creative, collaborative tool, prioritization, metrics, and working with designers as peers. Red flags: frameworks with no user, no point of view on Figma’s AI features, and treating designers as executors. How to prepare: take one Figma product area, define its users and a north-star metric, and propose one change with a test plan; our product manager interview questions guide covers the formats. Rehearse the product case in OphyAI Interview Practice using the case format.
Go-to-Market: Account Executive and Sales
Glassdoor reports describe a hiring manager interview, interviews with other account executives, a mock discovery call or a sales pitch with a Figma product demo, a presentation, and a final round with a sales VP or leadership. A Berlin candidate reported about five weeks; a New York candidate described the process as long but said interviewers helped with preparation.
What they test: discovery skills, selling to design, product and engineering buyers, deal strategy and coachability. Red flags: pitching features before asking questions, no quota numbers, and not knowing how Figma is bought (team plans growing into enterprise agreements). How to prepare: script a 30-minute discovery call for a design team moving to an enterprise plan, and bring a deal story with numbers; see our sales representative interview questions. Rehearse the mock discovery call in OphyAI Interview Practice, then use Interview Copilot on the live video round for real-time prompts.
Managers and Other Corporate Roles
A Glassdoor manager candidate described a recruiter screen, a 30-minute hiring manager interview, a 3-hour panel with four interviewers, a presentation to the same group, and a 30-minute interview with the team’s VP. Prepare the presentation as you would a design case study: problem, options, decision, outcome. Simulate the panel follow-ups in OphyAI Interview Practice.
Common Questions with Frameworks
These are representative prompts built from candidate-reported topics and prep guides, not verbatim Figma questions.
1. “Why Figma?” (Motivation)
Approach: One product reason (a workflow Figma changed for you), one team reason (what this team ships) and one growth reason. Avoid “I love design tools” on its own. See how to answer “why do you want to work here”.
2. “Model layers with properties, apply changes, and support undo and redo.” (Coding)
Approach: Clarify operations first. Store layers in a map by ID; record each edit as the changed property’s old and new value rather than a copy of the layer; add a batch commit so several edits undo as one entry; clear the redo stack on a new edit. Test with a short sequence and talk about memory.
3. “Design real-time collaborative editing for a shared file.” (System Design)
Approach: Start from the user action, then the document model, sync protocol, conflict resolution (CRDT versus operational transforms, or a server-authoritative approach), presence, offline edits, persistence and rendering performance. State the trade-offs before the diagram.
4. “Design a system to show the most popular files.” (System Design)
Approach: Define “popular” (views, edits, unique users, time window). Propose event ingestion, a streaming aggregation with decay, per-team privacy filtering and a cached ranking. Discuss staleness and abuse.
5. “Walk me through a project you are proud of.” (Project Deep Dive)
Approach: Context, your role, the hardest decision, what you would change, and a number. Expect the interviewer to go two or three levels deep on one component.
6. “Critique an app you use every day.” (Design Critique)
Approach: Name the user and their goal, what works, the biggest friction, and one change with how you would measure it. Ask questions back; it is meant to be a conversation.
7. “Tell me about a time you received feedback you disagreed with.” (Values: Grow as You Go)
Approach: Use the STAR method: what the feedback was, how you tested it, what you changed and what happened. Show humility without abandoning a well-reasoned position.
8. “Tell me about a time you took initiative without being asked.” (Values: Run With It)
Approach: Pick a problem nobody owned, explain why you moved, how you brought others along and the measurable result.
Culture Fit: Craft and Multiplayer Collaboration
Multiplayer by default. Figma’s product is built around people working in the same file, and interviews mirror that: pair programming, collaborative whiteboarding and critiques you do with the interviewer, not at them.
Craft without ego. Love your craft and Grow as you go sit side by side. Interviewers look for people who care about detail and still change their minds when the evidence says so.
Initiative. Run with it means taking the first step when the path is unclear. Stories where you waited for permission read poorly.
What interviewers screen for: clear thinking out loud, curiosity about the product, specific craft decisions, generous collaboration and comfort with direct feedback.
Compensation Overview (2026 Estimates, USD)
| Role | Base Salary | Total Compensation (Base + Bonus + Equity) |
|---|---|---|
| Early Career Software Engineer (2026 posting, SF/NY hub) | $155,000 (posted) | Base plus equity (not published) |
| Software Engineer (all levels, US) | Varies by level | About $390,000 median (Levels.fyi, candidate-reported, April 2026) |
| Full-Stack Software Engineer (US) | Varies by level | About $506,000 median (Levels.fyi, candidate-reported, August 2026) |
| Software Engineering Manager (US) | Varies by level | About $605,000 median (Levels.fyi, candidate-reported, February 2026) |
| Early Career Product Designer (2026 posting) | $140,000 (posted) | Base plus equity (not published) |
| Product Designer (SF/NY hub postings) | About $149,000-$338,000 depending on posting and level | Not published |
| UX/Product Designer (US) | Varies by level | About $191,000 (L2) to $268,000 (L4) (Levels.fyi, candidate-reported, July 2026) |
| Product Manager (US) | Varies by level | About $364,000 median (Levels.fyi, candidate-reported, August 2026) |
Figma postings state base ranges for the San Francisco and New York hubs and say remote US roles are localized to between 80% and 100% of that range. Posted ranges are base salary only; equity comes on top and, since the July 2025 listing, is in a publicly traded company. Levels.fyi figures are candidate-reported, swing between snapshots, and mix levels, so use the posted range on your specific job plus your level for negotiation. For tactics, see our salary negotiation guide.
Preparation Timeline: 4-6 Weeks
| Week | Focus | Activities |
|---|---|---|
| 1 | Product immersion and story bank | Use Figma Design, FigJam and Dev Mode on a real project. Draft 8 STAR stories, one per value plus impact stories. |
| 2 | Core skill | Engineers: 20-30 applied problems with state, trees and history. Designers: rebuild 2-3 case studies. PMs: one product teardown. Sales: discovery script. |
| 3 | Signature rounds | Engineers: two collaborative-editing design prompts. Designers: two timed critiques and one design exercise in Figma. PMs: product case and metrics. |
| 4 | Deep dive and values | Prepare the project deep dive or portfolio presentation; rehearse values stories with follow-ups in OphyAI Interview Practice. |
| 5-6 | Full loop | Run a full mock onsite, fix weak rounds, prepare questions for the director round and research your posted pay range. |
Common Mistakes
Solving the puzzle but not the product. Figma’s coding prompts are applied. Ignoring edge cases like batched undo or deleted layers costs more than a slightly slower algorithm.
Coding or designing in silence. Collaborative rounds are scored on how you think with the interviewer. Narrate decisions and invite input.
Showing screens, not decisions. Portfolio reviewers want the problem, constraints and trade-offs, including what failed.
A generic system design. A design that never mentions conflicts, presence or document size misses what Figma builds.
Thin product knowledge. Not having used FigJam, Dev Mode or Figma’s AI features is an easy signal to avoid.
Treating the values round as small talk. Values come up in the hiring manager call and a dedicated interview; prepare stories for each.
Prepare for Figma with OphyAI
Figma’s loop rewards people who think out loud, defend craft decisions under follow-up questions and collaborate in real time, all skills that improve with timed rehearsal rather than reading.
Use OphyAI Interview Practice for voice or text mock interviews with follow-up questions, a transcript and per-answer feedback in behavioral, technical, system design and case formats. Use OphyAI Coding Interview, a Premium product, to rehearse live coding and system design rounds. Use OphyAI Interview Copilot in the desktop app for real-time answer suggestions during live Zoom, Microsoft Teams or Google Meet interviews. Start practicing →
Start Your Figma Application
Ready to apply? OphyAI can help at every stage:
- Search for open roles at Figma and similar companies with AI-powered job matching
- Generate a tailored cover letter that highlights your fit for the role, plus follow-up emails and thank-you notes for after your interviews
- Track your application status alongside every other role you’re pursuing
Pair these with Interview Copilot for real-time help in the live interview, or practise first with OphyAI Interview Practice.
Round-by-round guides
- Figma product designer interview: portfolio review, live design critique, example prompts and a 1-week plan
- Figma CoderPad interview: the undo and redo layer problem, batches, a TypeScript sketch and a 3-day plan
Related company guides
- Canva interview guide
- Adobe interview guide
- Atlassian interview guide
- Airbnb interview guide
- Stripe interview guide
Frequently Asked Questions
How many rounds are in the Figma interview?
Most candidates describe seven or eight conversations in total: a recruiter screen, a hiring manager call, a technical screen or portfolio review, then a virtual onsite of about four to five interviews. Staff-level engineers and some final PM or sales candidates add a director, VP or executive round. Figma has not published a fixed count, so ask your recruiter for your loop in writing.
How long does the Figma hiring process take?
Candidate reports range from about two weeks to six weeks, and one prep guide puts the software engineer average at about 24.5 days. Onsites are sometimes split over two or three days, and a final executive round can add a week. A polite check-in with your recruiter after a week of silence is normal and not a bad sign.
What is the Figma CoderPad interview like?
It is a one-hour live coding session, usually in CoderPad, with a practical problem that mirrors a Figma feature rather than a pure algorithm puzzle. Reported themes include layers and properties, tree structures, state machines and undo and redo history. Candidates say prompts can be long, so clarify scope early, write working code first and narrate your trade-offs. Our CoderPad guide has a worked example.
Does Figma give a design take-home?
Third-party guides say most product design roles do not get a take-home. Instead you present your portfolio, complete a live design exercise in Figma, and take part in a design critique or collaborative session analyzing an existing product with the interviewers. Formats change by team and level, so confirm with your recruiter what the exercise involves and how long it runs.
How should I structure my portfolio for Figma?
Follow Figma’s own recruiting advice: lead with your strongest work and tell complete stories, including the obstacles, your process, what you learned and what you would do differently. Unshipped concepts are fine if they show how you think. Two or three deep case studies with clear decisions beat ten polished screens. Rehearse presenting each in about 10-12 minutes.
Is the Figma interview hard?
Glassdoor shows an average difficulty of about 3 out of 5 (candidate-reported). Engineers say the hardest parts are long applied coding prompts and collaborative-editing system design; designers find the critique and panel presentation the hardest. Many reviewers describe friendly, well-organized interviewers, but positive-experience ratings sit under half on Glassdoor’s aggregate.
How much does Figma pay software engineers?
Levels.fyi’s candidate-reported US median for Figma software engineers was about $390,000 in total compensation in April 2026, with full-stack engineers higher. A 2026 early-career engineering posting listed a $155,000 base plus equity for the San Francisco and New York hubs. Remote US roles are localized to 80-100% of the hub range, per Figma postings.
How does OphyAI work in a Figma interview?
Practice the hiring manager, deep dive and portfolio rounds first in OphyAI Interview Practice, which asks follow-up questions and scores each answer. On the live call, Interview Copilot in the desktop app hears the interviewer through system audio and suggests answers in a window excluded from screen sharing. For the CoderPad screen, Coding Copilot reads the problem window and shows the code with a dry run.
Sources and verification notes
Sources checked October 2026. Figma’s own pages (figma.com, its Greenhouse job board) and SEC filings could not be fetched from the research environment (WebFetch failed with DNS errors), so every fact below was checked via search summaries of the listed pages, October 2026; verify on each page before relying on it. Process details from Glassdoor, 1Point3Acres and prep guides are candidate-reported or secondhand and vary by team, level and year.
- Figma, IPO pricing announcement (July 30, 2025) and Business Wire copy: $33.00 per share, NYSE ticker FIG (first-party).
- Figma Form 10-K for fiscal 2025 (SEC), as cited by Yahoo Finance and Makerstations: 1,886 full-time employees at December 31, 2025; 1,646 in the S-1 as of March 31, 2025.
- Figma Careers and Figma Code of Conduct (PDF): the five values and the Grow as you go framing (first-party).
- Figma blog, portfolio advice and Breaking in: landing your first product design role: portfolio storytelling guidance (first-party).
- Built In, Figma company profile: hub offices and hybrid model.
- Figma Greenhouse posting and Base10 copy of Early Career Software Engineer (2026): $155,000 base, hub ranges, 80-100% remote localization. Base10, Early Career Product Designer (2026), Hirebase and Kardow: designer ranges from single, possibly closed postings.
- Levels.fyi, Figma Software Engineer, Full-Stack, Engineering Manager, Product Manager and UX Designer: medians and level ranges (candidate-reported, snapshot dates as noted).
- Paraform, How Figma hires: collaborative interviews, pair programming, design sessions analyzing an existing product.
- Prep guides: Exponent, Interview Query SWE, Interview Query PM, TechPrep, Design Gurus, techinterview.org, CleverPrep product designer and ResumeGeni product designer: round structure, durations, question themes, the 24.5-day estimate (secondhand).
- Candidate reports: Glassdoor, Figma interview reviews, Glassdoor TPM and manager panel report, Glassdoor AE report, 1Point3Acres onsite report: stages, difficulty, timelines and the AE mock pitch (candidate-reported).
Figma does not publish round counts, interview lengths or rubrics.
Tags:
Share this article:
Coding round at Figma? Coding Copilot reads the problem with one hotkey.
In the OphyAI desktop app, Coding Copilot snaps the problem on your screen and returns an approach, working code, edge cases and the Big O, in an overlay left out of screen sharing. It is part of the Premium plan.
On your phone? Practice interview answers in the OphyAI app. Coding Copilot runs in the Mac and Windows app.
Hidden from screen share and recording; a webcam or a person in the room can still see your screen, and the overlay never takes focus from your editor.
Related Articles
Figma Product Designer Interview: 5 Rounds, Portfolio & Live Critique
Company Guides
Figma product designer interview: the reported 5-round loop, portfolio review, live design critique, 5 example prompts, red flags and $169K-$303K posted pay.
Read more →
Figma CoderPad Interview: The Undo/Redo Layer Problem in 60 Minutes
Company Guides
Figma CoderPad interview: the reported 60-minute layer store problem, undo, redo and batch follow-ups, a TypeScript sketch, a time plan and red flags.
Read more →
Cloudflare Interview Process 2026: Orange Cloud, Questions & Timeline
Company Guides
Cloudflare interview process for 2026: recruiter call, team panel, executive calls with the Orange Cloud interview, US pay, sample questions and prep plan.
Read more →