I went through a fairly tight, three-round loop for an SE3 Software Engineer role. After a structured kickoff, the first deep technical round was low-level design, where I was pushed on implementation details and coding patterns. It felt challenging in a way that still came across as “fair,” and most of the pressure was on how I’d structure the solution rather than just talking in abstractions.
Next came high-level design, and that’s where the focus shifted to system design thinking—scalability and how the system would hold up as requirements grew. The last step was the hiring manager round, which leaned more into behavioral questions and cultural fit than pure technical depth. Overall, the process felt organized end to end, but I didn’t end up getting an offer.
> 1 year
Easy Positive Bengaluru
My interview experience centered on data work and SQL. I was asked about joins and window functions, and even the ordering logic of SQL—how SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY, and LIMIT interact. The questions also covered how to handle filtering and cleaning using pandas, which made the round feel more analytical than purely engineering-focused.
The process was on the easier side overall, and I was able to address the topics that came up. I didn’t end up getting an offer, but the content itself felt straightforward and aligned with practical data skills.
> 1 year
Average Positive India
I had an in-person three-round flow, and the questions felt easy to medium across the technical parts. The first round went well enough that I cleared…
> 1 year
Average Neutral India
My interview was in-person and ran across two technical rounds. The first was a machine coding round where I was asked to design a restaurant system. …
> 1 year
Average Positive India
I went through a compact three-round set. The first round was machine coding where I had to create a basic folder structure. The second round was more…
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 consists of three to five rounds, often including a mix of technical assessments and a hiring manager round, with a timeline ranging from a few days to several weeks. Candidates noted a fast-paced environment, especially when moving from one round to the next.
Interview roundsTimelineFast-paced
Technical Rounds Focus
Technical rounds often include low-level design (LLD) and high-level design (HLD) questions, with a strong emphasis on coding patterns, system design, and problem-solving skills. Candidates reported a mix of machine coding challenges and system design discussions, with varying levels of difficulty.
Low-level designHigh-level designCoding patterns
Data & SQL Assessment
Some candidates experienced rounds focused on data work, particularly SQL, where they were tested on joins, window functions, and data manipulation using tools like pandas. This round was described as more analytical than purely engineering-focused.
SQLData manipulationAnalytical skills
Behavioral & Cultural Fit
The hiring manager round often included behavioral questions aimed at assessing cultural fit and past experiences, with some candidates feeling that this round diverged from the technical focus of earlier stages. The emphasis was on understanding the candidate's alignment with company values.
Behavioral questionsCultural fitValues alignment
Difficulty & Candidate Experience
Candidates reported a range of experiences from average to difficult, with some feeling the process was organized and fair, while others described it as mentally draining or disorganized. The perception of difficulty often depended on the specific focus of each round.
Difficulty levelCandidate experienceMental strain
Communication & Feedback
Candidates noted varying levels of communication throughout the process, with some appreciating the prompt responses from HR, while others felt that the feedback and engagement from interviewers could have been more constructive. This affected their overall impression of the process.