After the initial introduction, I was hit with a CP-style problem almost immediately. I was given a Google Doc containing the question, and I was expected to talk through my approach out loud while I worked through it. The pressure was that it wasn’t just about writing—it was about explaining the plan clearly in real time.
I wasn’t able to land a coherent verbal approach during that exchange, and the interviewer ended the interview right after that. The whole interaction felt abrupt and unforgiving: even though I had the doc and time to look at the problem, the conversation didn’t get a chance to turn into a longer problem-solving discussion.
> 1 year
Difficult Neutral Bhopal
My process started as an online assessment that ran through four rounds. The first round was DSA, and then the second round moved into system design alongside core technical topics, with a strong focus on database management system concepts. The third round was centered on my projects, where the questioning went deeper into technical details rather than staying high-level.
After that, there was an HR round at the end. Overall, it was described to me as difficult, and the structure matched that feeling: it moved from algorithms into system design and DBMS fundamentals, then into project-driven technical depth before finally switching to HR.
> 1 year
Average Positive Bangalore Rural
My interview followed a clear, four-round flow. Round one was a DSA round. Round two was more dev-based, but it went pretty deep into my project, with…
> 1 year
Average Positive India
The process started with a DSA question where I worked through merge sort, and I had to also deal with project-related parts alongside it. After that,…
> 1 year
Average Positive Bengaluru
My interview for the SDE intern role started with an unexpected, playful challenge: I had to build a whimsical virtual pet simulation using obscure pr…
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 & Rounds
The interview process typically consists of four rounds: an initial coding assessment focused on data structures and algorithms (DSA), followed by technical rounds that delve into system design, project discussions, and core computer science concepts. The final round often includes an HR interview.
Interview roundsDSASystem design
Coding Assessment
Candidates begin with a coding assessment on platforms like InterviewBit, which includes multiple questions that are generally medium to hard in difficulty, focusing on DSA concepts. Success in this round is crucial for progressing to the interview stages.
Coding testInterviewBitLeetCode
Technical Depth & Project Discussion
Interviews often include in-depth discussions about candidates' projects, requiring them to explain their technical choices and defend their work, which can feel more like a technical defense than a casual walkthrough.
Project discussionTechnical depthDefense
Communication Skills
Interviewers place significant emphasis on candidates' ability to communicate their thought processes clearly while solving problems, making effective communication as important as technical correctness.
CommunicationProblem-solvingTechnical discussion
Difficulty Level & Candidate Experience
The overall difficulty of the interviews is perceived as high, especially in the coding and technical rounds, which can create a challenging atmosphere. Candidates often report feeling the pressure to perform well under scrutiny.
DifficultyPressureCandidate experience
Preparation Insights
Candidates suggest that a strong focus on standard DSA questions and a solid understanding of core CS fundamentals are essential for success, as many felt underprepared for the depth of questions asked.