GameChanger logo

GameChanger Ios Engineer Interview Questions
& Process

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

Based on 8 interview experiences · FREE TO READ

3.8 Rounds average
Average Typical difficulty
12.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at GameChanger.

Showing 3 of 8
GameChanger logo
GameChanger

Senior iOS Engineer

Engineering · nearly a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Coding Technical

Had HR Screening, then a Manager Interview. After that, a take home project was assigned. The next interview was a tech interview where we went over the take home project and had a live coding interview. The recruiter mentioned the tech interview would also cover architecture/system design, but the interviewers didn't ask any questions in that area, which felt like a waste of study time. They seemed to be very picky and not understanding of interview nerves during live coding.

Confirmed questions1 question
  • Could you implement undo and redo features for the take-home project?
GameChanger logo
GameChanger

iOS Engineer

Engineering · a year ago

Mid Average Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Technical Coding System Design Behavioral

The interview track was standard: recruiter, hiring manager, a take-home assignment, and then a panel interview. In total, four interviews were scheduled. The first two were technical and happened on the first day, and the next two were culture-focused and scheduled for the second day. I was told that I'd only proceed to the second day interviews if I passed the first day's. The first interview was an hour to review the take-home assignment, which was submitted as a GitHub PR. After that, we had to add a new feature to the assignment in a paired programming session. They mentioned it was okay if we didn't finish within the hour. The interviewers liked my detailed PR, and we finished the whole task with time left for questions. Before coding, I outlined my plan, which they said was good. The second interview was a bit strange. I was given a single sentence (copied below) and then an awkward silence for a few seconds. They said it's usually a whiteboard exercise, but since it was remote, they used a Google doc for notes instead of an online whiteboard app. Because the 'question' was so unclear, I asked many questions and made some incorrect assumptions, which they corrected, and we continued the discussion. I felt it went okay. Less than an hour later, I got rejected. They offered a feedback call, which I accepted. I thought the problem might be with the architecture interview, but I couldn't figure out how it went so poorly that I didn't even get to the culture fit interviews, especially since everyone emphasized culture fit as the top priority. The feedback I received felt completely out of touch with my experience. They said I was unprepared for the PR discussion (because I took 30 seconds to reorient myself?), got stuck during paired programming (really? was it because we debated the meaning of a poorly worded function?), didn't ask clarifying questions during the architecture discussion (impossible not to!), and didn't think high-level enough, getting too caught up in network code details (they gave no indication of what they wanted; I'm an app developer, I discussed app architecture, not backend server protocols). I tried to express my concerns after the feedback, but they cut me off and hung up. In my career, I've never felt so blindsided by an interview. On the plus side, at least I won't have to work with them. There are several negative reviews for iOS roles at this company from recent years, and they all seem accurate. Save yourself the trouble.

Confirmed questions1 question
  • Considering we now have an app that tracks scores, how would you suggest we sync this data to a backend so fans can view the game on their mobile or web clients?
GameChanger logo
GameChanger

iOS Developer

Engineering

Mid Average Positive experience Accept offer 6 rounds
Interview process
Recruiter call Take home Onsite Technical screen Background check Offer
Interview formats
Technical Coding System Design Behavioral Technical

It started with a phone call, then after 3 weeks they scheduled an in-person interview. I also had to submit a small iOS project beforehand. The onsite had iOS app building rounds, a system design interview, two behavioral interviews, and one subject matter expert interview.

Confirmed questions3 questions
  • Normal System design questions
  • Algorithm questions
  • Behavioral questions

GameChanger Ios Engineer Interview Questions

Quoted word for word from GameChanger interview reports.

Considering we now have an app that tracks scores, how would you suggest we sync this data to a backend so fans can view the game on their mobile or web clients?

Read reports

In a live coding session, could you add undo/redo functionality to the SwiftUI app?

Read reports

Could you implement a rule set for a complex SwiftUI application?

Read reports

Could you implement undo and redo features for the take-home project?

Read report

Formats, difficulty and experience

Across all 8 GameChanger interview reports.

Interview formats

Coding 30.4%
Technical 30.4%
Behavioral 26.1%
System Design 13%

Interview difficulty

Easy 12.5%
Average 62.5%
Difficult 25%

Candidate experience

Negative 75%
Positive 12.5%
Neutral 12.5%