After a recruiter call, the process moved pretty quickly into a small set of technical screens. My first round was focused on DSA where I had two LeetCode-style problems, both on the medium side, and I spent about an hour working through them. A week didn’t drag on too long, and soon after I got another technical check.
That second round leaned more toward core fundamentals and practical knowledge. I was asked questions around networking and Linux commands, and there was also a puzzle thrown in to see how I handled ambiguous problem statements. Later, the process shifted into manager-style conversations where I discussed my resume and walked through my past projects at more depth. The final step was an HR round.
3 months ago
Difficult Positive Bengaluru
My interview was run entirely on HackerRank with both video and audio staying within the platform. The prompt itself was a classic medium LeetCode-style challenge that combined binary search with prefix sum, and it felt like one of those problems where the right approach mattered more than just coding speed.
What stood out was how supportive the interviewer was during the session. Even though the question was non-trivial, the guidance made it feel less like a “gotcha” and more like an attempt to see how I reasoned. I also remember the recruiting team being very friendly, which helped the whole thing feel smoother emotionally.
4 months ago
Average Negative India
The first thing that threw me off was timing and attention. The interviewer joined late, roughly 15–20 minutes after the session started, and then I w…
4 months ago
Average Positive Bengaluru
My process started with an HR outreach and moved into interview slots quickly, but the early rounds were where I felt the biggest swing in experience …
11 months ago
Average Positive Gurgaon, Haryana
My interview journey had a clear sequence: DSA first, then machine-coding and design, and finally a deeper project conversation. I started with two DS…
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
Technical Screening
Candidates can expect a mix of data structures and algorithms (DSA) questions, often in a LeetCode-style format, focusing on problem-solving skills and coding proficiency. The difficulty level is generally medium, with some candidates noting a supportive interviewer approach that helps manage the challenge.
DSALeetCodeCoding proficiency
Core Technical Knowledge
Interviews often include questions on core technical concepts such as networking, Linux commands, and specific programming languages like JavaScript and React. Candidates should prepare for practical applications of these fundamentals in addition to coding challenges.
NetworkingLinuxJavaScript
System Design and Architecture
Expect discussions around system design, including low-level design (LLD) and high-level design (HLD) questions, where candidates may be asked to design systems or components and discuss scalability and architecture principles.
System designHLDLLD
Behavioral and Managerial Rounds
Candidates will likely encounter managerial interviews focusing on past experiences, project discussions, and cultural fit. These rounds tend to be more conversational and reflective, assessing alignment with the company's values and expectations.
BehavioralCultural fitProject discussion
Interview Coordination and Experience
The overall interview process is reported to be well-coordinated, though experiences can vary significantly based on interviewer engagement and timing. Candidates should be prepared for potential delays or variations in interview structure.
CoordinationInterviewer engagementTiming
Feedback and Outcome Transparency
Many candidates expressed a desire for clearer communication regarding feedback and outcome decisions, as some reported feeling disconnected from the evaluation process despite performing well in interviews.