My interview process involved the following steps:
The first two rounds were quite short and quick. Essentially, they focused on candidate experience, project description, and some organizational and soft-skills aspects. Both parties were amenable to proceeding to the next stage, which was the take-home assignment.
It's worth noting that they have not updated their take-home task in several years, yet it seems most (if not all) candidates receive the same quiz. Despite my application for a Software Engineer position requiring 90% Go proficiency, the quiz/tasks contained no Go-related questions. Instead, there were several irrelevant language-specific questions on C, Ruby, and JavaScript. Therefore, even if you solve all the questions (7) and code tasks (JS, 2), you will most likely still be rejected. As I was, it seems they don't care about your answers. They may judge you're not a good Go developer without asking a single question about Go, which is quite amusing.
Do not waste your time on their take-home assignment.
How do you celebrate the release with the team?
The following metrics were computed from 1 interview experience for the Unity Software Engineer role in Helsinki, Finland.
Unity's interview process for their Software Engineer roles in Helsinki, Finland is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Unity's Software Engineer interview process in Helsinki, Finland.