Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Unity (Dublín, Dublín) en sept 2020
Entrevista
I had an initial phone screen with a recruiter, then a take home test. The take home test was a timed 45 minute coding challenge on codility, there were two questions. The first was easy enough, the second one took me a bit longer and I didn't quite finish it but still got through.
The next stage was a one hour chat with an engineering manager. It was mostly general questions and questions about my technical experience but not technical knowledge (Describe your proudest bug fix, how did you de-bug it?).
The next stage was 3 face to face interviews each with one person, all technical. This would normally be on-site but for me it was over zoom because of covid. Two interviews involved sharing your screen and solving a coding problem. One was easy for me and another was a bit trickier. All the questions were general algorithmic coding challenges and don't require a specific knowledge set other than just being able to solve problems and write an algorithm without googling it. I appreciate this approach as it's language agnostic. I saw another review which recommended a book called "Cracking the coding interview". You don't have to read all of it but the first few chapters will give you a sense of what they ask. The other interview didn't involve sharing my screen but there was a lot of technical questions surrounding TCP/IP protocols, difference between http and HTTPS etc.
I got turned down after this last stage and my recruiter offered to phone me to give me feedback next week.
The recruiter was great and the process moved very fast. I really got the sense that they want applicants to have a good experience which I did. My only recommendation would be maybe shortening the whole process or number of interviews. It is quite frustrating to go through a phone interview, coding challenge and 4 hour long interviews only to be turned down at the very last step.
Preguntas de entrevista [1]
Pregunta 1
What does the lock icon in the address bar of a browser indicate? What does it mean if it is unlocked/red etc. How would ensure that it does appear
Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Unity (Mountain View, CA) en mar 2026
Entrevista
Overall, I had a very positive experience. The process was a bit long (a little over a month), but it also included the Easter holiday period in Europe/Montreal.
The process was: HR phone screen, hiring manager interview, take-home assignment, technical round, and three virtual onsite rounds (Product, Behavioral, and ML knowledge), followed by the final decision.
There was only one coding assessment, in take-home format. The algorithm/design pattern/GitHub parts were quite basic. There was also some web development content (CSS/HTML layout), which was more challenging for me since that is not my primary area.
I then had a technical round that focused mostly on past experience rather than the take-home assignment itself.
In the virtual onsite rounds, the last ML round covered many ML topics. I prepared a lot and was able to answer many of them, though not all. The interviewer was very helpful and willing to share knowledge, which I appreciated.
The interview process began with a phone call with a recruiter, followed by a Zoom technical interview with the team leader, who asked about my experience. After that, I had two system design interviews, and finally an HR and senior manager interview.
Preguntas de entrevista [1]
Pregunta 1
Design Bitly – URL shortening service.
Design recommendation server – you receive a list of campaigns and filter them based on business logic.
Envié una solicitud electrónica. El proceso duró 4 semanas. Acudí a una entrevista en Unity (Copenhague, Hovedstaden) en jul 2025
Entrevista
I started with an initial conversation with Recruiter team, where the process was clearly explained to me. After that, I quickly moved to a high-level discussion with the hiring managers about the team’s architecture and specific needs.
I was then guided into several technical interview rounds — about four sessions, each lasting around 45 minutes. These included both team members and experienced professionals from outside the team, with diverse backgrounds. Almost every stage included a coding assignment component, as well as high-level discussions and deep dives into relevant parts of my background.
The entire process took around four weeks in total: about two weeks for the interview stages to be scheduled and completed, and another two weeks before I received the official result. Throughout the process, interviewers were intelligent, collaborative, and supportive.
I enjoyed the experience and gained a clear understanding of what the role involves. The challenges were fair and engaging, without feeling overwhelming. I was very happy with the outcome.
Preguntas de entrevista [1]
Pregunta 1
focus on solving algorithmic problems in the style of common online coding platforms, particularly involving data structures and graph-related challenge
