GSN Games logo

GSN Games Game Developer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

2 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at GSN Games.

Showing 3 of 5
GSN Games logo
GSN Games

Game Developer

Engineering · more than a year ago

Intern Average Positive experience No offer 1 round
Interview process
Technical screen
Interview formats
Technical Behavioral

The interview process was good. There were two interviewers who asked questions relevant to the role. They also had some scenario-based questions, which were good. That's all.

Confirmed questions5 questions
  • Questions about algorithms
  • Questions about Unity
  • Questions about logic
GSN Games logo
GSN Games

Game Developer

Engineering · more than a year ago

Entry Easy Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical Coding

So first, they say hello and ask you to tell them about yourself. Then, they want to see what you know about the Unity engine and all the different parts of it. They'll ask you some stuff about C# and then have you write a little bit of code.

Confirmed questions1 question
  • What made you decide to go into this line of work?
GSN Games logo
GSN Games

Game Developer

Engineering · more than a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Technical screen Technical screen
Interview formats
Technical Coding Technical

The first round was about basic Unity and OOPS, C# programming theoretical questions. The second round was a coding round with a lengthy program and some theoretical questions. The interviewer didn't know the logic himself and expected me to complete the program and get it to an executable state. He then tested if the logic was fine by passing inputs and executing the program. By then, it had been more than 1.5 hours, which had already made me bored with the interview. I believe an interviewer should know the logic and only then can they analyze the skill of a developer with hints. Overall, not a good way to conduct a coding interview, and the interviewer himself isn't skilled enough to judge anyone else.

Confirmed questions2 questions
  • Can you explain Unity coroutines, SOLID principles, OOPS, and C# basics?
  • How would you convert a number to words, like 3456 to 'three thousand four hundred...'?

GSN Games Game Developer Interview Questions

Quoted word for word from GSN Games interview reports.

How would you convert a number to words, like 3456 to 'three thousand four hundred...'?

Read reports

Can you explain Unity coroutines, SOLID principles, OOPS, and C# basics?

Read reports

Formats, difficulty and experience

Across all 5 GSN Games interview reports.

Interview formats

Technical 53.8%
Behavioral 23.1%
Coding 23.1%

Interview difficulty

Easy 20%
Average 80%
Difficult 0%

Candidate experience

Positive 40%
Negative 40%
Neutral 20%