Software Engineer applicants have rated the interview process at Figma with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 57% positive. To compare, the company-average is 47.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 25 days to get hired, when considering 35 user submitted interviews for this role. To compare, the hiring process at Figma overall takes an average of 25 days.
Common stages of the interview process at Figma as a Software Engineer according to 35 Glassdoor interviews include:
Phone interview: 31%
One on one interview: 22%
Presentation: 15%
Skills test: 15%
Group panel interview: 7%
Background check: 5%
Drug test: 2%
IQ intelligence test: 2%
Other: 2%
Here are the most commonly searched roles for interview reports -
I completed a technical phone screen which asked me a question related to sorting and grouping objects on a screen. I also spoke with the hiring manager who explained to me their primary goals and initiatives. I was interested to find out they take some pretty advanced measures to protect customer experience and are contributing to open-source projects to advance modern frameworks.
Interview questions [1]
Question 1
How would you sort a group of objects from left to right based on points
How would you sort a group of objects with distributed y-axis and x-axis to be grouped from top to bottom and left to right?
I applied through a recruiter. The process took 2 weeks. I interviewed at Figma (London, England)
Interview
I was recently reached out to by a recruiter and had my HR and coding interview. The overall process was very simple and straightforward.
The interviews were scheduled back to back, 30 minutes HR interview followed by the 1 hour live coding interview.
In hindsight, I realised having these two interviews back to back and with different interviewers meant I did not have a chance to switch gears and blanked out in the coding interview. For future interviewees, make sure you have a gap in between the interviews.
The recruiter reached out and did a first-round interview. The first round interview consists of coding and HM interview. HM was a person good to communicate with, and he was professional. HM interview questions were typical. For the coding round, the question was a bit too long to understand in a 1-hour window, given the number of questions, and the interviewer provided too much further info outside of the question, which made it more confusing. The interviewer doesn't seem to understand the question very well and need to re-explain some solutions. Not a very good experience for the coding round