Software Engineer applicants have rated the interview process at Big Fish Games with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 25% positive. To compare, the company-average is 52.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 45 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Big Fish Games overall takes an average of 17 days.
Common stages of the interview process at Big Fish Games as a Software Engineer according to 4 Glassdoor interviews include:
Phone interview: 27%
One on one interview: 18%
Group panel interview: 18%
Skills test: 18%
Presentation: 9%
IQ intelligence test: 9%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Big Fish Games
Interview
Behavior and technical questions at the early step.
More serious behavior questions with the future team at the end.
The technical questions I got were mostly from the easy level of LeetCode.
Interview questions [1]
Question 1
Basic questions about the development environment of the mobile game industry.
I applied online. The process took 4 months. I interviewed at Big Fish Games (Seattle, WA) in Feb 2016
Interview
The whole interview process takes a very long time. The hiring manager and interview teams are very nice and friendly. Lots of questions abut CS algorithm and system design. However, the recruiter is the worst I have ever seen. He never answers my question or reply emails, very very rude.
I applied through a recruiter. I interviewed at Big Fish Games
Interview
Programming question by email, followed by 2 phone interviews, i failed the second phone screen.
first phone screen went well, a senior techie asked basic java, jvm (gc) questions.
Interview questions [1]
Question 1
In the second phone screen, I was asked a design problem: how would you design and develop a method which takes a time-range as parameter and says if the person's calendar is busy in that time-range.
I started off with an OO approach, not directly diving into the method details but the classes (and attibutes) i could be using. and arrived at a mediocre solution ( i guess)
I dont think the interviewer was listening to my approach at all, cause the next thing he tells me, he wants to ask me some terminology questions and if i have knowledge of OO design.