My process ended up being very compressed. I met with a manager and one of the developers on the team, and it stayed at a single interview round where I was offered the position. There weren’t any problem-solving questions; it was mostly technical questions tied to the team’s tech stack and Git.
The interview atmosphere felt friendly and practical. I talked through my experience and the kind of work I’d done, and the whole thing didn’t feel like an interrogation or a long gauntlet. Even so, I didn’t end up moving forward in the end, and I remember it more for the directness than for any intense technical hurdle.
5 months ago
Average Positive Toronto, ON
After a recruiter chat, I had about a week’s wait before moving to the hiring manager. The whole process ended up being online and stretched to roughly a month total, which made the pacing feel a bit stop-and-go.
Next came an additional interview with people in the same role, followed by a final interview back with the hiring manager. The vibe felt structured and fairly straightforward: enough conversations to cover both the job fit and the technical side, without it turning into a maze of back-to-back screens. I walked away feeling like I’d had multiple chances to show my background and match the role, even though I wasn’t selected in the end.
6 months ago
Average Negative Montreal, QC
A recruiter reached out to me and set up the interview, but the experience soured quickly. The recruiter came across as quite rude and lacked basic re…
7 months ago
Average Positive Montreal, QC
The first contact was an introductory call for about thirty minutes. It was meant to understand what I was interested in and to see whether my motivat…
9 months ago
Average Positive Pune
My interview path felt like it had clear steps and decent momentum, but the technical expectations were real. First I had an HR call to talk about the…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Flow
The interview process typically includes an initial HR screening followed by one or more technical interviews, often with a mix of coding challenges and discussions about past projects. The overall flow is generally structured, with candidates appreciating the clarity of steps involved, although some experienced delays and communication issues.
HR screeningTechnical interviewsStructured flow
Technical Expectations
Candidates should prepare for a range of technical questions, particularly focused on C++ concepts, coding challenges, and sometimes game-related technical knowledge. The difficulty level varies, but many report it as average to challenging, with a focus on practical application and problem-solving skills.
C++Coding challengesTechnical depth
Behavioral & Motivational Questions
Interviews often include discussions about candidates' backgrounds, motivations, and past experiences, blending technical evaluation with softer skills. This approach helps interviewers gauge cultural fit and personal alignment with the company's values.
The general atmosphere of interviews is described as friendly and approachable, with interviewers aiming to create a comfortable environment for candidates. However, experiences vary, with some candidates reporting unprofessional interactions, particularly during the initial recruiter stages.
Candidates frequently express frustration with the lack of timely communication and follow-up after interviews, including delays in receiving feedback or decisions. This aspect significantly impacts the overall experience, leading to feelings of uncertainty and dissatisfaction.
CommunicationFollow-upFeedback delays
Overall Experience & Outcomes
While many candidates find the interview process manageable and fair, a significant number do not receive offers, leading to mixed feelings about the experience. The time investment and lack of closure are common points of contention, affecting candidates' perceptions of the company.