I started with a recruiter outreach just to schedule things, and the process felt quick and straightforward. After that email, I did a basic phone screen interview. That call was mainly about me—my resume and my background—with the recruiter and interviewer both coming across as pleasant.
Next came a video call where the format was split between more personal, background-style questions and technical topics. I remember it felt balanced rather than purely coding-heavy, and I was able to walk through my experience clearly. Even though I didn’t move on to later rounds, the overall experience stayed positive—friendly people, clear communication on what would happen next, and no awkward surprises.
5 months ago
Average Negative United States
I went through a multi-round loop that started with an initial recruiter screen and then moved into a panel situation. In that panel, I spoke with the head of Cloud Engineering along with a couple of engineers, and the engineers were engaged and interested in my answers. The manager, though, seemed distracted, and near the end I asked questions about culture. The response I got was sharp and dismissive, which threw off the whole vibe and left me feeling like my questions were being treated unfairly.
I never received a clean follow-up after that interview, even after I sent messages to the recruiter. My application also stayed stuck as “under consideration,” and the waiting dragged out longer than it should have. What made it worse was that, elsewhere in the process, other rounds had gone well on paper—I got positive feedback in earlier stages and even referrals forward—until my candidacy got put on hold.
> 1 year
Average Positive Bengaluru
My interview process started with an online coding test that set the tone for the rest of the pipeline. The test itself was about DSA and lasted aroun…
> 1 year
Average Positive Bengaluru
The process felt unusually smooth and organized. I received regular updates from the hiring team, and from start to finish I finished everything in ab…
> 1 year
Average Positive Church Street
My timeline started with a structured, three-part sequence after I interviewed. The first round took about an hour and was heavy on technical work—adv…
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 & Timeline
The interview process typically starts with a recruiter call followed by a series of technical and behavioral interviews, often culminating in an onsite or virtual interview. The overall timeline ranges from about two weeks to over a month, with some candidates reporting smooth and organized communication throughout.
Recruiter callOnsite interviewTimeline
Technical Assessments
Candidates can expect a mix of coding assessments focusing on data structures, algorithms, and system design, often including online tests or HackerRank-style challenges. The technical interviews are generally thorough, covering both foundational and advanced topics relevant to the role.
Coding assessmentData structuresSystem design
Behavioral & Managerial Rounds
Behavioral interviews are integrated into the process, often assessing cultural fit and past experiences through structured questions. Candidates should prepare for managerial discussions that may focus on their resume and project experiences.
The level of communication varies, with some candidates experiencing prompt updates and clear feedback, while others report delays and unresponsiveness. It's important to follow up if communication stalls, as some candidates felt frustrated by a lack of clarity.
CommunicationFeedbackFollow-up
Interview Atmosphere
Most candidates describe the interview atmosphere as friendly and supportive, with interviewers showing genuine interest in their responses. However, some candidates noted instances where the demeanor of certain interviewers felt dismissive or distracted, impacting their overall experience.
Friendly atmosphereEngagementInterview demeanor
Preparation Insights
Candidates suggest focusing on both technical skills and behavioral responses, especially in relation to past experiences and cultural fit. Practicing coding under time constraints can also be beneficial, as the pressure of timed assessments was a common challenge.