J'ai postulé en ligne. Le processus a pris 5 jours. J'ai passé un entretien chez Osmo (San Francisco, CA) en nov. 2013
Entretien
The CEO of the then two member company contacted me and set up a phone interview. On the phone interview he said we're not going to waste each other's time so let's dive right into the problem in hand. The problem was fairly easy but I was very inexperienced with coding in an interview and I bombed it.
Questions d'entretien [1]
Question 1
Write code to draw line on the screen horizontally where the output is binary and the pixel values are stored in a char buffer.
J'ai postulé via une agence de recrutement. Le processus a pris 2 jours. J'ai passé un entretien chez Osmo en sept. 2016
Entretien
Was contacted by their HR representative with a canned email (got my name wrong). Went through a pretty routine initial phone screen and then received a coding homework assignment in which I completed and returned within an hour. After passing that I then had a face-time call with the VP of engineering to have a paired programming exercise. The exercise was awkward and rushed and had little to do with game development principles or even the tech I would have been engineering in.
In their defense, the company is ran by former Google employees and thus their interview process is similar. However, it is in my opinion that they are too stuck in their old ways.
Questions d'entretien [2]
Question 1
Take home test was a complete-the-api algorithm assignment. It was pretty straight forward, relevant to the job description and presented enough of a challenge to rule out anyone that didn't know what they were doing.
The paired programming exercise was coding a Google spider. Probably something that should have been given to a Google candidate or someone that would be coding for big data -- not game development.
J'ai postulé en ligne. Le processus a pris plus d'une semaine. J'ai passé un entretien chez Osmo (Palo Alto, CA) en avr. 2015
Entretien
Initial non-technical phone screen followed up by a short (hour long) half technical and half resume based phone screen. Came in for a set of about 5 one hour interviews with different people. I was interviewing for a game developer job, 3 of my interviews were technical whiteboard interviews, one was more focused on game design, and one was more of just a general fit/company culture interview.
Questions d'entretien [1]
Question 1
What has been a difficult game design challenge you have had with one of your previous projects? How did it arise? What made it difficult? How did you solve it?