RepostedFigma logo

Figma · OA → Phone screen → Onsite

In process

Figma SWE Intern OA and Final Round: 21 Experiences

Software engineer · InternshipBachelor's degreeOct 2026
Shared by

Figma SWE intern OA and interviews, 2020 to 2026: the Byteboard design-doc OA gave way to a 90-minute AI-assisted CoderPad build in the 2027 hiring cycle.

At a glance

  • Process: a written application, then an OA, then a final of two technical interviews and one behavioral chat (06, 07, H01, H02). Through 2025 the OA was Byteboard: about 30 minutes on a design document, then about 60 minutes coding in a small codebase (10). From August 2026 it was a 90-minute AI-assisted CoderPad (01, 02), and one 2027-cycle candidate skipped the OA for two live interviews (04).
  • Asked recently: building features from a scope and design doc with AI help (01, 02, 03), Revision History (05), a browser editor design (06), Symmetric Binary Tree (07) and AI-assisted debugging in TypeScript (04).
  • Difficulty: time was the common complaint. The design-doc part felt tight (09, 10, 11), and one onsite candidate felt short on graphics knowledge (07). Instructions reportedly said candidates were not expected to finish every part.
  • Practise first: Revision History (05) and Design a Browser-Based Graphics Editor (06).

Coverage: Figma Software Engineer Intern candidates, mostly in the U.S. (San Francisco and New York where named). OAs, recruiter check-ins and final rounds. Eleven reports from September 2024 to October 2026, covering the Summer 2025 to 2027 cycles, plus ten older reports from September 2020 to October 2023 in History.

What came up

The OA has always been about working inside a project rather than solving a puzzle: read a plan, then build part of it. In 2026 the same idea carried over into an AI-assisted build.

Topic Reports Last seen
Building features in a project or codebase 6 of 11 Oct 2026 (report date)
AI-assisted coding 5 of 11 Oct 2026 (report date)
Design document reading and comments 4 of 11 Oct 2026 (report date)
Data structures and algorithms interview 3 of 11 Summer 2026 cycle
Why Figma and project questions 2 of 11 Summer 2026 cycle
Browser editor architecture 1 of 11 Summer 2026 cycle

A candidate can appear in more than one row. One further report, with no date or candidate detail, said an interviewer kept asking how a working solution handled extra edge cases.

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Revision History (undo, redo and batches) 1 —
Symmetric Binary Tree 1 Feb 2026

System Design

Question Reports Last seen
Design a Browser-Based Graphics Editor 1 Summer 2026 cycle

AI Coding

Question Reports Last seen
Implement several features from a scope and design document with AI 1 Oct 2026 (report date)
Build a system from scratch with AI and explain the architecture 1 Sep 2026 (report date)
AI-assisted debugging in an existing TypeScript codebase 1 Sep 2026

Behavioral (BQ)

Question Reports Last seen
Why Figma? 2 Summer 2026 cycle
Which engineering teams interest you most? 1 Sep 2025 (report date)
The project that best shows your programming ability (practice) 1 Sep 2025 (report date)

11 detailed candidate timelines, loops, and screens

01: Features from a scope and design document

Report date: October 2026 · Role: SWE Intern, 2027 cycle · Result: Not disclosed

  1. The OA was AI-assisted. The candidate got a scope and a design document and used the available AI to implement several features.
  2. Their takeaway was to break the work into small pieces, talk through tradeoffs and check alternate and edge cases out loud.
  3. They had no result yet when they posted.

02: A 90-minute AI build that ended after the OA

Report date: September 2026 · Role: SWE Intern, 2027 cycle · Result: Rejected after OA

  1. The CoderPad ran 90 minutes, after recruiter outreach.
  2. The candidate built a system from scratch with AI help and kept explaining the architecture and choices, rather than accepting one unexplained answer from the tool.
  3. They felt it went well but did not move on.

03: "Not a LeetCode test"

