kotak mahindra bank logo
Kotak Mahindra Bank· SDE II Backend Engineer

Kotak | SDE 2 | Backend Engineer | India | Aug 2026 | Reject

Location
India
Experience
3.25 years
Posted
17 Sept 2026
236 reads

Summary

I interviewed for an SDE II Backend Engineer role at Kotak in India. I cleared the first two rounds but was rejected after the final HLD/LLD interview.

How it went

Kotak SDE II Backend Interview Experience

Experience: 3 years 3 months

Current Role: Software Engineer at a FAANG company in India

Education: B.Tech, CS, Tier 1, India

Current Compensation: ₹33 LPA

I recently interviewed for an SDE II Backend Engineering role at Kotak, India.

Application

Recruiter called me on phone directly for this job opening. I think he got my number from InstaHyre or LinkedIn. I don't remember exactly how, but I never applied to Kotak on Career Portal.

Round 1 - DSA + LLD + HLD

Duration: 90 minutes

This was an elimination round. It was taken by a 3rd party company called Bar Raiser.

DSA (30 mins):

LLD (45 mins):

  • LLD of Food Delivery App (Eg; Zomato)
    • Expectations: Discuss requirements, find entities, draw class diagram and explain design pattern.
    • Machine coding was not expected.
    • There were multiple questions on which design pattern fits where, explain whole of SOLID, explain OOPS, etc.

HLD (15 mins):

  • 5 questions directly of HLD. No full-fledged HLD.
    • How does a distributed system behave during a network partition? What factors do you consider, and what are the key trade-offs?
    • What is a lock? What different types of locks are there? When would you use a lock, and when would you avoid it?
    • When would you favor consistency over availability, and when would you favor availability over consistency?
    • What is the difference between strong consistency and eventual consistency? What are the trade-offs?
    • What is idempotency? How do you define an idempotency key, and how would you use it for a transaction such as placing an order in a food-delivery application?

Result: Hire

After this round, I was moved to the 2nd stage round


Round 2 - Behavioral + DSA

Duration: 60 minutes

This was an elimination round, taken by SDE 2 with 4+ YOE.

Behavioral - 10 mins

  • Introduce yourself
  • Describe an ambiguous situation you faced - Eg; Tell me about a time when you delivered a project with ambiguous problem statement. How did you approach it?

DSA - 45 mins

Result: Hire

In this round, I felt that if you have previously solved these problems, only then you can pass this. Because otherwise doing 1 Medium and 1 Hard with the most optimal 1D solution and monotonic stack is impossible to do within 45 minutes.

After this round, I was moved to the final interview round.


Round 3 - HLD + LLD

Duration: 60 minutes

This was an elimination round and the final round with the Hiring Manager. The recruiter had mentioned that this would be a pure LLD round.

The question was: "Design a vehicle booking and loan processing application" - essentially, an application used by the sales team at a Hyundai showroom to book a car and initiate the loan process.

I started with requirements gathering and defining the entities. After ~10 minutes, the interviewer asked me to switch to an HLD and complete a high-level diagram in 5 minutes.

We then discussed potential failures, bottlenecks, and scalability. The expectation seemed to be to include components such as MQs, caches, load balancers, etc., even where their necessity wasn't immediately obvious given the limited time.

After that, we returned to the LLD. I finalized the entities and created the class diagram. We also discussed design patterns such as Strategy, Singleton, Factory, and Decorator, including where they could potentially fit into the design.

Result: No Hire


Final Outcome

Rejected


PS

  • Notice Period of Kotak: 3 Months (Non-Negotiable)
  • SDE 2 Pay of Kotak: Ranges from 30L to 60L; they decide it based on your past CTC
  • Number of interviews depends on your previous company. If you are from FAANG, expect 3. If from Service based, expect 5.

Questions asked (11)

  1. 01

    Valid Parentheses

    Data Structures & Algorithms · Easy

    Determine if a string containing only the characters '(', ')', '{', '}', '[' and ']' is valid. A string is valid if open brackets are closed by the same type of brackets in the correct order.

    Open the problem
  2. 02

    Valid Palindrome

    Data Structures & Algorithms · Easy

    Given a string, determine if it reads the same forward and backward after removing non-alphanumeric characters and ignoring case.

    Open the problem
  3. 03

    Coin Change

    Data Structures & Algorithms · Medium

    You are given an integer array of coin denominations and an amount. Compute the fewest number of coins needed to make up that amount. If it is not possible, return -1.

    Open the problem
  4. 04

    Largest Rectangle in Histogram

    Data Structures & Algorithms · Hard

    Given an array of non-negative integers representing the heights of bars in a histogram, find the area of the largest rectangle that can be formed within the bounds of the histogram.

    Open the problem
  5. 05

    Food Delivery App LLD

    System Design

    Discuss requirements, identify entities, draw a class diagram, and explain appropriate design patterns for a food delivery application similar to Zomato. Topics include SOLID principles and object‑oriented concepts.

  6. 06

    Network Partition Behavior

    System Design

    Explain how a distributed system behaves during a network partition, factors to consider, and key trade‑offs involved.

  7. 07

    Locks and Their Types

    System Design

    Define what a lock is, describe different types of locks, and discuss when to use or avoid them.

  8. 08

    Consistency vs Availability Trade‑off

    System Design

    When would you favor consistency over availability, and when would you favor availability over consistency in a distributed system?

  9. 09

    Strong vs Eventual Consistency

    System Design

    Describe the difference between strong consistency and eventual consistency and discuss the trade‑offs of each approach.

  10. 10

    Idempotency in Transactions

    System Design

    Explain what idempotency is, how to define an idempotency key, and how it can be used for a transaction such as placing an order in a food‑delivery application.

  11. 11

    Vehicle Booking and Loan Processing Design

    System Design

    Design a vehicle booking and loan processing application for a Hyundai showroom. Include requirements gathering, entity identification, high‑level architecture (including components like MQs, caches, load balancers), and detailed class diagram with appropriate design patterns such as Strategy, Singleton, Factory, and Decorator.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Kotak Mahindra Bank recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

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