After an HR screening, I moved into two technical rounds and then wrapped up with a managerial discussion. The whole thing felt fairly smooth, and the difficulty matched that “average” level—nothing that completely blindsided me, but it still required solid problem-solving.
Across the technical rounds, I talked through my project experience and got questions around JavaScript, React, and Node.js, plus REST API concepts. I also had to cover database-related fundamentals, and the interviewers stayed focused on how I approached problems rather than trying to trick me.
3 weeks ago
Average Positive Pune
My interview felt fairly grounded in resume details. The conversation started with questions connected to what I’d already written down—projects, experience, and the key tech I claimed—and then it expanded into basic programming and OOP concepts. I remember being asked about OOPS explicitly and also facing SQL-related questions.
There was also a coding component, but it stayed on the easier side—more about testing whether I could actually implement basic ideas than solving anything extremely complex. In the same technical discussion, I handled straightforward DSA-style prompts that were meant to gauge problem-solving rather than trick me.
1 month ago
Average Positive New Delhi
My interview started with a discussion of my project background, then shifted into a more focused deep dive. I was asked about the streaming-related w…
1 month ago
Average Negative Canada
My interview call was on Teams, and from the start the tone went off. The interviewer joined late and then began asking questions in a very abrupt, al…
1 month ago
Average Positive Pune
My selection process started with an online aptitude phase that felt like an elimination filter. I went through quantitative aptitude, logical reasoni…
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 starts with an online assessment followed by technical rounds that include coding and project discussions, often culminating in an HR round. Candidates noted that the overall structure felt organized and predictable, although some experienced delays in receiving follow-up communication after interviews.
Structured processTimelineHR round
Technical Rounds Focus
Technical interviews often emphasize core programming concepts, particularly in Java, OOP principles, and practical problem-solving scenarios. Candidates reported that questions were generally aligned with their resumes and aimed at assessing both theoretical knowledge and practical application.
JavaOOPPractical problem-solving
Project Experience Discussion
Candidates frequently engaged in discussions about their past projects, with interviewers probing for detailed explanations and scenario-based questions related to the technologies used. This focus on real-world application required candidates to articulate their thought processes and decision-making clearly.
The HR round typically assesses cultural fit, communication skills, and career aspirations, often involving questions about teamwork and adaptability. Candidates felt that this round was less technical and more focused on personal alignment with the company's values and expectations.
Overall, candidates described the difficulty of the interviews as average, with some noting that while the questions were straightforward, they required careful thought and clarity in responses. Many felt that the interviewers aimed to evaluate their problem-solving abilities rather than trick them with difficult questions.
Average difficultyProblem-solvingClarity in responses
Communication & Follow-up Issues
Several candidates expressed frustration with the lack of communication following their interviews, particularly regarding updates on their application status. This lack of transparency left some feeling deflated, despite having completed the technical portions successfully.