Report date: August–October 2026 · Role: SWE Intern, 2027 cycle

  1. This candidate said the new OA was not a traditional LeetCode test.
  2. They described what it measured as AI fluency.

04: OA skipped, two live interviews instead

Report date: September 2026 · Role: SWE Intern, 2027 cycle · Status: In process

  1. The candidate went straight to two back-to-back interviews with no OA.
  2. The first was AI-assisted debugging in an existing TypeScript codebase; the second was data structures and algorithms. The completed-interview details were not shared.

05: Revision History, with the API left open

Report date: not given · Role: SWE Intern

  1. The task was Revision History: build edit history for a document editor and support several operations through a small API.
  2. The prompt suggested method names, but candidates could design a different API if it made more sense.
  3. AI tools were allowed, and candidates still had to explain their choices. The exact prompt, examples and tests were not shared; the linked problem adds undo, redo and grouped edits as a close practice version.

06: Summer 2026 offer, with a browser editor design

Cycle: Summer 2026 · Role: SWE Intern · Location: San Francisco · Result: Offer

  1. Byteboard came before the onsite.
  2. A senior engineer ran a relaxed 30-minute behavioral conversation.
  3. One technical interview was on data structures. The other asked the candidate to architect a browser editor; no scale, rendering or persistence requirements were shared.
  4. The candidate felt domain knowledge helped.

07: Summer 2026 onsite that exposed a graphics gap

Cycle: Summer 2026 · Role: SWE Intern · Location: San Francisco · Result: No offer

  1. The candidate reached the onsite and felt the behavioral round went fine.
  2. The two questions they kept were why they applied to Figma and checking whether a binary tree is symmetric.
  3. They thought limited graphics knowledge hurt them in the technical rounds.

08: Three of three steps, then the final

Report date: November 2025 · Role: SWE Intern, Summer 2026 · Result: Advanced after OA

  1. The candidate finished all three implementation steps of the Byteboard.
  2. After about ten days with no word, they got the final-round invitation. The final questions and outcome were not shared.

09: Two of three steps, then a quick no

Report date: November 2025 · Role: SWE Intern, Summer 2026 · Result: Rejected after OA

  1. The candidate finished two of the three steps and wrote up the unfinished one.
  2. They felt their code comments were decent but the design-document work was weak.
  3. They submitted on a Tuesday night and were rejected on Friday morning.

10: The 2025 New York time crunch

Report date: September 2025 · Role: SWE Intern · Location: New York · Result: Rejected after OA

  1. The application asked written questions: why Figma, which engineering teams they preferred, and the project that best showed their programming ability (practice).
  2. The Byteboard gave 30 minutes for a technical design document and 60 minutes to implement related functionality.
  3. The document part felt too short to think carefully before coding, and the candidate did not advance.

11: Product features instead of puzzles

Report date: September 2024 · Role: SWE Intern, 2025 cycle · Result: Not disclosed

  1. Candidates first got an online process form and a candidate slide deck.
  2. The assessment asked them to implement product features from a design challenge, not isolated algorithm questions.
  3. One person who finished it called it reasonable, though time was a concern.

History (before November 2023)

H01: 2023 offer after a two-part OA

Report date: October 2023 · Role: SWE Intern · Location: San Francisco · Result: Offer

  1. A recruiter questionnaire covered logistics.
  2. The roughly two-hour Byteboard paired design-document comments and recommendations with related coding.
  3. The final ran about three hours: a 30-minute behavioral and two 60-minute technical interviews, around LeetCode medium on graphs, trees and hash maps.

H02: A three-week 2023 process

Interview date: September 2023 · Role: SWE Intern · Result: No offer

  1. Applied online, did the Byteboard, then had a recruiter check-in.
  2. Three back-to-back finals followed: two technical and one behavioral, which asked why Figma. The whole process took about three weeks.

H03: An OA graded on logic and efficiency

Report date: 2023 · Role: SWE Intern

  1. This OA-only report named the areas it tested: data structures, iterative logic and code efficiency. No runnable prompt was kept.

