I went through a Java-heavy process that felt very structured and fully technical. Over four rounds total, each conversation was focused on different slices of the same skill set: DSA, OOPs, and core Java concepts, with a clear expectation that the DSA questions would be solved in Java.
The first two rounds leaned more heavily toward DSA plus OOPs. Later rounds shifted even more into Java and OOPs, so the overall arc moved from pure problem-solving toward applying those concepts more broadly. Even though it never felt random, it did feel like each round expected me to be equally strong across multiple areas, not just one.
4 months ago
Average Positive India
My recruitment process started with an online assessment that tested aptitude, coding, and communication skills. After that, I went into a group discussion round, and then I had two interview rounds that were more about role fit, knowledge, problem-solving, and how I worked with others.
What stood out to me was that the questions were very situation-based and role-based rather than just abstract technical trivia. I liked that it sounded connected to how the job would actually feel, but I also felt the flow of the interviews could’ve been smoother and more considerate.
5 months ago
Difficult Positive Bengaluru
My process started with pre-interview sessions that covered the company’s journey and what their interview process looked like. That made the next ste…
9 months ago
Average Negative United States
My interview experience took a sharp turn right away. The interviewer showed up late, didn’t introduce themselves beyond their name, and throughout th…
10 months ago
Difficult Neutral United States
My process started with a 30-minute recruiter screening call where they focused on whether I met the minimum qualifications. After that, I was schedul…
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
Technical Interview Structure
The interview process typically includes multiple technical rounds focused on data structures and algorithms (DSA), object-oriented programming (OOP), and core Java concepts, with an expectation for candidates to demonstrate proficiency across these areas. Interviews often progress from problem-solving to applying concepts in practical scenarios.
DSAOOPJava
Behavioral and Role Fit Interviews
Candidates can expect behavioral interviews that assess role fit and problem-solving abilities through situational questions, emphasizing real-world applications and teamwork. This aspect often includes discussions about past experiences and how candidates handle challenges.
BehavioralRole FitSituational
Assessment and Evaluation Process
The process generally starts with an online assessment to evaluate coding and communication skills, followed by structured interviews that may include both technical and HR components, sometimes blending technical assessments into HR discussions, which can create confusion about expectations.
Online AssessmentHR RoundEvaluation
Interview Atmosphere and Professionalism
The interview experience can vary significantly in terms of professionalism and engagement from interviewers, with some candidates reporting disinterest or distractions during technical rounds, which negatively impacts the overall impression of the process.
ProfessionalismEngagementAtmosphere
Communication and Clarification Challenges
Candidates often face challenges with communication clarity during technical interviews, particularly when interviewers are not responsive or when questions are poorly phrased, leading to misunderstandings that can affect performance.
CommunicationClarificationMisunderstanding
Feedback and Follow-Up Delays
Many candidates report delays in feedback and follow-up communication after interviews, which can lead to frustration and a sense of disrespect for their time and effort, highlighting a need for improved transparency in the hiring process.