My process started with a virtual interview. After that, I moved into a programming assessment where I had to work on paper, aiming for something functional rather than perfectly compiling code. It felt like a practical test of whether I could reason through the problem and produce a working solution, even without running it.
Once the technical part was done, I expected the rest to be fairly quick, and it mostly was. I also went through a group discussion stage focused on communication and teamwork before the final interview sequence. The overall flow stayed structured and predictable from round to round, and after the remaining steps the process moved toward the medical check.
5 months ago
Average Neutral India
I began with an aptitude test: thirty questions to finish in one hour, heavily numerical. It also required a solid command of English, and I could feel the pressure of that constraint as I worked through the questions. The difficulty here was the gatekeeper—people who weren’t strong at aptitude clearly struggled to move forward, and only a small fraction passed the cut.
After clearing that screen, the next stage shifted into group discussion. I was put in a setting where communication, confidence, and teamwork were what they were really watching, and I had to explain and think on my feet while staying engaged with the group.
6 months ago
Easy Negative Fremont, CA
My interview process felt unusually streamlined and not especially hard. I went into a technical-focused conversation where many of the questions cent…
7 months ago
Average Negative Ottawa, ON
My first step was an HR conversation, and it didn’t drag on—I was mainly going through standard fit and background questions. Less than a week later, …
12 months ago
Average Positive Fremont, CA
I went through a more direct, conversation-heavy path. HR and the engineering manager interviewed me, and the first part was mostly common behavioral …
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
Initial Screening & Aptitude Test
Candidates typically start with an aptitude test that includes numerical and verbal reasoning questions, which serves as a significant gatekeeper for advancing in the process. Strong performance is crucial, as only a small fraction of candidates pass this initial screening.
Aptitude testNumerical reasoningVerbal reasoning
Technical Assessment & Programming Exercise
Following the initial screening, candidates engage in a technical assessment that often includes a paper programming exercise, where the focus is on producing functional solutions rather than perfectly compiling code. This stage tests problem-solving abilities under constraints.
A group discussion round is common, where candidates are evaluated on their communication, teamwork, and ability to articulate thoughts in a collaborative setting. This round emphasizes quick thinking and engagement with peers.
Group discussionTeamworkCommunication skills
Technical Interviews & Project Discussions
Candidates often participate in technical interviews focused on their past projects and relevant programming languages, with interviewers looking for clear technical storytelling and understanding of fundamental concepts. The atmosphere can vary, impacting the overall experience.
The interview environment can be described as unstructured or even oppressive at times, leading to discomfort despite the technical content being manageable. Additionally, many candidates report delays and a lack of follow-up communication post-interview, which can leave them feeling uncertain about their status.
Interview environmentFollow-up communicationUnstructured process
Behavioral Questions & Work Style Assessment
Behavioral questions focusing on work style, stress management, and decision-making under pressure are prevalent, indicating that the company values candidates' approaches to real-world challenges as much as their technical skills.