H04: BFS, recursion and two unfinished solutions

Report date: October 2022 · Role: SWE Intern · Result: No offer

  1. The final had two technical interviews and one behavioral.
  2. One problem was BFS on a tree; the other was described only as recursion.
  3. The candidate finished neither completely and rated the difficulty medium.

H05: A Byteboard with an O(log n) search

Report date: 2022 · Role: SWE Intern

  1. This candidate completed the Byteboard and remembered writing an O(log n) search over ordered entries. The entry format and return value were not kept.

H06: Classes, methods, design, then values

Report date: October 2021 · Role: SWE Intern · Result: No offer

  1. Byteboard first, then an onsite with two coding interviews and one technical design interview.
  2. The coding rounds supplied a class structure and asked for particular methods using standard data structures and some algorithms.
  3. A 30-minute engineering-values chat with a hiring manager closed the loop.

H07: The fully narrated Summer 2021 journey

Report date: February 2021 · Role: SWE Intern, Summer 2021 · Result: Rejected after the final

  1. OA part 1, about 40 minutes: she read a project proposal with several implementation options, left comments, answered teammates' comments and wrote a conclusion choosing one approach.
  2. OA part 2, about 70 minutes: in Python, she downloaded a small multi-file codebase and implemented functions tied to the proposal. She finished the three highest-priority functions of four and explained the fourth in comments.
  3. A recruiter later said the rubric flagged attention to detail while recognizing strong coding. The advice for the final was to ask questions, test the code and work collaboratively.
  4. Final: a CoderPad round with several classes, tests and missing functions based on a real engineering problem; a database-oriented design conversation, where the prep packet said interviewers could teach any SQL needed; and a second codebase round implementing several functions.
  5. She was rejected a few days later. Her reflection: communicating and coding were harder when so much unfamiliar code arrived at once.

H08: Search highlighting and file organization

Report date: early report (around 2021) · Role: SWE Intern

  1. This candidate remembered two Figma-flavored feature prompts: search-result highlighting and file organization.
  2. The contract, query rules and rendering details were not kept.

H09: The 2020 non-LeetCode onsite

Report date: September 2020 · Role: SWE Intern · Result: No offer

  1. Byteboard, then two technical coding interviews and one system design interview.
  2. The questions were Figma-specific rather than standard LeetCode, but still used familiar structures such as dictionaries and binary search trees.

H10: Document and layer operations

Report date: September 2020 (sighting date) · Role: SWE Intern

  1. An early report described document and layer operations on a Figma-style model. The original API was not kept.

Patterns across the reports

  1. Plan first, then code. Every Byteboard account paired a design document with implementation (09, 10, H01, H07), and the 2026 AI version still started from a scope and design doc (01).
  2. Explain the AI's work. Both detailed 2026 OA reports stressed explaining architecture and tradeoffs rather than trusting the tool (01, 02), and 05 allowed AI but still expected reasons.
  3. Two technical plus one behavioral. The final had that shape in 06, 07, H01, H02 and H04.
  4. Finishing helped but was not required. One candidate who finished three of three steps advanced (08); one who finished two of three did not (09). The 2021 candidate who finished three of four reached the final (H07).

Common questions

What is the Figma intern OA in 2026?

A 90-minute CoderPad where candidates built features with AI help from a scope and design document (01, 02). One 2027-cycle candidate skipped it and went to two live interviews (04).

Is the Figma OA LeetCode?

No report described it that way. Candidates called it product feature work (11) or "not a traditional LeetCode test" (03).

How long is the Figma Byteboard OA?

Ninety minutes in 2025: 30 for the design document and 60 for code (10). Earlier versions ran about two hours (H01) or 110 minutes (H07).

What is the Figma intern final round like?

Usually two technical interviews and one behavioral (06, 07, H01). Recent technical rounds covered data structures, a browser editor design and a symmetric tree check (06, 07).

How long does Figma take to reply after the OA?

One candidate got the final invite after about ten days (08); another was rejected three days after submitting (09).

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.