I started with a recruiter call that felt pretty relaxed, and I got an email to move forward to a technical interview. After that, things went quiet—no solid next step even after I followed up a few times. The whole process left me feeling stalled and unsure where I stood.
What stood out was how the next interaction timing changed. I later went through a more detailed early sequence: a first behavioral discussion with a product person, followed by a technical round where the focus was system design. I remember being given a fairly large, scenario-style design prompt and having to talk through my thinking, but I didn’t get much follow-up; it felt like the interviewers weren’t deeply aligned with the tools or depth implied by the question. After that second round, I never heard back, and I ended up learning there wasn’t any further step for me.
5 months ago
Difficult Positive India
My process felt fairly technical from the start, with a lot of emphasis on what was already on my resume. I went through a couple rounds after the initial screening phase where the questions were largely aimed at validating my day-to-day engineering skills.
The first part was computer-based MCQs, and then I moved to an interview with two interviewers where they tested my technical knowledge. Across those rounds, the themes were Java and building applications. In a similar thread, my preparation expectation ended up being heavily around databases too—especially SQL details like joins and grouping logic, plus how relational systems compare to non-relational ones.
6 months ago
Easy Positive United States
My process started with a recruiter call that covered general details about my resume and also gave me a picture of what the company expected. After t…
6 months ago
Average Negative Gurgaon, Haryana
My start was campus-style, with the process kicking off after a detailed pre-placement talk that covered the company’s culture and the types of roles …
7 months ago
Difficult Negative Gurgaon, Haryana
My interview journey started with an online take that set the tone for how much time they’d ask me to invest. I was given a platform link and told to …
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 begins with a recruiter call, followed by a technical assessment, and then multiple technical interviews focusing on coding and system design, concluding with a behavioral round. The timeline can vary, with some candidates experiencing delays and a lack of communication about next steps.
Candidates can expect a strong emphasis on core technical skills, including data structures, algorithms, Java, SQL, and system design. The technical interviews often include coding challenges and scenario-based questions that require structured reasoning and problem-solving.
Data structuresAlgorithmsSQL
Behavioral Interviews
The behavioral rounds generally follow a standard format, focusing on candidates' past experiences and situational responses. However, some candidates noted that the behavioral questions could sometimes feel more technical than expected, leading to confusion during the discussion.
Throughout the process, communication skills and cultural fit are assessed, with some interviews including discussions about personal strengths, weaknesses, and career aspirations. Candidates reported that the tone of these conversations could significantly impact their overall experience.
Communication skillsCultural fitSelf-awareness
Overall Difficulty & Candidate Experience
The overall difficulty of the interview process is generally seen as average, but candidates expressed concerns about the emotional weight of the interviews and the lack of closure after the process. Many felt that the experience could be frustrating, especially if they did not receive timely feedback or clear outcomes.
Average difficultyEmotional weightFeedback
Preparation Insights
Candidates recommended focusing on core technical fundamentals, including SQL troubleshooting and DSA, as well as practicing coding problems on platforms like LeetCode. Additionally, being prepared for a structured discussion about past projects and experiences can enhance performance.