The first round was a recruiter call. The recruiter was really nice and explained the next steps.
The next round was a one-hour technical screen. The question focused on a real-world use case they encounter at Figma.
I had never seen a problem like this before, and I felt it wasn't explained very well. I had a lot of questions before getting started, and even more as I began working through it.
I thought this was to be expected, as the question was vague and unique to Figma. I actually enjoyed working on it regardless.
Apparently, I asked too many questions, because I received a rejection email the next day.
They make you sign an NDA, but the problem is not LC at all. It focuses on a real-world Figma use case and involves creating object classes.
My advice is to just practice your programming language of choice and make sure you know it very well to solve a real-world problem (and not just an LC one).
The following metrics were computed from 39 interview experiences for the Figma Software Engineer role.
Figma's interview process for their Software Engineer roles is extremely selective, failing the vast majority of engineers.
Candidates reported having good feelings for Figma's Software Engineer interview process.