RepostedFigma logo

Figma · OA → Onsite

In process

Figma SWE Intern OA Questions: 25 Experiences

Software engineer · InternshipBachelor's degreeSep 2026
Shared by

Figma SWE intern reports, 2020 to the Winter 2027 cycle: the design-doc Byteboard OA gave way in August 2026 to a 90-minute CoderPad with built-in AI.

At a glance

  • Process: resume review, an OA, then a final of two technical rounds and one behavioral (H02, H03). Byteboard was the OA through the Summer 2026 cycle; for Winter 2027 Figma moved to a 90-minute CoderPad (04, 05). One Winter 2027 candidate skipped the OA and went straight to two interviews (02).
  • Asked recently: a CoderPad task to design a solution and build it with built-in AI (05), multiple choice plus problem solving (01), AI-assisted debugging in a TypeScript codebase followed by DSA (02), and Byteboard design-doc comments plus coding (07–13).
  • Difficulty: the Byteboard clock was the common complaint, especially the design-doc part (08, 12, 13). The CoderPad AI task felt manageable to one candidate (05). Figma's stated turnaround after CoderPad is about 10 business days (03).

Coverage: Figma Software Engineer Intern candidates, mostly in the U.S. (New York, San Francisco and Atlanta where named). OAs, recruiter steps and final rounds. Thirteen reports from September 2024 to September 2026, covering the 2025, Summer 2026 and Winter 2027 cycles, plus twelve older reports from September 2020 to April 2024 (2023 cycle) in History.

What came up

Most recent reports are about the OA itself. Byteboard asked candidates to critique a design document and then code against it; its replacement keeps the build-something idea but adds AI.

Topic Reports Last seen
Byteboard design-doc and coding OA 8 of 13 May 2026 (report date)
CoderPad OA 4 of 13 Sep 2026 (report date)
AI-assisted design or debugging 2 of 13 Sep 2026 (report date)
Multiple choice and problem solving 1 of 13 Sep 2026 (report date)
Data structures and algorithms interview 1 of 13 Sep 2026 (report date)
Mock PM response on a mock project 1 of 13 Oct 2025

A candidate can appear in more than one row.

Questions we found

AI Coding

Question Reports Last seen
AI-assisted debugging in an existing TypeScript codebase 1 Sep 2026 (report date)
Design a solution and build it with the built-in AI 1 Aug 2026 (report date)

Other

Question Reports Last seen
Write a response to a mock PM about a mock project 1 Oct 2025

13 detailed candidate timelines, loops, and screens

01: CoderPad with multiple choice and problem solving

Report date: September 2026 · Role: SWE Intern, Winter 2027 · Result: Advanced

  1. The CoderPad OA had multiple-choice questions and problem solving.
  2. The candidate moved on to interviews but did not share topics, language or AI rules.

02: No OA, straight to two interviews

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

  1. The candidate skipped the OA entirely.
  2. They got two back-to-back interviews: AI-assisted debugging in an existing TypeScript codebase, then data structures and algorithms.

03: Waiting past the stated turnaround

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

  1. This candidate had failed the Summer 2026 OA and reapplied.
  2. More than 10 business days after finishing the CoderPad, which is Figma's stated turnaround, they were still waiting.

04: A 90-minute CoderPad invite

Report date: September 2026 · Role: SWE Intern, Winter 2027

  1. The candidate received a 90-minute CoderPad OA invite. They did not describe the questions.

05: Design it, then build it with AI

Report date: August 2026 · Role: SWE Intern, Winter 2027 · Result: Not disclosed

  1. The candidate confirmed Figma had moved from Byteboard to CoderPad.
  2. The task was to design a solution and use the built-in AI to code it.
  3. They found it manageable and quite different from regular LeetCode.

06: Through resume review, out at Byteboard

Report date: May 2026 · Role: SWE Intern, Summer 2026 · Result: Rejected

  1. The candidate passed resume review but failed the Byteboard.
  2. The recruiter encouraged them to apply again next cycle.

07: All three steps, then the final

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

  1. The candidate finished all three steps of the OA.
  2. The final-round invite came about ten days later.

08: Two of three steps, rejected by Friday

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

  1. The candidate finished two of three steps and felt their comments were decent, but their design-doc section was weak.
  2. They submitted on Tuesday night and were rejected on Friday morning.

09: Two of three, with a note on the last

Report date: November 2025 · Role: SWE Intern, Summer 2026 · Result: Not disclosed

  1. The candidate finished two of three steps and used the optional text box to explain the last one.
  2. The instructions said candidates were not expected to finish everything.

10: New York: 90-minute Byteboard and a mock PM task

