I applied via the company link and was contacted by email to get the first meeting scheduled. That initial conversation focused mainly on my past experience—especially my background working in a technical support engineering type role—so it felt like an intro to my history and fit rather than a deep technical checkpoint.
After that, I moved to a second interview with an operations manager. The tone felt more like a hiring alignment conversation than a coding session, centered on how my experience mapped to how the team ran day-to-day. Overall it didn’t end with an offer, and the process felt fairly straightforward in structure, just focused on fit and experience.
1 month ago
Easy Negative Tel Aviv-Yafo
I applied through the website and heard back from HR. After that, I had an interview arranged via a Zoom-style setup, and later I also met the hiring manager.
What stood out most was the lack of closure: after the hiring manager interview, things went quiet and I never heard back, even after follow-ups. It felt like a standard process up front, but the post-interview communication was missing—if they were going to reject me, at least it would have helped to receive a clear response.
3 months ago
Average Negative Bengaluru
My loop started with a campus-style path where I ended up going through three rounds: a first technical screen, then a manager round, and finally an H…
4 months ago
I came in through a referral and waited a bit—around two weeks—before HR reached out and scheduled my interview for the same Friday. The process felt …
4 months ago
I applied through a referral and waited about two weeks before HR scheduled my interview on a Friday. The first round was a fairly tight coding sessio…
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 involves multiple rounds, starting with a recruiter call, followed by technical screens and managerial discussions. Candidates noted that the timeline can vary significantly, with some experiencing long gaps between interviews and a lack of closure after the final round.
Recruiter callMultiple roundsTimeline variability
Technical Coding Challenges
Candidates faced coding challenges that were primarily LeetCode-style problems, focusing on data structures and algorithms. Common topics included grouping anagrams, finding the K-th largest element, and other algorithmic tasks, with varying levels of difficulty reported.
LeetCodeDSACoding challenges
Behavioral & Fit Interviews
Behavioral interviews often emphasized cultural fit and past experiences, with questions designed to assess problem-solving approaches and team alignment. Candidates reported that these discussions were generally respectful and aimed at understanding their reasoning and project experiences.
Behavioral questionsCultural fitProblem-solving
Technical Depth & Domain Knowledge
Interviews frequently delved into specific technical domains, such as networking fundamentals, cloud-native concepts, and system design. Candidates were expected to explain concepts in depth, often requiring a strong grasp of both theoretical and practical aspects related to the role.
NetworkingSystem designTechnical depth
Communication & Follow-Up Issues
Several candidates expressed frustration over poor communication post-interview, including a lack of feedback and follow-up after the process concluded. This left many feeling uncertain about their performance and the overall outcome.
CommunicationFeedbackFollow-up
Presentation & Group Discussions
Some candidates experienced presentation-heavy components or group discussions as part of their interviews, which focused on evaluating communication skills and the ability to engage an audience. This aspect was noted as particularly demanding and less common than standard technical interviews.