Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Blizzard Entertainment

      Parte di Activision Blizzard

      Azienda coinvolta

      Chi siamo
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Blizzard Entertainment | Offerte di lavoro di Blizzard Entertainment | Stipendi di Blizzard Entertainment | Benefit di Blizzard Entertainment
      Colloqui di Blizzard EntertainmentColloqui per Lead Gameplay Engineer presso Blizzard EntertainmentColloquio di Blizzard Entertainment


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Lead Gameplay Engineer

      8 feb 2023
      Candidato anonimo a colloquio
      Offerta rifiutata
      Esperienza negativa
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 2 mesi. Ho sostenuto un colloquio presso Blizzard Entertainment nel mese di feb 2023

      Colloquio

      The process is fairly standard. I appreciated that the technical interview process used a take-home assessment instead of a HackerRank coding test (those are absolutely dreadful and inaccurate). The number of interviews is very high, and for this position, I found that many of the questions centered around behavior were vague, leading to vague answers from the candidate. I made it through the entire process and the company was prepared to make an offer. However, I was informed very late in the process (as in after all interviews and test submissions were completed) that this role would be a hybrid role, as in 3 days a week in the office. The recruiter told me that in the coming months, there would be "a great push to get back to the office", and it doesn't look good if the lead engineer has a remote only position. I was very clear from the beginning that I was only interested in a remote position, and I even received confirmation that no relocation would be required in one of the early interviews. Despite me warning Blizzard that requiring a relocation would be a deal-breaker, they insisted on all offers being contingent upon relocation. As a result, I refused to hear any offers and went with another company that I'm extremely excited about to be joining. My advice to Blizzard is to strongly reconsider forcing employees to carry their work with them to work while having to fight traffic for two hours to pay for an insanely overpriced parking space that is a mile away from a mediocre office just so that they can sit in an exposed cubicle environment with horrible ambient noise and frequent interruptions from co-workers just so that managers can justify a job of "cracking the whip" and the CEO doesn't have to face the reality that maybe a 30 year lease on a very expensive office floor in southern California might not have been a financially sound decision.

      Domande di colloquio [1]

      Domanda 1

      Interview questions were typical for this role. They included amazing technical questions such as "Can you run a coroutine asynchronously in Unity?" It turns out that you can (I didn't know this before the interview, I discovered it with my own experimenting after the interview), but it requires some hacky tricks, and you lose the benefits of being in a coroutine in the first place. I was also asked vague behavioral questions like "If you and another engineer have fundamentally different opinions on how to complete a task, what do you do?" This question is vague in my opinion because each situation is different, and depending on what the task is and how central it is to the overall project, I can have completely different responses. I'm not a petty person (he says as he writes a scathing interview review on Glassdoor, lol), so if the task has a low impact on future tasks, I would simply learn from what the other engineer had submitted and move on with my life. However, if the task is central to the entire project, I would spend more time with the other engineer to get to understand their perspective. They probably see something that I don't, and there's a strong possibility that we can find a common solution together that has more benefits and less drawbacks. If I still find that my idea for an implementation is far better, I would bring in more people to discuss the situation and make sure that we're taking the right approach. Finally, if I have discussed my concerns and the rest of the team agrees to take the other engineer's solution, then I agree to move forward with that solution and support it. At the end of the day, we're still a team, and it serves no one for one engineer to insist on their implementation be used at the cost of the rest of the team.
      Rispondi alla domanda
      4