After a recruiter online call, I got pulled into a technical loop that felt fairly structured. It started with an online tech round, and then I went through three more interviews in sequence. Each round had a distinct purpose, so I always knew what kind of thinking the panel was testing.
The coding rounds covered the usual mix: one was DSA, one was LLD, and one was HLD. The LLD question leaned toward “machine coding” style work, specifically flattening a recursive JSON structure. The HLD prompt was about building reliable infrastructure for uploading files, and honestly it didn’t feel as hard as the label might imply.
7 months ago
Average Negative India
My process started with HR, where the tone was more “fit and context” than anything deeply technical. In that first conversation, I walked through my background and the recruiter discussed the open role and whether my experience matched what they were looking for. The recruiter also covered practical logistics around the position and my situation.
After that, I had a technical round that focused on technical discussion rather than a long take-home. The interview itself went well enough that I expected to move forward, but then everything stalled—HR stopped replying after the technical conversation. I kept following up, and the response never really came with a clear verdict or feedback.
> 1 year
Easy Neutral Bengaluru
My interview path was pretty light-touch and followed a clear sequence: a HackerRank-style assignment, two technical interviews, and then an HR interv…
> 1 year
Average Negative Bengaluru
I was referred for a full-stack role, and the recruiter initially framed it as mostly backend with a smaller frontend component. The timeline already …
> 1 year
Average Positive Bengaluru
My interviews leaned heavily into databases and fundamentals. Early on, I had questions about MySQL and there was a lot of discussion of my projects a…
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 a recruiter call, followed by a series of technical interviews that may include coding assessments and project presentations. Candidates noted a mix of structured and unstructured experiences, with some reporting delays and poor communication from HR affecting the overall flow.
Technical interviews often cover data structures and algorithms (DSA), low-level design (LLD), and high-level design (HLD), with some candidates experiencing hands-on coding tests or SQL-related questions. The difficulty is generally perceived as average, with an emphasis on real-world applications and problem-solving skills.
DSALLDSQL
Behavioral & Communication Assessment
Candidates reported that behavioral questions were common, focusing on working style, project discussions, and communication skills, especially during project presentations. The ability to articulate thoughts clearly and engage in discussions was emphasized as a key component of the evaluation.
Several candidates expressed frustration with inconsistent communication from recruiters, including delays in feedback and lack of follow-up after interviews. This often led to feelings of uncertainty and dissatisfaction with the overall process, overshadowing the quality of technical interviews.
Onsite interviews typically involve multiple rounds with various team members, including technical assessments and discussions about past projects. Candidates noted that the onsite format can be intense, but many appreciated the collaborative atmosphere and the opportunity to interact with different team members.
Many candidates did not receive offers, often reflecting on the experience as fair but lacking closure due to poor communication. Some expressed a desire for clearer feedback and a more respectful process, while others noted that the overall experience could be impacted by the recruiting team's professionalism.