SDE-2
Anonymous
1 day ago
The process opened with an OA covering DSA, behavioural questions and a system design component. After clearing it I moved into four loop rounds, a mix of in-person and virtual.
Fairly standard territory — graphs, DP, arrays and strings. The interviewer wanted more than a working solution: it had to be syntactically clean, and I had to handle follow-up constraints added as the conversation went on.
Requirement gathering, then API design and schema design. Doing well came down to solid OOP fundamentals and the right design patterns, backed by class and UML diagrams.
Define requirements up front, then estimate scale — expected users, queries per second, database size — and justify every design decision, including caching strategy and the overall logical flow.
Conducted by someone from a completely different team, evaluating performance holistically. A mix of HLD, LLD and DSA, and I was expected to produce fully functional, tested code rather than pseudocode.
These weren't confined to one round — one or two came up in every session, always tied back to real experiences from my background.
Selected.
Sign in to join the discussion.
Sign in to commentNo comments yet — be the first to respond.