
Wizards of the Coast Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 99 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 99 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Wizards of the Coast.
Marketing Manager
It was a pretty standard interview process. First, I had a call with a recruiter, then I spoke with the hiring manager and some of the team. They asked standard questions that shouldn't be a problem if you're prepared. Make sure to negotiate your salary.
- How would you estimate the number of planes currently in the air without internet access?
Project Manager
The interview process had 2 rounds: a quick screener with the recruiter and then a 45 min to 1-hour interview with the hiring manager. Everything went fine until after the second interview. The whole process lacked communication, and I was ghosted without even a rejection email. I had to check their confusing careers portal to see that I wasn't selected. It seems they don't care about candidates if they aren't selected. Their recruiting team needs to improve; avoid this company if you don't want to be left in the dark.
- Tell me about your work experience.
- Can you answer some basic behavioral questions?
- What are your thoughts on some situational questions?
Product Quality Engineer
The interview process consisted of 8 total rounds. First, a recruiter chat. Then, a manager screening with some job specific questions and also a lot of clarity about the team and cultural expectations. Rounds 3-8 were team interviews, with 1 or 2 participants per round, each interview had a different flavor. One focused on processes, one on supplier quality, one on personality, another on data and technology, and the final one was HR mandated behavioral questions. The interview process itself was tedious but I enjoyed each conversation and got very excited about the role. The recruiter/HR Rep was on top of scheduling and despite it being a lot, it was pleasant and transparent as far as the team and role. The problem comes after. I followed up a few weeks after my final interview, knowing there were additional candidates screened after me and received a message that gave me a lot of hope for an offer. It included a specific day I should receive an update and asked if I was expecting additional offers. The day mentioned came and went with no communication. I followed up twice more and finally got the news that I wasn't selected. The wording indicated to me that, had I not followed up, I would have been ghosted by the recruiting team. I felt incredibly disrespected by the lack of communication and the fact I had to wait so long to be rejected. To add insult to injury, I had been ghosted during a previous candidacy for a similar role and had to find a team member on LinkedIn to learn this. No formal rejection. My advice to the recruiting team is to inform the unselected candidates right away and put us out of our misery. If you as a candidate are comfortable being left without updates for weeks and having to follow up numerous times to get answers, go for it, but I feel that the recruiting team stops caring about you the second you aren’t selected. The poor communication from recruiting makes the entire team look bad and has the potential to alienate candidates that otherwise may have considered applying again in the future.
- Were you asked many questions concerning internal and external communication?
Software Developer
Applied online and got an email from the hiring manager. I tried replying multiple times with no luck, even though he reached out first. Finally, I connected and had a good chat with him. He then passed me to a recruiter, which was supposed to be the first step. After the recruiter meeting, I had to do a technical challenge, I could pick between front-end or back-end, and I chose back-end. After passing, I had 4 more interviews. 2 were with technical folks. They were nice, but didn't ask about my back-end challenge or even see my code. They also didn't know anything about the job I applied for. A third interview was about how I'd handle situations. A fourth was a final chat with the recruiter. I was told if I passed that, there'd be a final round in Seattle, which was basically a formality if I got there. Needless to say, I wasn't flying anywhere without serious guarantees. I got let go professionally at this stage. Everyone was nice, seemed like good people. But the process was way too long, showed indecisiveness and poor communication. It was also weird that the technical evaluators didn't know the job's technical needs.
- Questions about your personality
- A challenge related to back-end or front-end development
- Questions that are technical in nature
Wizards of the Coast Interview Questions
Quoted word for word from Wizards of the Coast interview reports.
“Can you explain this C bit shift function in simple terms? It counts the set bits in a number.”
Read reports →“How would you estimate the number of planes currently in the air without internet access?”
Read reports →“Then, could you write another piece of code to take that String and rebuild the original binary tree?”
Read reports →“Could you write some code to turn a binary tree into a String?”
Read reports →“Implement the `isPrime` function and let's talk about making it faster, maybe with caching.”
Read report →“How can we make Magic the Gathering attractive to new players who don't know the game, without simplifying the content?”
Read report →“Could you describe the stacking of continuous effects in Magic: The Gathering?”
Read report →“How would you approach a sorted list problem that could be solved with binary search?”
Read report →“Could you tell me about the last board game you played?”
Read report →Formats, difficulty and experience
Across all 99 Wizards of the Coast interview reports.