Kotak Mahindra Bank SDE 2 Backend Interview Experience (3 Rounds)

kotak mahindra bank logo
kotak mahindra bank
· SDE 2 Backend· 3y exp
February 23, 2026 · 1 reads

Summary

I interviewed for the SDE 2 Backend role at Kotak Mahindra Bank, undergoing three challenging rounds covering DSA, LLD, and Distributed Systems. Despite being rejected, the experience was valuable in identifying my areas for improvement.

Full Experience

Experience Level: ~3 years
Role: SDE 2 – Backend
Mode: Referral
Result: ❌ Rejected

Initial HR Call

Discussion points:

  • Overall experience
  • Current tech stack
  • Backend exposure
  • Current & expected compensation
  • Notice period

HR was clear and supportive throughout the process.


Round 1 – Bar Raiser (90 mins)

This was a mixed round (DSA + LLD + Distributed Systems).

  • DSA: Problem based on Kadane’s Algorithm
  • LLD: Design an E-commerce platform (classes, DB choice, flows)
  • Distributed Systems: Event-driven processing, DB selection, scalability

Focus was on clarity, reasoning, and trade-offs.


Round 2 – DSA

  • Number of Islands
  • One LeetCode Hard problem

Clean code + complexity discussion expected.


Round 3 – LLD + Experience

Problem: Design an Airport Scheduler (single runway).
Covered priority queue design, priority handling, race conditions, starvation, and concurrency.

This round was rescheduled 3 times.
Interviewer seemed to expect a very specific approach.

Final Thoughts

Honestly, I was expecting a positive result after the final round, so the rejection was disappointing. I had invested a lot of preparation and effort into the process.

That said, the interviews were challenging and helped me identify gaps in my LLD and concurrency concepts. The HR team was supportive and professional throughout, which I genuinely appreciated.

Interview Questions (5)

1.

Kadane's Algorithm Problem

Data Structures & Algorithms·Medium

A problem based on Kadane's Algorithm.

2.

Design an E-commerce Platform

System Design

Design an E-commerce platform, covering aspects like class design, database choice, and system flows.

3.

Distributed Systems Discussion

System Design

Discussion on event-driven processing, database selection for distributed systems, and scalability.

4.

Number of Islands

Data Structures & Algorithms·Medium

The classic LeetCode problem 'Number of Islands'.

5.

Design an Airport Scheduler

System Design·Hard

Design an Airport Scheduler for a single runway, covering aspects like priority queue design, priority handling, race conditions, starvation, and concurrency.

Discussion (0)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

No comments yet

Be the first to share your thoughts and start the discussion!