The process began with an initial phone screening. This was to be followed by a 'build a complete game in 30 minutes' stage, which the recruiter mentioned would not be a technical interview, but rather a demonstration of understanding of the game engine software.
Both of these stages presented difficulties. I was stood up by the initial recruiter twice before the actual first call. The second instance occurred because an internal meeting had been scheduled over my allocated time at the last moment.
After finally proceeding to the 'build a game' section, my recruiter instructed me to use a specific game engine, which I did. I used it as requested and built what was asked. However, it seemed my interviewer for the game section had no knowledge of that particular game engine and judged my work according to different workflows.
I was repeatedly asked to perform tasks more akin to an actual technical interview, which I could have prepared for if the instructions had been clearer.
Overall, I believe this process is reflective of how the company and department operate, and I would have to not recommend it.
Build a game in 30 minutes.
The following metrics were computed from 3 interview experiences for the Snap AR Engineer role in United States.
Snap's interview process for their AR Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Snap's AR Engineer interview process in United States.