I applied online and received a request for an interview a couple of weeks later. This started with a video call to a member of their recruitment team, who was very friendly and enthusiastic about the company. There was some explanation about the role and Unity's background. Questions mostly revolved around my reasons for applying and my background. The recruiter was very nice and allowed ample time for me to ask questions.
The rest of the hiring process was explained during this call and would entail:
All calls were conducted using Zoom, and the skills test used Codility. The skills test was in two parts and timed at 90 minutes (from the moment you begin). This is as much as I knew before starting, as the task is only detailed when you begin. The tasks themselves weren't difficult nor did they require 'ninja code.' They actually seemed like a less-than-typical type of problem you'd solve in the role, requiring some less commonly used patterns and broad thinking about the problem.
The video call and on-site interviews were very similar, with three people interviewing. One person changed in the lineup between the two sessions. Questions were mostly about experience, past projects, and understanding my knowledge. Nothing was too pressing, and I felt comfortable talking about knowledge gaps, failures, or where I feel I could do better. Everyone was very welcoming and appeared genuinely interested in understanding my ability. I was given time at the end of both sessions to ask my own questions. During the on-site interview, I was also given a brief tour of the office.
A video call with a VP sounded intimidating but was far from it. It was very casual and was more an opportunity for me to ask questions about the company, its direction, management style, etc., of someone quite senior. It was definitely a useful stage in the whole process, and I'd recommend everyone take full advantage of it. The VP was very friendly and sincere with their answers.
Finally, I was asked to provide references: two colleagues and two managers. These were very promptly followed up on, despite the difficulties of time differences between the US and the UK.
After references were handled, there was another call with the same recruitment contact I had been in email contact with throughout the whole process, where I was given details of the job offer. One thing I found unusual was that there wasn't even a conditional offer until this stage, which I would usually expect before references. Although this could just be a UK practice that I'm accustomed to.
Overall, the whole process was great. It took a lot longer than I expected; however, the Christmas break wouldn't have helped. Everyone I spoke to was very nice and enthusiastic about the company. The attitude I picked up on made it clear that the company would be a good place to work. Good contact was maintained throughout the whole process.
Why Unity?
What do you know about the company?
What projects have you worked on and with what tech stacks?
Questions around experience with technologies mentioned in the job spec.
The following metrics were computed from 19 interview experiences for the Unity Software Engineer role in United Kingdom.
Unity's interview process for their Software Engineer roles in the United Kingdom is on the easier side as most engineers get an offer after going through it.
Candidates reported having very good feelings for Unity's Software Engineer interview process in United Kingdom.