My general point would be: If you see a position that strikes your interest, definitely follow through the interview process at least until you have had a chance to talk to the potential future team. You will get honest answers and a good impression of the job. I have been impressed from the start by the company's approach.
Over the past year, you can see the effects of rapid growth on the company. Unity, and especially the management teams, are really aware of the value of the original company culture. It might have changed since its inception (according to conversations with long-time employees), but coming from a mega-corp, I saw things that really appealed to me in their approach. I feel more valued and considered as an engineer, and that has had a big impact on my daily life.
The interview process was very personal: direct, open conversation with the team and various bits of management. There were no technical interview questions, but instead conversations about my previous experience, and some questions from me on the product and team I would be working with.
My experience might have been positive, but I have also heard from other engineers who are disillusioned by their managers or even the company's response to some of their requirements or concerns.
My advice would be to really prod about the team during the interview.
The company is shifting gears as it grows in size, and some of the usual corporate stuff starts to seep in, in what I would describe as "United States-isation". The management communicates well about their intentions behind everything, but in the end, we still end up stuck with job levels, like any other tech company, for example.
The interview process consists of three stages: * The first stage is an informal, on-site meeting with the Product Manager. * The second stage involves two one-hour technical interviews with a total of four developers. * The third stage is a m
7-interview process: * One interview with HR * A 2-hour Codility code challenge in Python, Go, or Scala * Five different 45-minute interviews with: * Director of the team * Data Scientist * Data Warehouse Manager * Soft
The interview process was thoughtful and engaging. The design question and home application task, covering both backend and frontend, were well-structured, challenging, and provided a great way to showcase real-world skills.
The interview process consists of three stages: * The first stage is an informal, on-site meeting with the Product Manager. * The second stage involves two one-hour technical interviews with a total of four developers. * The third stage is a m
7-interview process: * One interview with HR * A 2-hour Codility code challenge in Python, Go, or Scala * Five different 45-minute interviews with: * Director of the team * Data Scientist * Data Warehouse Manager * Soft
The interview process was thoughtful and engaging. The design question and home application task, covering both backend and frontend, were well-structured, challenging, and provided a great way to showcase real-world skills.