My journey started with an LLD-style round that felt like the hardest part of the process because of the time pressure. I remember the problem statement taking longer than expected to fully reason through during the allocated window. I was able to answer the follow-up questions and explain my thinking around the approach, but I still couldn’t get the full coding portion to the finish line. Even though I felt interactive and responsive, I didn’t make it to the next stage.
The setup also had an assessment vibe before that deeper discussion—there was an OA with three problems split across different points, and I managed to clear it. After that, I went into the LLD interview that ran in a group discussion style. I answered questions during the session, but I wasn’t let through to the following round. What surprised me was how much the outcome seemed tied to completing the core code work under time constraints, not just being able to reason out parts of the solution.
5 months ago
Difficult Positive Bengaluru
After I got pulled into the process, I ended up going through two interview rounds. The first one was a machine coding task where I had to implement a reviews system for a food delivery app, covering restaurant, food, and delivery aspects. The work felt fairly grounded in building features rather than just talking theory, but it still required careful thinking about structure and edge cases.
The second round was more high-level design focused. I was asked to design a payment system, which shifted the emphasis to the bigger components and how they fit together. By the time I finished both rounds, the process felt thorough and challenging in a specific way—less about memorizing algorithms and more about demonstrating how I reason through real product systems. I didn’t get an offer, though the overall experience felt constructive and clear about what they were evaluating.
6 months ago
Difficult Neutral India
I attended the first round and it focused heavily on DSA-style problem solving. The questions were medium to difficult overall, and I managed to solve…
9 months ago
Difficult Neutral Bengaluru
Right from the start, the process felt unusually smooth and professionally run, with interviewers who kept things conversational instead of adversaria…
9 months ago
For an SDE3 interview, the process stretched out for more than two months, which honestly felt long but also deliberate. It took about a month and a h…
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 (OA)
The interview process begins with an online assessment featuring multiple coding questions of varying difficulty, often including both DSA and CS fundamentals. Candidates should prepare for a mix of problem types, as performance here is crucial for advancing to the next stages.
HackerRankDSACS fundamentals
Technical Coding Rounds
Candidates will face multiple technical rounds focused on coding, often requiring implementation of real-world systems under time constraints. Expect to demonstrate not just coding skills but also the ability to explain design choices and handle edge cases.
Machine codingImplementationTime pressure
Low-Level Design (LLD) Focus
A significant portion of the interview process emphasizes low-level design, where candidates must showcase their ability to design and implement systems effectively. This includes translating requirements into working code and understanding system interactions.
System designOOPDesign thinking
Interview Structure and Flow
The interview process is structured with clear stages, typically starting from the OA to technical rounds and concluding with HR discussions. Candidates should expect a competitive environment with escalating difficulty across rounds.
Structured processCompetitiveClear stages
Communication and Explanation
Throughout the interviews, candidates are expected to articulate their thought process and design choices clearly. Effective communication is critical, especially during coding and design discussions, as evaluators look for clarity alongside technical proficiency.
CommunicationClarityThought process
Overall Difficulty and Pressure
Candidates report a high level of difficulty and pressure throughout the interview process, with tight time constraints and high expectations for performance. It's important to practice under similar conditions to build confidence and manage stress.