My journey started with a Hackerrank-style test, and it was described to me as an easy-to-medium mix. After finishing that, I had a call with a team member where I walked through my experience and got some behavioral-style questions.
The call itself felt a bit awkward—both because of how the interviewer handled the conversation and because it didn’t feel as natural as I expected. Even so, I think I was able to explain parts of my background, but the momentum didn’t carry me very far.
> 1 year
Average Positive United States
After a recruiter screening, I went into an online technical stage and then a personality-focused round. The overall vibe felt fairly straightforward, and I didn’t get the sense the bar was extreme; I was still surprised by how much they leaned on core fundamentals rather than trying to hard-push deep, tricky DSA.
During the technical portion, I ended up doing questions that mixed DSA with more object-oriented and database concepts. One interviewer started by having me introduce myself, then moved through a sequence of questions for close to an hour. I remember feeling a little cold at the start, but the interviewer stayed calm and made it feel easier to breathe and think. I was able to answer most of what came up.
> 1 year
Average Negative United States
I went through a pretty long stretch of interviews that felt unusually heavy on volume and timing. I first had HR conversations, then after that I hit…
> 1 year
Difficult Neutral Pune
My process started with technical questioning that really focused on fundamentals and details in the typical stack areas—OOPs, DSA, DBMS, and operatin…
> 1 year
Average Positive Bengaluru
I went through an online assessment first, and it was structured with multiple-choice questions on OOPs and SQL plus a coding section. The whole test …
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
Online Assessment
Candidates typically start with an online assessment that includes multiple-choice questions on OOPs and SQL, followed by a coding section. The assessments are described as straightforward, but timing can be tight, especially for the multiple-choice portion.
OOPsSQLCoding challenge
Technical Interviews
The technical interviews focus heavily on core fundamentals, including data structures and algorithms (DSA), object-oriented programming, and database concepts. Candidates report a mix of technical discussions, often lasting around 1.5 hours, with some variation in depth and focus depending on the interviewer.
DSAOOPTechnical depth
Behavioral & HR Rounds
After technical evaluations, candidates typically engage in behavioral and HR rounds that assess cultural fit and personal background. These discussions can feel straightforward but may lack clarity regarding the next steps in the process.
BehavioralCultural fitHR
Communication & Follow-up
Many candidates express frustration with the communication and follow-up process, noting delays and a lack of clarity after interviews. This can lead to feelings of being 'ghosted' or uncertainty about their status in the hiring process.
CommunicationFollow-upGhosting
Interview Experience & Atmosphere
Candidates report mixed experiences regarding the interview atmosphere, with some finding it friendly and relaxed while others describe it as disjointed or even unprofessional. The overall vibe can significantly impact candidates' comfort and performance during interviews.
Interview atmosphereComfortProfessionalism
Mismatch in Evaluation Criteria
Some candidates feel there is a mismatch between their online assessment performance and the topics covered in subsequent interviews, leading to confusion and stress. This includes unexpected shifts in focus, such as an emphasis on functional programming over DSA.