Interview date: September–October 2025 · Role: SWE Intern · Location: New York · Result: No offer

  1. This entry combines two closely matching New York reports.
  2. The Byteboard ran 90 minutes: 30 minutes on design, 60 on code.
  3. There was also a task to write a response to a fake PM about a mock project.

11: Summer 2026 Byteboard, not LeetCode

Cycle: 2025 (for Summer 2026) · Role: SWE Intern

  1. The candidate completed a Byteboard OA for Summer 2026 and confirmed it was not standard LeetCode.

12: Easy functions, brutal design doc

Report date: September 2024 · Role: SWE Intern · Result: Advanced to the final

  1. The coding functions were straightforward.
  2. Finishing the design-doc section on time was the hard part.
  3. The candidate hinted that reviewing process scheduling would help.

13: Building real product features

Report date: September–November 2024 · Role: SWE Intern, 2025 cycle

  1. The Byteboard felt like building actual product features.
  2. The scope was reasonable, but time was tight.

History (before November 2023)

H01: Early application, October offer

Report date: April 2024 (2023 cycle) · Role: SWE Intern · Location: New York · Result: Offer

  1. The candidate applied in early September and heard back within one to two weeks.
  2. After Byteboard and three final rounds, the offer came in early October. The work felt like real codebase tasks.

H02: Two-hour Byteboard, three-round onsite

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

  1. A two-hour Byteboard, split between design-doc comments and suggestions and feature coding.
  2. The onsite had one behavioral and two technical rounds.

H03: A three-week loop

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

  1. Byteboard, a recruiter check-in, then two technical interviews and one behavioral. The whole loop took about three weeks.

H04: A creative OA after a campus event

Report date: July 2023 · Role: SWE Intern · Location: Atlanta · Result: No offer

  1. The candidate met recruiters at a campus event and got an OA.
  2. They called it creative, testing data structures, iterative logic and code efficiency.

H05: BFS and recursion onsite

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

  1. Two technical interviews, one on BFS over a tree and one on recursion, plus a behavioral.
  2. The candidate did not finish either coding problem.

H06: Fast turnaround and an O(log n) search

Report date: August–September 2022 · Role: SWE Intern · Result: Advanced

  1. The candidate applied cold and got the Byteboard ten days later.
  2. They heard back eight days after submitting, and the final was scheduled three days after that.
  3. They wrote clean code, an O(log n) binary search (practice) and extensive comments.

H07: Byteboard, design, two coding rounds and values

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

  1. Byteboard, then one design round, two coding rounds and a 30-minute values chat.
  2. The coding involved building a class structure and specific helper functions.

H08: A 115-minute writing-and-coding OA

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

  1. The Byteboard ran 115 minutes and mixed writing with coding.
  2. It set up a fake scenario to design and partly implement.

H09: Search highlighting and file organization

Report date: January 2021 · Role: SWE Intern · Location: San Francisco · Result: No offer

  1. Byteboard first, then a final with two coding rounds and one design round.
  2. Tasks involved search-result highlighting and file organization.

H10: OA, then a virtual onsite with system design

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

  1. An OA, then a virtual onsite with two technical rounds and one system design round.

H11: Byteboard and a four-round loop

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

  1. Byteboard with design-doc comments and coding functions.
  2. A loop of two technical, one system design and one behavioral interview.

H12: Figma-style questions on standard structures

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

  1. The candidate passed Byteboard.
  2. The onsite had two technical rounds and one system design round, using standard data structures in a Figma-like setting.

Patterns across the reports

  1. The design doc is where time runs out. Candidates singled out the design-doc part as weak or too short (08, 12, 13), and H08 described the same writing-plus-coding mix.
  2. Unfinished work is not automatically fatal. Instructions said finishing everything was not expected (09); one candidate who finished all steps advanced (07), and one who finished two of three did not (08).
  3. Two technical, one behavioral. Finals had that shape in H02, H03 and H05, with a system design round added in H10–H12.
  4. CoderPad from August 2026. Four Winter 2027 reports mention the new CoderPad OA (01, 03, 04, 05).

Common questions

What is the Figma intern OA for Winter 2027?

A 90-minute CoderPad (04). One candidate designed a solution and built it with the built-in AI (05); another described multiple choice plus problem solving (01).

Does Figma still use Byteboard?

Not since August 2026, per one candidate (05). Summer 2026 and earlier cycles used Byteboard (06–13).

How long does Figma take to respond after the OA?

Figma's stated turnaround after CoderPad is about 10 business days (03). A Summer 2026 candidate heard back in three days (08) and another waited about ten days for the final invite (07).

What is in the Figma intern final round?

Two technical interviews and a behavioral in most reports (H02, H03, H05). One Winter 2027 candidate had AI-assisted TypeScript debugging and a DSA round (02).

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.