Voodoo Game Developer Interview Questions
& Process

The interview process involved several calls and a design test. I thought the test was a good way to see what the job was really like. The Q&A after the test was super useful because I could explain my thinking and get feedback. Antoine would set up follow-up meetings after calls to check in, which really helped answer my questions and keep me on track for what was next. The in-office meeting was a surprise but very helpful. It let me experience the work environment and do some brainstorming and talking in person, which gave me a real idea of the day-to-day work.

I did a first interview to introduce myself and my objectives while also learning more about Voodoo. Then I did a second interview where my recruiter told me it was interested and invited me to make a technical test (Game prototype). After I sent it, I got a third interview with a developer to explain what I did, why, and what could be improved. I finally got an answer. It took 2 or 3 months in total time. That's quite long, but they explained it was because there weren't many empty seats left and they were waiting for new Game Directors to come.

The entire interview process spanned two months, concluding with a rejection. The process felt like a waste of time given the outcome. There were multiple rounds of manager meetings and technical interviews with significant gaps between them. The applicant often had to inquire about their application status to maintain momentum. The initial technical challenge required replicating one of their mobile games within a week, which seemed excessive for an ability test. Following this, there were questions focused on cultural fit, Unity knowledge, and game reviews.