The interview process was well structured and fairly straightforward. It started with an initial recruiter screening to discuss my background, motivation, and expectations for the role. After that, I had a technical interview focused on coding, system design, and past project experience. The interviewers were professional and gave clear instructions. Overall, the process felt organized and respectful, with a good balance between technical depth and behavioral discussion.

Round I: Virtual DSA i) Job scheduling: each job takes X time and must be done before Y ii) Rotated array, find min element Round II + III: In office interview drive - Poorly managed interviews - ⁠They even had people stay from 11 to 7 - ⁠Initially told us that we will only have one round here and the next one will happen virtually. But took the next round on the same day as well ( I left at 7 ) - ⁠They had exact number of participants and knew how long each interview takes, not sure why it wasn’t managed better by a bunch of engineers - ⁠Round II: LLD Design MyGate entities and relations. Great interviewer, was clear with the expectations. Asked important questions on notification logic. - ⁠Round III: This was meant to be a HLD round but interviewer asked me LLD instead, said we had less time. - ⁠He wasn’t clear with the expectations, showed a UI didn’t tell which part he exactly wants to focus on. - ⁠It was WeWork’s booking system for different activities - ⁠While solving focused on some booking mechanics, asked relevant question on locking which I wasn’t aware of. - ⁠Gave negative response on my solution approach - ⁠During follow up questions told me a similar approach of solving ( one I was building towards ) - ⁠I think the interviewer was also very tired and didn’t understand what I was building

The interview process was intense but moved really fast. Everything was scheduled tightly, so there wasn’t much downtime between stages. It started with a quick recruiter screen, then jumped straight into technical rounds. The DSA interviews were very LeetCode-style: you had to clarify requirements fast, pick the right approach under pressure, and code cleanly while explaining tradeoffs. They pushed hard on complexity, edge cases, and optimizations, so it felt like you were constantly being tested for both speed and correctness. The system design round was equally demanding. You had to scope the problem quickly, define APIs/data models, and reason through scaling, reliability, caching, and bottlenecks. They asked “what breaks first?” questions and expected crisp justifications, not hand-wavy answers. Overall, it was a high-pressure sprint: lots of depth, minimal fluff, and rapid turnaround