applied to figma's new grad SWE role last week and just got an email for a recruiter screen. absolutely panicking because figma is like my top choice and i have no idea what their process actually looks like for entry level.
from what i've pieced together from older posts: phone screen with recruiter, then a technical screen (seems to be one coding round), then a virtual onsite with multiple rounds. but i genuinely don't know how that maps to new grad vs. experienced hire loops. does figma give new grads the same full onsite or do they run a condensed version?
what i'm specifically trying to figure out: coding: is it strictly LC-style or do they lean into UI/DOM stuff? i'm applying for a generalist SWE role not explicitly frontend but figma is obviously a frontend-heavy product behavioral: is there a dedicated behavioral round or is it woven into every round? any sense of how much they care about it for new grads vs. just the technical bar system design: i've heard new grads sometimes get a lighter version of the system design round (more product-focused), is that true at figma? timeline: from recruiter screen to offer, roughly how many weeks are people seeing in 2026?
i'm a CS grad (class of 2025), mostly did internships in backend, some React experience but nothing crazy. genuinely not sure if my background fits what figma is looking for at the new grad level.
any recent loops would be so helpful. i'll share mine once i'm through it.
4 replies
frontend_fran
went through their new grad loop about 8 months ago (before my current role). for the coding rounds: they do ask standard algorithmic problems, but at least one round had a UI component. think implementing a small interactive widget, not full system design. knowing vanilla JS DOM manipulation actually helped me more than grinding LC hard problems did.
behavioral was woven into the technical rounds, not a separate block. maybe 10-15 minutes per interviewer at the start or end. they asked stuff like 'describe a project you're proud of' and 'how do you deal with ambiguity.' pretty standard, nothing too obscure.
timeline for me was about 4.5 weeks start to finish.
newgrad_neil
this is incredibly useful, thank you. so brush up on DOM/vanilla JS even for a generalist SWE role. got it. did they give you a take-home or was everything live coding?
corp_refugee
figma skews toward applied frontend even for generalist new grad roles. that's just the nature of what they build. you don't need to be a CSS wizard but if you've never built a canvas-like UI or thought about how collaborative editing works under the hood, at least read some high-level material on it. shows you actually care about what they do.
system design for new grads at most design-tool companies is lighter than what an L5 would get. usually something more like 'design a simplified version of X feature' with a lot of scaffolding from the interviewer.
tired_recruiter
recruiter screen tip: they're going to ask why figma specifically. 'i use figma every day' is not a compelling answer because everyone says that. know something about their infrastructure investments, their recent AI features rollout, or their API/plugin ecosystem. one specific thing you genuinely find interesting goes way further than enthusiasm for the product.