Kotak Mahindra Bank | SDE 2 | Hyderabad
Summary
I interviewed for an SDE 2 role at Kotak Mahindra Bank in Hyderabad, undergoing multiple rounds covering dynamic programming and various system design challenges. Despite performing well in some rounds, I ultimately received a rejection.
Full Experience
A recruiter reached out to me for an SDE 2 role at Kotak Mahindra Bank in Hyderabad. Here's how my interview experience went:
Bar Raiser Rounds:
- I encountered the Coin Change Problem, a classic dynamic programming question.
- I was also tasked with the Low-Level Design (LLD) of an E-commerce system.
The interviews were conducted in a random order.
LLD Discussion Round:
Interestingly, despite HR informing me that this round was supposed to be purely coding, I was asked to design a system for an Online Survey.
Coding Round:
I was given an arrays-related question, which I managed to solve with an optimized solution within 20 minutes. However, the interviewer abruptly shifted the discussion and asked me to design a system similar to Google Drive. The specific scenario involved uploading a massive 100 GB file over an unstable network with a mere 10 Mbps speed. I admit I fumbled a bit here, as I didn't have much experience with breaking files into chunks and handling such resilient uploads. I conveyed my unfamiliarity with this specific area, but the interviewer continued to press for more details, which definitely added to the pressure.
The initial two rounds felt promising, but the third round, especially the system design part, didn't go as expected. HR had mentioned the possibility of another round, but I've since received no further communication from them.
4th Round:
I had a discussion on the High-Level Design (HLD) of CricBuzz, which went very well.
Verdict:
I received a rejection. To be honest, I still don't fully understand why, especially after some rounds seemed to go quite well.
Interview Questions (5)
Given a set of coin denominations and a target amount, find the minimum number of coins needed to make up that amount.
I was tasked with designing the low-level architecture for an e-commerce system.
I was asked to design a system for an online survey.
I was asked to design a system similar to Google Drive, specifically focusing on the challenge of uploading a 100 GB file over an unstable 10 Mbps network.
I was asked to design the High-Level Design (HLD) for a system similar to CricBuzz.
Preparation Tips
My key takeaway from this experience is not to rush to an optimized solution too quickly during coding rounds. It's often better to start with a brute-force approach and walk through the problem gradually, even if it seems inefficient at first. This strategy helps to utilize the allocated time effectively and prevents the interviewer from shifting focus to unexpected or irrelevant questions that might fall outside your direct expertise.