After the recruiter stage, I moved into a technical interview where the questions were split across a few buckets. I got tested on core Java—OOP basics, collections, and Java 8 style concepts—then on Spring Boot topics like REST endpoints, annotations, and exception handling. The round also included React basics (components, hooks, and how state changes) plus a couple of DSA coding prompts built around arrays and strings. The interviewer felt supportive, asking both theoretical questions and practical ones.
A week or so later, I went into a deeper advanced technical/system design round. This one leaned hard on how I’d structure real systems: high-level architecture, database design and optimization, microservices concepts, and how things connect in practice. AWS basics came up too, including EC2/S3 and deployment understanding, along with scenarios around Spring Boot interacting with a database. The style felt more like working through tradeoffs and my design approach rather than just writing syntax.
8 months ago
Difficult Positive New Delhi
My process was online and tightly controlled. I joined a Zoom meeting using proctoring software, and the format felt intentionally difficult because it was hard to tell exactly how I was being monitored—there was no room to drift. It ran as three rounds, all centered on SQL.
In the first round, I was tested on SQL directly. The second round shifted to projects, but it still stayed SQL-based and medium to hard in difficulty. The third round was HR, which came after the technical filtering.
8 months ago
Average Positive Pune
This round was run by two US-based engineers, and it was very hands-on. I had to complete a live React coding task using TypeScript while they watched…
9 months ago
Average Positive India
I went through a pretty classic three-round path. In round one, it started like a screening where we talked about product development background and t…
> 1 year
Average Negative United States
I spent nearly five hours in the interview loop, and that time didn’t translate into a clear result. The initial call with the manager felt promising,…
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 multiple rounds, starting with a recruiter call, followed by technical interviews focusing on coding, system design, and managerial discussions. Candidates should prepare for a structured sequence that often emphasizes technical breadth before delving into deeper system architecture topics.
Candidates can expect a strong emphasis on technical skills, including core programming concepts, data structures, algorithms, and system design. Interviews often include live coding tasks, with a focus on clean code and problem-solving under pressure.
Data structuresAlgorithmsLive coding
Behavioral & Managerial Assessment
Interviews include behavioral assessments where candidates discuss past projects, team dynamics, and problem-solving approaches. This part of the interview aims to evaluate leadership qualities and communication skills in a technical context.
Behavioral questionsProject discussionLeadership
Communication & Follow-up Issues
Candidates frequently report poor communication from the company regarding interview outcomes and feedback, leading to frustration. It's advisable to follow up proactively for updates, as many candidates experienced delays or silence after interviews.
CommunicationFollow-upFeedback
Interview Difficulty & Pressure
The interview process is described as intense and challenging, with candidates feeling pressured to perform well in a tightly controlled environment. Many interviews are proctored, adding to the stress of real-time coding tasks.
High pressureProctored interviewsIntense difficulty
Inconsistency in Interview Experience
Candidates have noted inconsistencies in the interview experience, including varying levels of interviewer professionalism and clarity of questions. It's important to be prepared for different styles and paces of questioning across rounds.