I applied off-campus and ended up with a pretty straightforward three-round process that felt easy to manage. It started with a short screening call where the conversation stayed on basics—things like overall fundamentals and the kind of core topics you’d expect before getting into anything deep.
After that, I moved into a technical round that lasted around half an hour. The questions stayed at an approachable level and focused on fundamentals like programming and related areas, rather than anything overly tricky. I remember feeling like the whole flow was smooth and friendly, and the interviewers made it feel comfortable rather than intimidating.
7 months ago
Average Positive Bengaluru
After the initial screening, I went into an assessment-style flow that felt very “structured” about checking different dimensions. I had an aptitude test first to gauge logical thinking, then a coding round focused on programming basics. There was also a communication or speech assessment component, and finally a face-to-face interview where they evaluated technical knowledge, problem-solving, and confidence for a GET-type role.
What made the process feel intense wasn’t the number of steps so much as the format itself. During the interview with the coding component, I had to share my screen and write the code directly in front of them, all while the interview was happening. That combination of live coding plus the expectation to present it while being watched added pressure.
11 months ago
Average Positive New Delhi
My process felt structured and a bit more technical than I expected, but still “smooth” overall. I had an HR step plus technical interviews, and the t…
12 months ago
Average Positive Pune
My interview sequence was pretty direct and focused on specific areas. The first round was mainly basic AI and ML questions, and then the second round…
> 1 year
Difficult Neutral Chennai
I went through a final-stage technical interview that lasted for more than an hour, and it felt like the process really got into the details. The pane…
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 consists of an initial HR screening followed by multiple technical rounds, often including a mix of live coding, problem-solving, and behavioral assessments. Candidates noted that the structure felt organized, though the number of steps varied across experiences.
HR screeningTechnical roundsStructured process
Technical Focus & Topics
Technical interviews often emphasize core programming fundamentals, with a notable focus on Java, coding basics, and practical applications such as CI/CD and API testing. Candidates should be prepared for both theoretical questions and practical problem-solving scenarios.
JavaCI/CDProblem-solving
Behavioral & Fit Assessment
Several interviews included a strong behavioral component, assessing candidates' fit within the company culture and their problem-solving approaches through scenario-based questions. This aspect is crucial for demonstrating communication skills and alignment with company values.
Behavioral questionsCultural fitScenario-based
Live Coding & Pressure
Candidates reported experiences with live coding sessions where they had to solve problems in real-time while sharing their screens. This format can create additional pressure, so practicing coding under observation is advisable.
Live codingScreen sharingPressure
Communication & Follow-Up
Some candidates experienced delays or lack of communication following interviews, which affected their overall impression of the process. Clear and timely follow-up is important for maintaining candidate engagement and trust.
CommunicationFollow-upCandidate experience
Overall Difficulty & Candidate Sentiment
The difficulty of the interviews varied, with some candidates finding them manageable while others faced intense technical questioning. Overall, candidates appreciated the supportive atmosphere but expressed frustration when offers did not follow positive experiences.