My process started with a recruiter step, and then I ended up doing three interviews total. Two of them were DSA-focused, and the last one was HR.
In the first DSA round, I was asked two medium LeetCode-style problems. After that, the second DSA interview went a bit tougher: I worked on one medium-hard LeetCode question, and I also got pulled into an OOPs concept discussion as part of the same round.
4 months ago
Difficult Positive Bengaluru
After the recruiter call, I had a process that felt unusually structured and transparent, almost like they told me what each round would test before I even walked into it. It made it easier to focus, because the technical interviewers didn’t treat it like a test of memorized answers—they wanted to understand the trade-offs in my thinking and kept the conversation moving.
The technical flow included a hiring-manager touchpoint early to check alignment, and then more technical rounds afterward. Across the interviews, I ended up facing a mix of DSA plus design discussions in the LLD/HLD space, and each interviewer encouraged deeper back-and-forth rather than rushing to a single correct solution. One of the hiring-manager discussions was more of a techno-managerial conversation, which helped connect the coding and design topics back to how I’d operate on the team.
5 months ago
Average Negative India
My interview journey started with some real scheduling chaos. Early on, rounds kept getting rescheduled—first the initial round, and then the next one…
6 months ago
I interviewed for a Senior Software Engineer role in Bengaluru, and the process was centered around a 60-minute PS/DS round. That session was the whol…
> 1 year
Difficult Neutral Bengaluru
The process was a straightforward three-round loop: two coding rounds followed by an HR conversation. The first coding round felt easy to moderate, an…
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 consists of three rounds: two technical interviews focused on data structures and algorithms, followed by an HR conversation. The overall timeline can vary, with some candidates experiencing delays and rescheduling issues, while others report a smooth and organized flow.
Interview roundsTimelineOrganization
Technical Problem Solving
Candidates can expect a strong emphasis on technical problem solving, particularly around data structures, algorithms, and sometimes object-oriented design. The interviews often focus on reasoning and thought processes rather than just arriving at the correct answer, with interviewers encouraging discussion and collaboration.
DSAProblem solvingCollaboration
Design Discussions
Some interviews include discussions on system design, both low-level and high-level, where candidates are expected to articulate their thought processes regarding architecture and scalability. This aspect is integrated into the technical rounds and can be a significant part of the evaluation.
System designArchitectureScalability
Behavioral & Cultural Fit
The final HR round often focuses on cultural fit and alignment with the company’s values, with interviewers assessing how candidates would integrate into the team. This round can be pivotal, with some candidates noting it as the deciding factor in the outcome.
Cultural fitHR roundValues alignment
Communication & Follow-Up
Candidates have reported mixed experiences regarding communication throughout the process, with some feeling well-informed and others experiencing delays or a lack of follow-up. Clear communication from HR is noted as a positive aspect, while disorganization can lead to frustration.
CommunicationFollow-upHR responsiveness
Overall Experience & Difficulty
The overall difficulty of the interview process is described as mid-to-challenging, with candidates noting that while the questions are demanding, the interviewers create a supportive environment. However, some candidates felt that the process could be disorganized or unprofessional at times.