After I got shortlisted, my first interaction felt very structured: an external vendor ran a 1.5-hour bar-raiser style round. It covered the usual spread of DSA plus low-level and high-level design, so I didn’t just solve coding-style problems—I had to think through design topics as well.
For DSA, I was asked problems like Climbing Stairs and Merge Two Sorted Arrays in Place. The LLD portion focused on a Library Management scenario where the interviewer handed over the requirements. I remember having to define entities and relationships clearly before turning that into a design. Overall it felt fast-paced and thorough, with a lot of topics kept within a single session.
2 months ago
The most distinctive part of my Kotak SDE-1 journey was Round 3, which ended up being a low-level design focused discussion. Even before the interview, the recruiter had framed it as LLD, but I was also bracing for the possibility of DSA showing up alongside it. When I sat down for Round 3, it mostly felt like I was being evaluated on how I break down requirements into a workable service design.
I was asked to implement a notifications service that could send email, WhatsApp, and messages. The interviewer gave requirements for templates, so I had to model separate templates like an email template, WhatsApp template, and message template. From there, I designed the flow around two APIs: one for template registration and another for invoking the template for sending.
2 months ago
My process started with a 90-minute, three-round interview that kicked off right away with DSA. I filled out a Google form shared by a recruiter on Li…
4 months ago
My interview for the Kotak SDE role ran for exactly 1.5 hours and was split cleanly into three parts: DSA, low-level design, and distributed systems. …
5 months ago
I had a 1.5-hour interview that was explicitly divided into three parts: problem solving, then low-level design, and then high-level design. The momen…
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 & Rounds
Interviews typically last around 1.5 hours and are divided into three main sections: DSA, low-level design (LLD), and sometimes high-level design (HLD). Candidates should be prepared for a fast-paced format that requires switching between different types of questions and thinking modes.
Interview structureThree roundsTime management
DSA Focus
The DSA portion often includes straightforward problems, such as array manipulations or tree-based questions, with an emphasis on clear reasoning and problem-solving strategies. Candidates should practice common algorithms and be ready to explain their thought processes.
Data StructuresAlgorithmsProblem-solving
Low-Level Design (LLD)
LLD discussions are a significant part of the interview, where candidates are evaluated on their ability to translate requirements into structured designs, including defining entities and API interactions. It's crucial to focus on clarity and the rationale behind design choices.
Low-Level DesignAPI designSystem architecture
Behavioral & Background Discussion
Interviews often begin with a conversation about the candidate's background and relevant experience, which sets the tone for the technical discussions that follow. Candidates should be prepared to articulate their past challenges and how they relate to the role.
Behavioral questionsExperience discussionBackground fit
Overall Difficulty & Expectations
Candidates report that the interview process is rigorous, with a clear focus on breadth of knowledge rather than just coding skills. It's important to maintain a balance between technical proficiency and design thinking throughout the interview.
Feedback is often immediate, and candidates may find that the outcome is decided quickly, especially in single-round interviews. It's essential to perform well in the initial round as there may not be opportunities for recovery or additional rounds.