Synthesia Software Engineer Interview Questions
& Process

They started with an introductory call. After that, I was asked to write an overview of a project or product where I had significant ownership. This write-up needed to include details on how the project originated, my specific role, and its success metrics.

I went through 3 interview processes with Synthesia, getting rejected twice before being hired on the third attempt. My overall experience was very positive, especially with a really proactive Talent Acquisition specialist who was very enthusiastic about my background. The interviews presented real-world problems and standard questions about my past experience, nothing unusual. Everyone I spoke with was friendly and willing to pause the interview to answer my questions. I'd describe the process as difficult because it's a great company with great people, but I recommend not giving up after the first try and approaching it with a positive attitude.

The interview started with an HR call about salary expectations, my reasons for applying, and my past work. Then, I had a behavioral interview with the Direct Manager about my problem-solving approach and work habits, though they seemed a bit disengaged. After that, I got a technical assignment to build an image editor, which I completed on time. The debrief for the assignment was tougher than expected. Instead of letting me present, they immediately questioned my choices. I explained my methods, but then got asked about React context downsides and why Redux might be better, even though I didn't use either in my solution. They also asked me to compare pagination and infinite scroll, which felt outside the assignment's scope. The interviewer suggested client-side grayscaling using the browser, and I brought up issues like compatibility, blur, and data consistency, but they seemed set on their idea. I did manage to answer a system design question and made two requested changes to the assignment. Overall, it was a decent process, but the assignment debrief felt unfocused with unexpected, subjective questions, making it hard to prepare and possibly influencing the rejection unfairly over debatable points.