My run felt like a tightly timeboxed drive built around a big MCQ gate first. The opening round was 45 minutes with 50 MCQs, and the topics were very specific—DBMS, Operating Systems, OOP concepts, and pseudocode-style questions. They told me the cutoff mattered, and the scale was huge: out of 1385 students from my college, only 101 got shortlisted for the next stage. The pressure came from knowing how much the list shrank so fast.
After that, I moved into additional rounds that kept the focus on fundamentals and DSA. I eventually reached a final step delivered via a live video interview, where they had me solve two DSA problems. One of those problems was directly related to what I’d seen earlier, and the other required me to reason from the same general problem-solving pattern. They also asked me to design a system based on the problem they gave during the interview.
9 months ago
Average Positive India
After a recruiter call, I got an invite about a week later for an online screening. The flow felt pretty structured: first an MCQ test with aptitude, verbal, and technical questions, then an online coding assessment for shortlisted people, and finally interview rounds to decide hiring. The whole thing moved through multiple people and touchpoints, and it felt like the “final evaluation” step was what really mattered.
The MCQ stage was timed and broad, mixing fundamentals with communication-style questions. Once that cleared, the coding assessment was the next gate, and it was clear they were looking for working solutions rather than just theory. After that, I had to go through the interview rounds where they probed deeper into how I thought and explained my approach, rather than expecting me to only produce code.
9 months ago
I went through a pretty classic multi-round loop that started with MCQs and ended with a technical interview that leaned on both data structures and c…
11 months ago
Average Negative Bengaluru
I experienced a tougher-than-average process that felt optimized for elimination. It started with an aptitude + MCQ round, where they emphasized that …
> 1 year
Average Neutral Hyderābād
My process started with a fairly standard screening sequence, but what surprised me was how much the later stages depended on subjective evaluation. I…
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
MCQ Screening Round
The interview process begins with a timed MCQ assessment covering core CS topics such as DBMS, OOP, and algorithms, with a high cutoff that significantly narrows the candidate pool. Expect around 50 questions in 45 minutes, and be prepared for a pass/fail evaluation that can feel intense due to the pressure of elimination.
MCQCS fundamentalsHigh cutoff
Coding Assessment
Following the MCQ, candidates face a coding round that typically includes 5 questions, with a mix of difficulty levels from medium to hard, focusing on data structures and algorithms. Candidates should aim for correctness and efficiency, as only those who solve most problems are likely to advance.
Coding roundDSACorrectness
Technical Interview
The final interview stage often involves a live coding session where candidates must solve problems while explaining their thought process. This round tests not only coding skills but also the ability to communicate effectively under pressure, with questions that may connect back to previous assessments.
Live codingTechnical interviewCommunication
Behavioral and HR Discussion
Some candidates may experience a behavioral or HR interview at the end, focusing on cultural fit and communication skills. This round can include discussions about past projects and personal experiences, providing an opportunity to showcase soft skills alongside technical abilities.
BehavioralHR interviewCultural fit
Pressure and High Standards
Throughout the process, candidates report a consistent feeling of high pressure and high standards, with each round designed to filter out a significant number of applicants. The overall experience can feel competitive and unforgiving, making it essential to perform well at every stage.
High pressureCompetitiveElimination
Communication and Clarity
Candidates noted the importance of clear communication during technical discussions, as interviewers often assess not just the correctness of answers but also the reasoning behind them. Practicing how to articulate thought processes can be beneficial for success in this environment.