Recruiter reached out on LinkedIn. The first call was a fit conversation, with an honest mention that the role expects gradual movement toward the company's in-house engine and C++, I appreciated that they mentioned this early instead of me finding out later. Then came the technical interview with two senior engineers. We went through my solution together and spent most of the time discussing architecture and high-level decisions instead of focusing on small details. Finally, there was a culture-and-team conversation with the hiring manager. The full process took just over four weeks from first contact to written offer. Communication was consistent throughout the process, and the recruiter kept me informed on timing even when things were waiting on the team side. The offer included all the key information in writing, and I had several days to review it before making a decision.
Interview questions [2]
Question 1
Could you walk us through your most recent commercial project and the architecture decisions behind it?
I applied online. I interviewed at Playrix (Armenia, SC)
Interview
Recruiter call to align on expectations, then a technical interview focused on C++ gameplay code and a short live coding section. Final round was a conversation with the team lead about past projects and how I approach debugging on a live product. About two and a half weeks end to end.
Interview questions [2]
Question 1
Tell us a bit about your background and what you worked on in your previous role.
Started with a recruiter screen, then a portfolio review where I walked through past LiveOps work and the reasoning behind specific decisions. After that there was a design exercise sent home, and finally a panel interview with two senior designers and a producer. The whole process took about three and a half weeks, communication between stages was clear.
Interview questions [1]
Question 1
Could you walk us through your experience at your most recent company?