The process started with a screening call with the recruiter, which felt more like a sales pitch for the company rather than an actual interview. No questions were asked about my background or experience—just a rundown of how great GameChanger is as a workplace. The recruiter then scheduled a call with the hiring manager. The hiring manager interview was fairly straightforward, covering only resume-based questions. It went well overall. However, things started moving very quickly after that, and I was rushed into the technical rounds without much notice. Pair Programming Round (60 mins – Coderbyte) This was a computer vision-focused coding exercise where I was given a large, complex codebase with multiple files. It was unrealistic to expect anyone to fully understand the code in 5 minutes and start optimizing it immediately. The round included a 15-minute introduction, leaving very little time to actually work on the problem. I managed to modularize parts of the code and write some unit tests, but given the constraints, it was impractical to make significant improvements. The difficulty wasn’t in the problem itself—it was the unrealistic time expectations. System Design Round This round should have been easy, but the interviewer kept changing the requirements multiple times throughout the session. It was unclear what they were looking for, and they seemed unsure about their own expectations. The round was focused on AWS, despite them mentioning "cloud proficiency" in a more general sense. If you're taking this interview, I highly recommend asking the interviewer to clearly define the problem in writing before starting. Otherwise, it can get frustrating quickly. Final Thoughts The technical rounds felt rushed and unstructured, and the expectations weren’t clearly set. If you’re interviewing here, be prepared for ambiguity and time constraints.