After applying, the process felt fairly straightforward. I started with a recruiter-style conversation where the first part was mostly about why I wanted to work there. Then I had a technical screen that was LeetCode-style—coding-focused and pretty standard in structure.
Overall, the difficulty matched what I expected. The only thing that really stood out to me was how the technical work was presented, including the sense that they were pushing fairly quickly through the steps. I left feeling like I had done the right things for the format I was given, but I didn’t end up getting an offer.
5 months ago
Average Negative Bengaluru
My process started with a recruiter discussion where I was upfront about the level and expectations—specifically targeting 26 LPA given what I was already making (18 LPA). They agreed to that upfront, and at first everything sounded like it was moving in the right direction.
Then the timeline suddenly got rushed. They told me the role needed to close quickly and asked me to come in person, compressing all rounds into a single day. I traveled around 25 km for it. The interviews themselves went well, and they even had me take a UCAT test, which I cleared. After that, I was waiting for the HR discussion.
6 months ago
Average Neutral Burnaby, BC
I applied through LinkedIn and, about a week later, I got an email to coordinate times for a recruiter call. That call led into an OA. I submitted the…
10 months ago
Average Negative Burnaby, BC
The loop started with a recruiter call. After they said my profile stood out and that they liked it, I moved into an online assessment. Then I went th…
10 months ago
Easy Neutral Burnaby, BC
My interview path was pretty compact: a phone screen first, then an online test, and finally a final round. The structure matched what I expected from…
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
Recruiter Interaction
The interview process typically begins with a recruiter call that focuses on the candidate's interest in the role and expectations. Candidates noted that this stage is generally straightforward but can vary in depth and engagement.
Recruiter callExpectationsInterest
Technical Assessment
Candidates undergo a technical screening that often includes coding questions similar to LeetCode problems, with some also facing additional cognitive tests like the UCAT or CCAT. The technical questions can vary in difficulty and format, so preparation across multiple areas is recommended.
Technical screenLeetCodeCognitive tests
Interview Structure
The interview process typically consists of multiple rounds, often including back-to-back technical interviews with various team members and a final HR discussion. Candidates reported a mix of formats, including in-person and online assessments, with some experiencing a compressed schedule.
Interview roundsBack-to-backHR discussion
Communication and Feedback
Many candidates expressed frustration with the lack of communication and feedback throughout the process, especially after interviews. Delays in updates or complete silence from HR were common themes, leading to a feeling of unprofessionalism.
CommunicationFeedbackSilence
Interview Environment
The atmosphere during interviews can vary significantly, with some candidates experiencing friendly and supportive interactions, while others faced rushed or unfriendly interviewers. This can impact the overall candidate experience.
Interview environmentSupportiveRushed
Outcome and Expectations
Candidates often left the process without offers, despite feeling prepared and capable. Many noted that the outcome did not align with their expectations based on the interview experience, emphasizing the importance of managing expectations.