Figma Software Engineer Interview Questions
& Process

Applied online and after about two weeks, a recruiter got in touch to chat about my background, the company, and the role itself. Felt good. Then, I was set up for a first-round coding interview. They were cool about it, and I could even reschedule it last minute for personal reasons. The coding interview involved a series of tasks that built on each other. The interviewer seemed a bit low-energy and tired, but was still decent enough. Sadly, it didn't go well for me; I didn't finish everything and didn't move on. Generally, if you're pretty quick with data structures and core algorithms, you should be fine. It was an early interview, so I didn't get much specific feedback, just the standard rejection message.

I was sent a Greenhouse link asking some essay questions about why I chose Figma and my top 3 team preferences, like Backend or Infra. After that, I had a 90-minute Byteboard assessment. The first 30 minutes involved reading a technical design document and answering questions about it. Then, for the next 60 minutes, I had to implement some functionality related to that document. Unfortunately, I didn't pass the Byteboard. The 30 minutes for reading and thinking was really tough, a huge time crunch, and I didn't feel like I could really dive deep into anything.

First, there was a regular HR call where we talked about my previous work and my interest in joining Figma. Then, the phone screen involved a coding challenge with a few parts. It felt like LeetCode, although they said it wasn't. The trickiest part wasn't the algorithm itself, but really grasping the problem description, which they presented using Figma-related scenarios with a lot of extra words. You apparently have to pass all sections to advance to the next step, which is a chat with the Hiring Manager. Sadly, I didn't get that far, but everyone I spoke with was really nice and seemed like great people to work with. I'll try again next time!