After a recruiter-style pre-placement discussion, I was asked to complete a coding test, and then I went into a project-building round. The people I cleared these earlier steps with were then invited for two rounds of technical interviews, followed by an HR round. The overall flow felt pretty sequential, like each step acted as a gate before the next set started.
The hardest part for me was keeping momentum across the move from pure coding into building. By the time I reached the technical interviews, I was already thinking about how to explain my thinking clearly, not just produce working logic. Once I got through the technical portion, the HR conversation felt like the last checkpoint rather than another technical hurdle.
7 months ago
Average Negative Cochin
My process was a five-round journey that started with an aptitude test, moved into a programming round, then turned into a buildathon, followed by a technical interview and finally HR. The whole thing was time-consuming and demanded a lot of effort, and it felt like I kept investing more energy as each stage passed.
During HR, I was told that the final result would come via email within a week. I waited much longer than that—more than three weeks—and I never received any response at all. Later, I found out that candidates from other colleges had already been told their outcomes, which made the silence even harder to take. The lack of closure felt like being ignored after putting myself through a long sequence.
7 months ago
Difficult Positive Eranakulam
Before I even reached the “interview” part, the process filtered me through elimination-style rounds that felt very DSA and fundamentals heavy. First …
8 months ago
Difficult Neutral Cochin
My process started with a coding round where I solved DSA-focused questions, and then I moved straight into a hackathon-style session. The hackathon w…
10 months ago
Average Positive Cochin
My interview path was structured across multiple technical stages and then HR. It started with a coding round that was challenging for me—medium to ha…
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 & Flow
The interview process typically follows a structured sequence starting with an aptitude or coding test, followed by multiple technical rounds focused on DSA and system design, and concluding with an HR round. This sequential flow acts as a gatekeeping mechanism, where each stage builds on the previous one, making preparation for each step crucial.
Interview stagesSequential flowGatekeeping
Technical Rounds Focus
Candidates can expect a strong emphasis on data structures and algorithms (DSA) during the technical rounds, often requiring problem-solving under time pressure and the ability to explain solutions clearly. The difficulty tends to increase as candidates progress, with later rounds incorporating system design and broader software engineering topics.
DSASystem designProblem-solving
Project & Build Sessions
Some candidates participate in hackathon-style build sessions where they must develop a working solution based on given requirements, often under tight time constraints. These sessions require not only coding skills but also the ability to articulate the thought process and logic behind the solutions created.
Build sessionHackathonArticulation
Behavioral & HR Rounds
The HR round often shifts focus from technical skills to personal fit, discussing strengths, weaknesses, and experiences in a conversational manner. While technical questions may still arise, the emphasis is on cultural fit and how candidates handle interpersonal discussions.
HR roundCultural fitBehavioral questions
Communication Expectations
Throughout the interview process, candidates are expected to communicate their thought processes and reasoning clearly, especially during technical discussions. A lack of clarity or mismatched expectations regarding what interviewers are looking for can lead to confusion and impact outcomes.
CommunicationExpectationsClarity
Feedback & Follow-Up
Candidates have reported frustrations regarding the lack of timely feedback after the interview process, with some experiencing significant delays in receiving outcomes. This can lead to feelings of uncertainty and dissatisfaction, regardless of the technical experience itself.