Real, anonymous reports from people who interviewed for Software Engineer at Synthesia, newest first and distilled into what to expect across the loop.
After I connected with the team, the process felt tightly coordinated and generally moved stage to stage without much dead air. I went through a recruiter screen first, then a sequence of interviews that stayed pretty consistent in structure. The early technical portion leaned on problem-solving and clean code, with at least one session feeling like it had enough room to work through the ask rather than being purely rushed. Then there was a system design interview that was more structured than the open-ended style I’m used to—breaking the conversation into smaller decisions instead of asking me to conjure a whole architecture from scratch. A leadership-style interview followed, focusing on end-to-end ways of working and how I handled projects and problems, with the usual behavioural framing but with more emphasis on execution and ownership.
What made my experience stand out was how abruptly it ended and how badly it was communicated. After applying, I didn’t get any helpful follow-up from the process—within minutes I received a refusal email, and then I got another one almost immediately with a different template. The messages felt automated and careless, especially since I’d seen “after careful review” style wording twice back-to-back.
The interview process is generally well-organized, moving smoothly from one stage to the next with minimal delays, typically including a recruiter screen, technical interviews, and a final conversation with leadership. Candidates appreciated the structured approach, which allowed for clear expectations at each stage.
Candidates can expect a mix of technical interviews focused on problem-solving and clean coding, along with a take-home assignment that is engaging and allows for discussion of design choices during follow-up interviews. The take-home tasks are generally scoped to be manageable and are seen as a way to demonstrate practical skills.
Behavioral interviews often emphasize execution, ownership, and how candidates handle projects, with a focus on measurable outcomes from past experiences. These discussions tend to be framed around cultural fit and alignment with company values.
While many candidates appreciated the clear communication throughout the process, some reported frustrations with abrupt rejections and lack of detailed feedback, especially after investing time in interviews or assignments. Consistency in communication is a noted area for improvement.
The overall timeline for the interview process can vary, with some candidates experiencing a quick turnaround while others felt the process dragged on longer than necessary. Candidates noted that clarity on timelines and next steps could enhance the experience.
The difficulty level of interviews can vary, with some candidates feeling that the questions were either too broad or overly focused on specific technologies, which made it challenging to showcase their skills effectively. Candidates should prepare for a range of question types and be ready to discuss their reasoning.