The recruiter screen didn't go too deep into my experiences, other than to tick the correct boxes in terms of technologies.

The first technical screen was scheduled for the following week. I was asked a question that felt like a LeetCode easy with Figma-specific flavors. There were two additional follow-ups to the first question. I thought this went fairly well and would suggest showing that you have a good intuition for the problems they ask.

For the on-site, I was prepped heavily by the recruiting team on what to expect. Not questions word-for-word, but rather what signals interviewers might be looking for, so my prep was focused around that. The on-site consisted of:

• Two coding rounds
• One system design round
• A technical deep dive round
• A behavioral round

Both my coding rounds were based around Figma-specific features. Again, both problems contained up to two additional follow-ups. It would be best to at least solve two and talk about the third if you don't have time to solve. These problems were around LeetCode medium in difficulty.

The system design round was straightforward: the interviewer will give you a potential system they want you to design. If you've had system design interviews before, this should be no different. This was a very collaborative interview.

The technical deep dive is more of a presentation and then Q&A on a system that you've built in your career. I would suggest prepping for this heavily.

The behavioral interview is pretty much what you can expect from any other company. Make sure to review their values and tailor your responses accordingly.

Overall, the process was very quick, especially with moving forward to the offer. They really care more about how flexible your thinking can be when faced with difficult problems. Don't focus too much on the answer, but rather the collaborative nature of the interview.

NDA. Cannot say more other than coding questions are Figma-centric.