
Disruptor Beam Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 10 interview experiences · FREE TO READ
Which role are you interviewing for?
6 roles · 10 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Disruptor Beam.
Mobile Software Engineer
Got an email back really fast, like in a week, so they must have been eager to hire. Had a phone screen with someone pretty new to the company. They asked the usual questions to check how serious I was, and did a decent job. A week later, I went in for a full day of interviews at the office. Talked to a bunch of people, from HR and producers to senior engineers and even the VP of Engineering. They were really thorough and made me feel at ease with questions about my background and some technical stuff to see what I knew. Only one person made me a bit uneasy with vague expectations, but most of them focused on how I approach problems. They also let me ask questions about the company, and their answers were spot on.
- How would you implement a C string split function?
- Can you explain how to remove duplicate elements from an array?
- What are the differences and use cases for class relationship tools such as Inheritance, composition, and components?
Software Engineer
The interviewer seemed really awkward and unprepared for the call, struggling to come up with engineering questions on the spot. The whole vibe was cold, like they didn't want to be there. The next day, I got an automated email saying I didn't get the job. It felt super disconnected, especially since their company values emphasize culture and personality. I don't think they even considered my personality at all. Honestly, I'm kind of glad I didn't get an offer if this interview process is any reflection of how things run internally.
- Can you explain what MonoBehavior is and how it functions?
Data Scientist
I applied back in January and then had a phone interview with the hiring manager a few days later. Before the interview, I did some digging and noticed this job had been up for grabs for more than 6 months. The person interviewing me kept asking super specific stuff about the company. It really felt like they were trying to get free consulting out of me, so I'd say don't bother with these guys.
- Did you happen to play the video game xyz?
- Can you answer some specific questions about our company?
Community Manager
I was contacted quickly and had an initial phone interview. Then, I was brought in for a 6-hour on-site interview that included lunch. I met several staff members who are part of the team I'd be joining. We had lunch with multiple people, which was a nice, casual way to get to know the company culture.
- How do you cope with the stress of dealing with a community that can sometimes be frustrated?
Disruptor Beam Interview Questions
Quoted word for word from Disruptor Beam interview reports.
“Can C# have a memory leak?”
Read reports →“How would you implement a C string split function?”
Read reports →“Can you explain how to remove duplicate elements from an array?”
Read reports →“Can you explain what MonoBehavior is and how it functions?”
Read reports →“Can you explain the client-server process using HTTP?”
Read report →“Did you happen to play the video game xyz?”
Read report →“What are the differences and use cases for class relationship tools such as Inheritance, composition, and components?”
Read report →“What food would you be?”
Read report →“How would you evaluate this artwork?”
Read report →Formats, difficulty and experience
Across all 10 Disruptor Beam interview reports.