Wizards of the Coast logo

Wizards of the Coast Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 15 interview experiences · FREE TO READ

3.9 Rounds average
Average Typical difficulty
33.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Wizards of the Coast.

Showing 3 of 15
Wizards of the Coast logo
Wizards of the Coast

Software Developer

Engineering · a year ago

Mid Average Neutral experience No offer 6 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Panel Background check Offer
Interview formats
Technical Coding Behavioral

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.

Confirmed questions4 questions
  • Questions about your personality
  • A challenge related to back-end or front-end development
  • Questions that are technical in nature
Wizards of the Coast logo
Wizards of the Coast

Senior Software Engineer

Engineering · more than a year ago

Senior Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Coding

So, the interview process started with a recruiter screening, then a pre-NDA hiring manager screen. After that, there was a post-NDA hiring manager technical interview. Next up was a two-person design and teamwork type interview. The final round was a "technical" interview, which is where things got weird. I was interviewing for a senior role, expecting questions about my experience with libraries, leading projects, etc. Instead, the first question was just 'what is Kotlin?', followed by textbook definitions and basic questions about custom views and other everyday stuff. Nothing about my actual experience or resume, not even a LeetCode coding challenge, which I'd prepared for. It felt like they were asking junior-level questions for a senior role. Also, they rushed me through the process because it was near the end of hiring for this position. The recruiter said they'd get back to me in a few days after debriefing, but they ghosted me. I was really accommodating, taking interviews on short notice, even rescheduling when someone was sick. I at least expected a rejection email, but instead, I feel like my time was wasted because the recruiter won't even give me a courtesy response after I tried contacting them twice for an update. They really don't respect your time.

Confirmed questions5 questions
  • What is Kotlin?
  • What is an observable?
  • Should you use observable to communicate between fragments?
Wizards of the Coast logo
Wizards of the Coast

Senior Software Developer

Engineering

Senior Average Positive experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Offer
Interview formats
Behavioral Technical Coding System Design

Applied online and got a call from a recruiter about 3 weeks later. A week after that, had a phone interview with the recruiter, lasting about an hour and fifteen minutes. It was mostly behavioral questions with a few technical ones about design. An onsite interview got scheduled about a month after that. The whole thing took around 2.5 months. It's good to keep in touch with the recruiter often. My recruiter was fast to reply but didn't give updates unless I asked.

Confirmed questions4 questions
  • Can you explain this C bit shift function in simple terms? It counts the set bits in a number.
  • How would you architect the rules engine for Magic: The Gathering Online, focusing on the game's zones to simplify it?
  • Implement the `isPrime` function and let's talk about making it faster, maybe with caching.

Wizards of the Coast Software Engineer 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

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

Should you use observable to communicate between fragments?

Read report

Implement the `isPrime` function and let's talk about making it faster, maybe with caching.

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 15 Wizards of the Coast interview reports.

Interview formats

Technical 39.5%
Behavioral 34.2%
Coding 18.4%
System Design 5.3%
Presentation 2.6%

Interview difficulty

Easy 33.3%
Average 60%
Difficult 6.7%

Candidate experience

Negative 40%
Positive 33.3%
Neutral 26.7%