Great process, couple of interviews and lots of technical problems they do count the behavioral interview a lot so be prepared to be able to present and demonstrate your skills. At the end of the day their hiring team is super nice and help you with any questions that you have
Interview questions [1]
Question 1
Algorithms, make sure you know how to fix certain coding problems leet code is your best friend
I got a screening, behavioral, then 7 interviews for the final phase, around 4 coding interviews, 3 behavioral. All leetcode hards, behavioral asks about experience situations, one technical interview was more architectural.
The interview process was structured, transparent, and challenging. It started with an online application followed by an initial recruiter screening, where basic skills, experience, and role expectations were discussed.
Next came technical rounds — usually two to three online coding interviews through Google Meet. Each round involved solving data structures and algorithm problems on a shared editor while explaining the thought process out loud. For software roles, the questions often focused on problem-solving, system design, and optimization.
If you perform well, you’re invited for on-site (or virtual on-site) interviews, typically consisting of four to five rounds covering coding, system design, and behavioral interviews based on the “Googleyness” criteria — how well you collaborate, take ownership, and approach challenges.
The entire process is highly organized and consistent, with regular communication from the recruiter about next steps. Feedback is usually given within a week or two. Overall, it’s a rigorous but fair process that tests both technical depth and problem-solving mindset.
Interview questions [1]
Question 1
One of the questions I was asked during the interview was:
“Given an array of integers, find the length of the longest subarray whose sum is equal to zero.”
They expected me to explain my thought process clearly, discuss different approaches (like brute force vs. using a hash map for optimized time complexity), and then write clean, efficient code while handling edge cases.
