Kotak Mahindra Bank SDE-1 Interview Experience : DSA, LLD, Kafka, PostgreSQL & Distributed Systems

Ashutosh Verma

Last Updated : 26 May 2026

777 Views

#dsa

#interview-experience

#interview-preparation

#technical-interview

#coding-interview

Adℹ

Recently, I interviewed for an SDE-1 role at Kotak Mahindra Bank and the experience was honestly much more technical and backend-focused than I initially expected. I went into the interview thinking it would mostly revolve around basic Java and DSA questions, but the process covered a surprisingly wide range of topics including distributed systems, Kafka, database concepts, low-level design and coding problems.

The complete process consisted of 3 rounds and was conducted remotely. The overall difficulty level was medium, but what made the interview interesting was the balance between coding ability and engineering fundamentals. The interviewers were not just checking whether I could solve LeetCode problems. They were trying to evaluate whether I understood how real backend systems work and whether I could think like an engineer while discussing scalability, system behavior and production-level concepts.

If you are preparing for:

Kotak Mahindra Bank SDE-1 interview
backend developer interviews
Kafka interview questions
distributed systems interview preparation
Java backend interviews for freshers or SDE-1

then this experience can genuinely help you understand what kind of preparation is actually useful.

One important observation from this interview was: Banking companies are increasingly asking product-company style backend questions. Especially around: distributed systems, data consistency, scalability, Kafka, SQL databases, system design fundamentals.

which means backend preparation has become extremely important even outside big product companies.

Interview Process Overview

The process had 3 rounds:

Round	Focus
Round 1	Distributed Systems + DSA + LLD
Round 2	Pure DSA Round
Round 3	Resume Discussion + Kafka + PostgreSQL + DSA

The interview process was smooth overall and every round explored different aspects of backend engineering and problem-solving.

Round 1 : Distributed Systems, DSA & Low-Level Design

This was the longest round, around 1.5 hours. It was conducted through BarRaiser. The round was divided into three sections: Distributed Systems, DSA and LLD.

What I liked was that the interviewer did not immediately jump into coding. The discussion started gradually with backend concepts and system-level thinking.

Distributed Systems Questions

The first section focused entirely on distributed systems concepts.

Initially, I expected surface-level questions, but the interviewer actually explored practical reasoning behind scalability and consistency.

One of the first questions was:How do you maintain consistency in distributed database systems?

I explained concepts like: replication strategies, distributed transactions, quorum-based approaches, eventual consistency vs strong consistency.

I also mentioned that maintaining strong consistency across distributed systems can impact availability and latency, so many large-scale systems use eventual consistency depending on business requirements.

The interviewer then asked: How do you scale a system?

Instead of giving a generic answer, I explained scaling from both perspectives:

Vertical Scaling Increasing server resources like CPU and RAM.

Horizontal Scaling Adding multiple servers and distributing traffic among them.

I also discussed: load balancing, database sharding, caching, stateless services.

The interviewer seemed particularly interested in how scaling decisions change when traffic suddenly increases.

Another interesting question was: How do you handle deployment failures in production?

This felt more like a real engineering discussion rather than an interview question. I explained approaches such as: rollback strategies, blue-green deployment, canary deployment, monitoring and alerting, feature flags.

I also discussed why automated deployment pipelines are important to reduce human error.

This part of the interview gave me the feeling that they were trying to evaluate practical backend maturity instead of textbook knowledge.

DSA Problem :Container With Most Water

After the system discussions, we moved into coding. The DSA question asked in this round was: Container With Most Water

This is a classic two-pointer problem where we need to find the maximum area of water that can be trapped between two vertical lines.

At first glance, brute force looks straightforward because we can try every pair of lines. But that approach leads to O(N²) time complexity, which is inefficient for large inputs.

I explained my thought process before writing code because interviewers often care a lot about approach clarity. The key observation is : The area depends on distance between lines and minimum height between the two lines. So moving the taller line is usually useless because the smaller line limits the area. That naturally leads to the optimal two-pointer solution.


public class ContainerWithMostWater {

    public int maxArea(int[] height) {
        int left = 0;
        int right = height.length - 1;
        int maxArea = 0;
        while (left < right) {
            int area = Math.min(height[left], height[right])
                    * (right - left);
            maxArea = Math.max(maxArea, area);
            if (height[left] < height[right]) {
                left++;
            } else {
                right--;
            }
        }

        return maxArea;
    }
}

The interviewer asked several follow-up questions around:

why the optimization works
edge cases
time complexity
space complexity

So make sure you can explain the reasoning, not just memorize the solution.

Low-Level Design Round – Design Uber/Ola

The final section of Round 1 was LLD. The interviewer asked me to design a simplified version of Uber/Ola.

Initially, I thought they would only ask for class diagrams, but the discussion became much broader. The interviewer expected:

class design
APIs
database schema
entity relationships
booking workflow
ride allocation logic

I started by identifying the main entities:

User
Driver
Ride
Vehicle
Payment

Then I discussed: ride booking APIs, location tracking, driver assignment and fare calculation.

One thing I learned from this round is: In LLD interviews, communication matters more than perfect UML diagrams The interviewer mainly wanted to understand how I structure backend systems logically.

Round 2 : DSA Round

This round was around 1 hour and focused completely on coding problems. Both questions were medium-level problems and fully working solutions were expected. The interviewer was very particular about: clean code, optimization, handling edge cases, explaining thought process,

Problem 1 – Group Anagrams

The problem statement was straightforward: Given an array of strings, group all strings that are anagrams of each other.

Example:


Input:
["eat","tea","tan","ate","nat","bat"]

Output:
[["eat","tea","ate"],["tan","nat"],["bat"]]

The key observation is that anagrams have the same sorted character sequence. So for every string: sort its characters and use sorted string as hashmap key


class Solution {

    public List<List<String>> groupAnagrams(String[] strs) {
        Map<String, List<String>> map = new HashMap<>();
        for (String str : strs) {
            char[] chars = str.toCharArray();
            Arrays.sort(chars);
            String key = new String(chars);
            map.putIfAbsent(key, new ArrayList<>());
            map.get(key).add(str);
        }
        return new ArrayList<>(map.values());
    }
}

The interviewer also asked:

why hashmap works efficiently here
time complexity analysis
alternate approaches without sorting

Problem 2 – Permutations

The second problem was: Generate All Permutations of an Array This problem tests recursion and backtracking fundamentals. The interviewer wanted a complete running solution.

I explained how recursion explores every possible arrangement by: choosing one element, marking it visited and recursively building remaining permutations.


class Solution {

    public List<List<Integer>> permute(int[] nums) {

        List<List<Integer>> result = new ArrayList<>();

        backtrack(nums, new ArrayList<>(), new boolean[nums.length], result);

        return result;
    }

    private void backtrack(int[] nums,
                           List<Integer> current,
                           boolean[] visited,
                           List<List<Integer>> result) {

        if (current.size() == nums.length) {
            result.add(new ArrayList<>(current));
            return;
        }

        for (int i = 0; i < nums.length; i++) {

            if (visited[i]) continue;

            visited[i] = true;
            current.add(nums[i]);

            backtrack(nums, current, visited, result);

            current.remove(current.size() - 1);
            visited[i] = false;
        }
    }
}

The interviewer paid close attention to: recursion flow, backtracking cleanup and space complexity.

Round 3 : Resume Discussion + Kafka + PostgreSQL + DSA

This round was probably the most discussion-heavy round. The interviewer explored: Kafka, PostgreSQL, transactions, ACID properties and DSA basics. This round felt more like a backend engineering conversation than a coding interview.

Kafka Questions

The interviewer asked several practical Kafka questions.

Difference Between Topic and Partition

I explained:

Topic : Logical category of messages.
Partition : Physical division of a topic used for scalability and parallel processing.

I also explained how partitions enable Kafka to distribute load across brokers.

Consumer vs Consumer Group

I explained that:

consumers read messages
consumer groups allow parallel consumption

Within a consumer group: one partition is consumed by only one consumer This ensures message processing balance.

Scenario Question – 2 Partitions and 3 Consumers

The interviewer asked: If there are 2 partitions and 3 consumers, how are they distributed?

I explained that: only 2 consumers will actively consume and the third consumer remains idle. because one partition cannot be shared among multiple consumers within the same group simultaneously.

Another important question was: How do you maintain message order in Kafka?

I explained that ordering is guaranteed only within a partition. So messages with the same key should be routed to the same partition. This ensures proper sequential processing.

PostgreSQL Questions

The interviewer then shifted toward SQL concepts. One question was: Difference Between Primary Key and Unique Constraint

I explained:

Primary Key

uniquely identifies records
cannot contain NULL
only one per table

Unique Constraint

also prevents duplicates
allows NULL values (depending on DB)
multiple unique constraints possible

Next, The interviewer asked: Explain ACID properties

Instead of rushing definitions, I explained each property with practical examples.

Atomicity Either entire transaction succeeds or fails completely.
Consistency Database remains in valid state after transaction.
Isolation Concurrent transactions should not interfere incorrectly.
Durability Committed changes must survive failures.

The interviewer also asked: What is a transaction? and What are isolation levels?

I discussed: Read Uncommitted, Read Committed, Repeatable Read and Serializable. along with concurrency issues like: dirty reads, phantom reads, and non-repeatable reads.

DSA Questions

Two smaller coding questions were asked toward the end.

1. Reverse a String Without Extra Space

The interviewer expected an in-place solution using two pointers.


class Solution {

    public void reverseString(char[] s) {
        int left = 0;
        int right = s.length - 1;
        while (left < right) {
            char temp = s[left];
            s[left] = s[right];
            s[right] = temp;
            left++;
            right--;
        }
    }
}

2. Find Kth Smallest Element in Array

I discussed multiple approaches: sorting, min/max heap and quickselect.

The interviewer seemed more interested in optimization trade-offs than final syntax.

Final Result & Overall Experience

Overall, the interview experience at Kotak Mahindra Bank was quite good and much more technical than I expected from a banking company. The process tested:

coding ability
backend fundamentals
distributed systems understanding
communication skills
system design thinking

One important takeaway from this interview was: Backend engineering interviews are becoming increasingly practical . Companies now expect engineers to understand not only algorithms, but also:

scalability
distributed systems
messaging systems
databases
deployment strategies
backend architecture decisions

Preparation Tips for Kotak SDE-1 Interviews

If you’re preparing for similar backend-focused interviews, I would strongly recommend focusing on:

medium-level DSA problems
Kafka fundamentals
SQL and PostgreSQL concepts
ACID properties
distributed systems basics
microservices concepts
LLD fundamentals
recursion and backtracking

Most importantly: Practice explaining your thought process clearly Because many interviewers evaluate communication and reasoning as much as coding ability itself.

Recommended Interview Experience

JioHotstar Staff Software Engineer Interview Experience

Disney+ Hotstar SDE-2 Interview Experience | Coding + System Design + Techno Managerial

Uber Senior Software Engineer Interview Experience | Real Interview Questions, System Design & Preparation Guide

Meta Business Engineer (L4 → L5 Consideration) Interview Experience

Rupeek Android Developer Interview Experience | Real Questions Asked, Preparation Tips & Complete Process

Rupeek SDE-3 Interview Experience (3 Rounds ~ Coding, LLD & HLD)

WheelsEye Backend Engineer Interview Experience | DSA Questions, System Design, Backend Deep Dive

Wise Software Engineer Interview Experience | DSA, System Design, Product Thinking

Yext SDE 1 Interview Experience – Complete DSA Questions, Debugging Round, API Challenge & HR Round

Uber SDE 2 Interview Experience (5 Rounds, Selected)

Adobe Software Engineer 2 Interview Experience

Volvo Cars Full Stack Developer Interview Experience (Selected)

Wayfair SDE Interview Experience

Wells Fargo SDE I Interview Experience

Flipkart Machine Coding Round Experience ~ Log Engine Implementation

My Vegapay Backend Engineer (SDE 2) Interview Experience (Rejected)

Interview Process Overview

The process had 3 rounds:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Round	Focus
Round 1	Distributed Systems + DSA + LLD
Round 2	Pure DSA Round
Round 3	Resume Discussion + Kafka + PostgreSQL + DSA

The interview process was smooth overall and every round explored different aspects of backend engineering and problem-solving.

Round 1 : Distributed Systems, DSA & Low-Level Design

This was the longest round, around 1.5 hours. It was conducted through BarRaiser.\nThe round was divided into three sections:\nDistributed Systems,\nDSA and\nLLD.

What I liked was that the interviewer did not immediately jump into coding. The discussion started gradually with backend concepts and system-level\nthinking.

Distributed Systems Questions

The first section focused entirely on distributed systems concepts.

Initially, I expected surface-level questions, but the interviewer actually explored practical reasoning behind scalability and consistency.

One of the first questions was:How do you maintain consistency in distributed database systems?

I explained concepts like:\nreplication strategies,\ndistributed transactions,\nquorum-based approaches,\neventual consistency vs strong consistency.

I also mentioned that maintaining strong consistency across distributed systems can impact availability and latency, so many large-scale systems use\neventual consistency depending on business requirements.

The interviewer then asked: How do you scale a system?

Instead of giving a generic answer, I explained scaling from both perspectives:

Vertical Scaling Increasing server resources like CPU and RAM.

Horizontal Scaling Adding multiple servers and distributing traffic among them.

I also discussed:\nload balancing,\ndatabase sharding,\ncaching,\nstateless services.

The interviewer seemed particularly interested in how scaling decisions change when traffic suddenly increases.

Another interesting question was: How do you handle deployment failures in production?

This felt more like a real engineering discussion rather than an interview question.\nI explained approaches such as:\nrollback strategies,\nblue-green deployment,\ncanary deployment,\nmonitoring and alerting,\nfeature flags.

I also discussed why automated deployment pipelines are important to reduce human error.

This part of the interview gave me the feeling that they were trying to evaluate practical backend maturity instead of textbook knowledge.

DSA Problem :Container With Most Water

After the system discussions, we moved into coding.\nThe DSA question asked in this round was: Container With Most Water

This is a classic two-pointer problem where we need to find the maximum area of water that can be trapped between two vertical lines.

At first glance, brute force looks straightforward because we can try every pair of lines. But that approach leads to O(N²) time complexity,\nwhich is inefficient for large inputs.

I explained my thought process before writing code because interviewers often care a lot about approach clarity.\nThe key observation is : The area depends on distance between lines and minimum height between the two lines.\nSo moving the taller line is usually useless because the smaller line limits the area.\nThat naturally leads to the optimal two-pointer solution.

\npublic class ContainerWithMostWater {\n\n    public int maxArea(int[] height) {\n        int left = 0;\n        int right = height.length - 1;\n        int maxArea = 0;\n        while (left < right) {\n            int area = Math.min(height[left], height[right])\n                    * (right - left);\n            maxArea = Math.max(maxArea, area);\n            if (height[left] < height[right]) {\n                left++;\n            } else {\n                right--;\n            }\n        }\n\n        return maxArea;\n    }\n}\n

The interviewer asked several follow-up questions around:

why the optimization works
edge cases
time complexity
space complexity

So make sure you can explain the reasoning, not just memorize the solution.

Low-Level Design Round – Design Uber/Ola

The final section of Round 1 was LLD.\nThe interviewer asked me to design a simplified version of Uber/Ola.

Initially, I thought they would only ask for class diagrams, but the discussion became much broader.\nThe interviewer expected:

class design
APIs
database schema
entity relationships
booking workflow
ride allocation logic

I started by identifying the main entities:

User
Driver
Ride
Vehicle
Payment

Then I discussed:\nride booking APIs,\nlocation tracking,\ndriver assignment and\nfare calculation.

One thing I learned from this round is:\nIn LLD interviews, communication matters more than perfect UML diagrams\nThe interviewer mainly wanted to understand how I structure backend systems logically.

Round 2 : DSA Round

This round was around 1 hour and focused completely on coding problems.\nBoth questions were medium-level problems and fully working solutions were expected.\nThe interviewer was very particular about:\nclean code,\noptimization,\nhandling edge cases,\nexplaining thought process,

Problem 1 – Group Anagrams

The problem statement was straightforward:\nGiven an array of strings, group all strings that are anagrams of each other.

Example:

\nInput:\n[\"eat\",\"tea\",\"tan\",\"ate\",\"nat\",\"bat\"]\n\nOutput:\n[[\"eat\",\"tea\",\"ate\"],[\"tan\",\"nat\"],[\"bat\"]]\n

The key observation is that anagrams have the same sorted character sequence.\nSo for every string:\nsort its characters and\nuse sorted string as hashmap key

\nclass Solution {\n\n    public List<List<String>> groupAnagrams(String[] strs) {\n        Map<String, List<String>> map = new HashMap<>();\n        for (String str : strs) {\n            char[] chars = str.toCharArray();\n            Arrays.sort(chars);\n            String key = new String(chars);\n            map.putIfAbsent(key, new ArrayList<>());\n            map.get(key).add(str);\n        }\n        return new ArrayList<>(map.values());\n    }\n}\n

The interviewer also asked:

why hashmap works efficiently here
time complexity analysis
alternate approaches without sorting

Problem 2 – Permutations

The second problem was: Generate All Permutations of an Array\nThis problem tests recursion and backtracking fundamentals.\nThe interviewer wanted a complete running solution.

I explained how recursion explores every possible arrangement by:\nchoosing one element,\nmarking it visited and\nrecursively building remaining permutations.

\nclass Solution {\n\n    public List<List<Integer>> permute(int[] nums) {\n\n        List<List<Integer>> result = new ArrayList<>();\n\n        backtrack(nums, new ArrayList<>(), new boolean[nums.length], result);\n\n        return result;\n    }\n\n    private void backtrack(int[] nums,\n                           List<Integer> current,\n                           boolean[] visited,\n                           List<List<Integer>> result) {\n\n        if (current.size() == nums.length) {\n            result.add(new ArrayList<>(current));\n            return;\n        }\n\n        for (int i = 0; i < nums.length; i++) {\n\n            if (visited[i]) continue;\n\n            visited[i] = true;\n            current.add(nums[i]);\n\n            backtrack(nums, current, visited, result);\n\n            current.remove(current.size() - 1);\n            visited[i] = false;\n        }\n    }\n}\n

The interviewer paid close attention to:\nrecursion flow,\nbacktracking cleanup and\nspace complexity.

Round 3 : Resume Discussion + Kafka + PostgreSQL + DSA

This round was probably the most discussion-heavy round.\nThe interviewer explored:\nKafka,\nPostgreSQL,\ntransactions,\nACID properties and\nDSA basics.\nThis round felt more like a backend engineering conversation than a coding interview.

Kafka Questions

The interviewer asked several practical Kafka questions.

Difference Between Topic and Partition

I explained:

Topic : Logical category of messages.
Partition : Physical division of a topic used for scalability and parallel processing.

I also explained how partitions enable Kafka to distribute load across brokers.

Consumer vs Consumer Group

I explained that:

consumers read messages
consumer groups allow parallel consumption

Within a consumer group: one partition is consumed by only one consumer\nThis ensures message processing balance.

Scenario Question – 2 Partitions and 3 Consumers

The interviewer asked: If there are 2 partitions and 3 consumers, how are they distributed?

I explained that:\nonly 2 consumers will actively consume\nand the third consumer remains idle.\nbecause one partition cannot be shared among multiple consumers within the same group simultaneously.

Another important question was: How do you maintain message order in Kafka?

I explained that ordering is guaranteed only within a partition.\nSo messages with the same key should be routed to the same partition.\nThis ensures proper sequential processing.

PostgreSQL Questions

The interviewer then shifted toward SQL concepts.\nOne question was: Difference Between Primary Key and Unique Constraint

I explained:

Primary Key

uniquely identifies records
cannot contain NULL
only one per table

Unique Constraint

also prevents duplicates
allows NULL values (depending on DB)
multiple unique constraints possible

Next, The interviewer asked: Explain ACID properties

Instead of rushing definitions, I explained each property with practical examples.

\n
Atomicity Either entire transaction succeeds or fails completely.
\n
\n
Consistency Database remains in valid state after transaction.
\n
\n
Isolation Concurrent transactions should not interfere incorrectly.
\n
\n
Durability Committed changes must survive failures.
\n

The interviewer also asked: What is a transaction?\nand What are isolation levels?

I discussed:\nRead Uncommitted,\nRead Committed,\nRepeatable Read and\nSerializable.\nalong with concurrency issues like:\ndirty reads,\nphantom reads, and\nnon-repeatable reads.

DSA Questions

Two smaller coding questions were asked toward the end.

1. Reverse a String Without Extra Space

The interviewer expected an in-place solution using two pointers.

\nclass Solution {\n\n    public void reverseString(char[] s) {\n        int left = 0;\n        int right = s.length - 1;\n        while (left < right) {\n            char temp = s[left];\n            s[left] = s[right];\n            s[right] = temp;\n            left++;\n            right--;\n        }\n    }\n}\n

2. Find Kth Smallest Element in Array

I discussed multiple approaches:\nsorting,\nmin/max heap and\nquickselect.

The interviewer seemed more interested in optimization trade-offs than final syntax.

Final Result & Overall Experience

Overall, the interview experience at Kotak Mahindra Bank was quite good and much more technical than I expected from a banking company.\nThe process tested:

coding ability
backend fundamentals
distributed systems understanding
communication skills
system design thinking

One important takeaway from this interview was: Backend engineering interviews are becoming increasingly practical\n. Companies now expect engineers to understand not only algorithms, but also:

scalability
distributed systems
messaging systems
databases
deployment strategies
backend architecture decisions

Preparation Tips for Kotak SDE-1 Interviews

If you’re preparing for similar backend-focused interviews, I would strongly recommend focusing on:

medium-level DSA problems
Kafka fundamentals
SQL and PostgreSQL concepts
ACID properties
distributed systems basics
microservices concepts
LLD fundamentals
recursion and backtracking

Most importantly: Practice explaining your thought process clearly\nBecause many interviewers evaluate communication and reasoning as much as coding ability itself.

Recommended Interview Experience

JioHotstar Staff Software Engineer Interview Experience

Disney+ Hotstar SDE-2 Interview Experience | Coding + System Design + Techno Managerial

Uber Senior Software Engineer Interview Experience | Real Interview Questions, System Design & Preparation Guide

Meta Business Engineer (L4 → L5 Consideration) Interview Experience

Rupeek Android Developer Interview Experience | Real Questions Asked, Preparation Tips & Complete Process

Rupeek SDE-3 Interview Experience (3 Rounds ~ Coding, LLD & HLD)

WheelsEye Backend Engineer Interview Experience | DSA Questions, System Design, Backend Deep Dive

Wise Software Engineer Interview Experience | DSA, System Design, Product Thinking

Yext SDE 1 Interview Experience – Complete DSA Questions, Debugging Round, API Challenge & HR Round

Uber SDE 2 Interview Experience (5 Rounds, Selected)

Adobe Software Engineer 2 Interview Experience

Volvo Cars Full Stack Developer Interview Experience (Selected)

Wayfair SDE Interview Experience

Wells Fargo SDE I Interview Experience

Flipkart Machine Coding Round Experience ~ Log Engine Implementation

My Vegapay Backend Engineer (SDE 2) Interview Experience (Rejected)

","categoryId":363,"subCategoryId":363,"contentFormat":5,"blogId":121,"userId":"MjlfNF84LVszMF0ybi10Q19BTmdlX19JdA==","title":"Kotak Mahindra Bank SDE-1 Interview Experience : DSA, LLD, Kafka, PostgreSQL & Distributed Systems","url":"kotak-mahindra-bank-sde-1-interview-experience-dsa-lld-kafka-postgresql-distributed-systems","bannerImage":"","seoDescription":"Kotak Mahindra Bank SDE-1 Interview Experience with Java, Kafka, PostgreSQL, Distributed Systems, LLD, DSA & Backend Engineering Questions.","generatedOn":"2026-05-26T07:12:51","updatedOn":"2026-05-26T07:12:51"},"popularContents":[{"id":213,"title":"Amazon SDE II Interview Experience (Bangalore, Selected) ~ Aug 2026","url":"amazon-sde-ii-interview-experience-bangalore-selected-aug-2026","description":null,"seoDescription":"Amazon SDE II interview experience from Bangalore covering 4 rounds, DSA, LLD, system design, Leadership Principles, coding questions and selection.","contentType":5,"generatedOn":"2026-10-15T14:07:10.9988744Z","viewCount":0},{"id":138,"title":"DSA Patterns for Coding Interviews: Complete LeetCode Roadmap (Beginner to Advanced)","url":"dsa-patterns-for-coding-interviews-complete-leetcode-roadmap-beginner-to-advanced","description":null,"seoDescription":"Master every LeetCode pattern for coding interviews. Learn Arrays, Sliding Window, Graphs, Dynamic Programming, Trees, Heaps and more with 250+ curated problem","contentType":5,"generatedOn":"2026-10-15T14:07:10.9988624Z","viewCount":0},{"id":167,"title":"Meesho SDE-1 Online Assessment Interview Experience (Remote) - Rejected","url":"meesho-sde-1-online-assessment-interview-experience-remote-rejected","description":null,"seoDescription":"Read a real Meesho SDE-1 online assessment experience with coding questions, DSA topics, solutions, difficulty level, preparation tips and interview insights.","contentType":5,"generatedOn":"2026-10-15T14:07:10.998871Z","viewCount":0},{"id":166,"title":"System Design Interview – BIGGEST Mistakes to Avoid","url":"system-design-interview-biggest-mistakes-to-avoid","description":null,"seoDescription":"Learn the biggest mistakes to avoid in a system design interview, from unclear requirements to poor trade-off analysis. Includes real-world cases, advanced insights and examples to help you ace your next system design interview.","contentType":2,"generatedOn":"2026-10-15T14:07:10.9983505Z","viewCount":0},{"id":122,"title":"Zepto SDE-1 Interview Experience (Backend Developer) : Real DSA, LLD, Chess Game Design","url":"zepto-sde-1-interview-experience-backend-developer-real-dsa-lld-chess-game-design","description":null,"seoDescription":" Zepto SDE-1 Backend Interview Experience covering DSA, Dynamic Programming, LLD, API Design, DB Schema, OOP & Product Company Rounds.","contentType":5,"generatedOn":"2026-10-15T14:07:10.9988608Z","viewCount":0},{"id":165,"title":"Top 50+ SQL Interview Questions and Answers for Intermediate to Advanced","url":"top-sql-interview-questions-and-answers-for-intermediate-to-advanced","description":null,"seoDescription":"Top SQL Interview Questions and Answers for Intermediate to Advanced. Top SQL Interview Questions for experience. Frequently asked SQL interview questions with answers","contentType":2,"generatedOn":"2026-10-15T14:07:10.9983458Z","viewCount":0},{"id":172,"title":"Google L4 Software Engineer III interview experience | Selected","url":"google-l4-software-engineer-iii-interview-experience-selected","description":null,"seoDescription":"Google L4 Software Engineer III interview experience with API design, Googlyness, route matching, graph coding rounds, follow-up questions and tips.","contentType":5,"generatedOn":"2026-10-15T14:07:10.9988729Z","viewCount":0},{"id":153,"title":"Visa Software Engineer 1 (SDE-1) Interview Experience | CodeSignal OA + Graph-Based Technical Rounds","url":"visa-software-engineer-1-sde-1-interview-experience-codesignal-oa-graph-based-technical-rounds","description":null,"seoDescription":" Ace your Visa SDE-1 interview with this complete interview experience covering CodeSignal OA, graph coding rounds, hiring manager questions and tips.","contentType":5,"generatedOn":"2026-10-15T14:07:10.9988641Z","viewCount":0},{"id":35,"title":"Cursor vs Copilot : Which AI Coding Assistant Wins in 2025?","url":"cursor-vs-copilot-which-ai-coding-assistant-truly-wins-in-2025","description":null,"seoDescription":"Compare Cursor vs GitHub Copilot on speed, context awareness, multi-file support, pricing and code quality to choose the best AI coding assistant for developers","contentType":5,"generatedOn":"2026-10-15T14:07:10.9988591Z","viewCount":0},{"id":34,"title":"System Design Deep Dive: 25 Essential Interview Questions","url":"system-design-deep-dive-25-essential-interview-questions","description":null,"seoDescription":"","contentType":5,"generatedOn":"2026-10-15T14:07:10.9988549Z","viewCount":0}],"latestContents":[{"id":219,"title":"6 Tools That Made My Life Easier as a Software Engineer","url":"6-tools-that-made-my-life-easier-as-a-software-engineer","description":null,"seoDescription":"The 6 developer tools I use daily as a software engineer: Git, VS Code, Docker, Postman, Chrome DevTools, and AI assistants, with real tips, mistakes, and trade","contentType":5,"generatedOn":"2026-10-15T14:07:10.9976476Z","viewCount":0},{"id":218,"title":"When Should a Business Use Multiple AI Agents Instead of One?","url":"when-should-a-business-use-multiple-ai-agents-instead-of-one","description":null,"seoDescription":"Single agent or multi-agent AI? Learn the 4 signals that justify splitting agents by knowledge, permissions, and risk, plus routing and handoff tips.","contentType":5,"generatedOn":"2026-10-15T14:07:10.9976529Z","viewCount":0},{"id":216,"title":"AI in Clinical Trials Market Estimated to Experience a Hike in Growth by 2035","url":"ai-in-clinical-trials-market-estimated-to-experience-a-hike-in-growth-by-2035","description":null,"seoDescription":"The exclusive information about market dynamics serves as a valuable guide to predict economic scenarios and initiatives taken to enhance future growth. Our mar","contentType":5,"generatedOn":"2026-10-15T14:07:10.9976547Z","viewCount":0},{"id":217,"title":"AI in Clinical Trials Market Estimated to Experience a Hike in Growth by 2035","url":"ai-in-clinical-trials-market-estimated-to-experience-a-hike-in-growth-by-2035","description":null,"seoDescription":"The exclusive information about market dynamics serves as a valuable guide to predict economic scenarios and initiatives taken to enhance future growth. Our mar","contentType":5,"generatedOn":"2026-10-15T14:07:10.9976563Z","viewCount":0},{"id":215,"title":"What Happens When an AI Agent Doesn't Know the Answer?","url":"what-happens-when-an-ai-agent-doesnt-know-the-answer","description":null,"seoDescription":"Most AI agents fail quietly. They guess instead of saying \"I don't know.\" Here's how to design better fallback and human-handoff behavior.","contentType":5,"generatedOn":"2026-10-15T14:07:10.9976577Z","viewCount":0},{"id":214,"title":"Greedy Algorithms Explained: How They Work, When They Fail and How to Use Them","url":"greedy-algorithms-explained-how-they-work-when-they-fail-and-how-to-use-them","description":null,"seoDescription":"Learn greedy algorithms step by step with C# code Dijkstra, Huffman coding, knapsack and MSTs plus when greedy fails and how to prove it's correct","contentType":5,"generatedOn":"2026-10-15T14:07:10.9976632Z","viewCount":0},{"id":213,"title":"Amazon SDE II Interview Experience (Bangalore, Selected) ~ Aug 2026","url":"amazon-sde-ii-interview-experience-bangalore-selected-aug-2026","description":null,"seoDescription":"Amazon SDE II interview experience from Bangalore covering 4 rounds, DSA, LLD, system design, Leadership Principles, coding questions and selection.","contentType":5,"generatedOn":"2026-10-15T14:07:10.9976646Z","viewCount":0},{"id":212,"title":"How to Get 10x Better AI Answers Without Writing Better Prompts : 10 Proven Techniques","url":"how-to-get-10x-better-ai-answers-without-writing-better-prompts-10-proven-techniques","description":null,"seoDescription":"Get better AI answers without complex prompts. Learn 10 practical techniques using context, examples, tools, feedback, and verification.","contentType":5,"generatedOn":"2026-10-15T14:07:10.9976658Z","viewCount":0},{"id":211,"title":"I Interviewed for a Microsoft SDE I Role. Here's Everything That Happened.","url":"i-interviewed-for-a-microsoft-sde-i-role-heres-everything-that-happened","description":null,"seoDescription":"My real Microsoft SDE I interview experience, all 4 rounds, the exact DSA problems with fully tested solutions, the WhatsApp system design round","contentType":5,"generatedOn":"2026-10-15T14:07:10.997667Z","viewCount":0},{"id":140,"title":"PolicyBazaar Software Development Engineer (SDE) Interview Experience | DSA, Core CS & System Design","url":"policybazaar-software-development-engineer-sde-interview-experience-dsa-core-cs-system-design","description":null,"seoDescription":"Detailed PolicyBazaar SDE interview experience covering 3 rounds: DSA coding, core CS assessment and system design with key learnings and insights.","contentType":5,"generatedOn":"2026-10-15T14:07:10.9976682Z","viewCount":0}],"relatedContents":[{"id":181,"title":"My Teradata SWE Intern Interview Experience (Full Story, Real Code, Real Mistakes)","url":"my-teradata-swe-intern-interview-experience-full-story-real-code-real-mistakes","description":null,"seoDescription":"A real, first-person Teradata SWE intern interview experience. Full Java code for every DSA question, mistakes I made, hints","contentType":5,"generatedOn":"2026-10-15T14:07:11.0023118Z","viewCount":0},{"id":175,"title":"American Express (AMEX) Online Assessment Experience (2026) | 3 Coding Questions","url":"american-express-amex-online-assessment-experience-2026-3-coding-questions","description":null,"seoDescription":"Read my American Express Online Assessment 2026 experience with 3 coding questions, C# solutions, approaches, difficulty analysis and preparation tips.","contentType":5,"generatedOn":"2026-10-15T14:07:11.0023165Z","viewCount":0},{"id":173,"title":"Uber SDE-2 Interview Experience : LLD, HLD, DSA & Hiring Manager Round","url":"uber-sde-2-interview-experience-lld-hld-dsa-hiring-manager-round","description":null,"seoDescription":"Read a real Uber SDE-2 interview experience covering DSA, low-level design, high-level system design, behavioral rounds, hiring freeze and key takeaways.","contentType":5,"generatedOn":"2026-10-15T14:07:11.0023217Z","viewCount":0},{"id":163,"title":"VISA Staff Software Engineer Online Assessment (OA) Experience (2026) | Two Coding Questions | Rejected","url":"visa-staff-software-engineer-online-assessment-oa-experience-2026-two-coding-questions-rejected","description":null,"seoDescription":" VISA Staff Software Engineer OA experience with HackerRank coding questions on Graphs and Dynamic Programming, solutions, tips, and preparation guide.","contentType":5,"generatedOn":"2026-10-15T14:07:11.0023231Z","viewCount":0},{"id":162,"title":"KLA Software Engineer Interview Experience (DSA Round) | Two Coding Questions | July 2026","url":"kla-software-engineer-interview-experience-dsa-round-two-coding-questions-july-2026","description":null,"seoDescription":"KLA Software Engineer interview experience with two DSA coding questions, Java solutions, HashMap, Monotonic Stack, follow-up questions and tips.","contentType":5,"generatedOn":"2026-10-15T14:07:11.0023245Z","viewCount":0},{"id":153,"title":"Visa Software Engineer 1 (SDE-1) Interview Experience | CodeSignal OA + Graph-Based Technical Rounds","url":"visa-software-engineer-1-sde-1-interview-experience-codesignal-oa-graph-based-technical-rounds","description":null,"seoDescription":" Ace your Visa SDE-1 interview with this complete interview experience covering CodeSignal OA, graph coding rounds, hiring manager questions and tips.","contentType":5,"generatedOn":"2026-10-15T14:07:11.0023261Z","viewCount":0},{"id":145,"title":"Infosys Specialist Programmer Interview Experience (2 Rounds) | OA + Technical Interview | Selected","url":"infosys-specialist-programmer-interview-experience-2-rounds-oa-technical-interview-selected","description":null,"seoDescription":"Infosys Specialist Programmer interview experience with OA and technical rounds covering DSA, DP, Sliding Window, Bit Manipulation, OOP and tips.","contentType":5,"generatedOn":"2026-10-15T14:07:11.0023273Z","viewCount":0},{"id":141,"title":"Postman Software Development Engineer - II (Full Stack) Interview Experience","url":"postman-software-development-engineer-ii-full-stack-interview-experience","description":null,"seoDescription":"Detailed Postman SDE-2 (Full Stack) interview experience covering recruiter screening, frontend/backend fundamentals, architecture discussions, machine coding, ","contentType":5,"generatedOn":"2026-10-15T14:07:11.0023284Z","viewCount":0},{"id":136,"title":"Qualcomm C++ Engineer Interview Experience","url":"qualcomm-cpp-engineer-interview-experience","description":null,"seoDescription":"Qualcomm C++ Engineer Interview Experience (Rejected) | OS, C++ Concepts, DSA & Tree + Stack Coding Problems Breakdown","contentType":5,"generatedOn":"2026-10-15T14:07:11.0023295Z","viewCount":0},{"id":134,"title":"Meta(Facebook) Software Engineer Round 1 Interview Experience","url":"metafacebook-software-engineer-round-1-interview-experience","description":null,"seoDescription":"Meta(facebook) Software Engineer Interview Experience | Sort Even Odd Indices & Making a Large Island | Coding Round Breakdown","contentType":5,"generatedOn":"2026-10-15T14:07:11.0023309Z","viewCount":0}]}}},"source":{"isMobile":false}}; window.__CLIENT_RENDER__ = false;

Kotak Mahindra Bank SDE-1 Interview Experience : DSA, LLD, Kafka, PostgreSQL & Distributed Systems

Interview Process Overview

Round 1 : Distributed Systems, DSA & Low-Level Design

Distributed Systems Questions

DSA Problem :Container With Most Water

Low-Level Design Round – Design Uber/Ola

Round 2 : DSA Round

Problem 1 – Group Anagrams

Problem 2 – Permutations

Round 3 : Resume Discussion + Kafka + PostgreSQL + DSA

Kafka Questions

Scenario Question – 2 Partitions and 3 Consumers

PostgreSQL Questions

DSA Questions

1. Reverse a String Without Extra Space

2. Find Kth Smallest Element in Array

Final Result & Overall Experience

Preparation Tips for Kotak SDE-1 Interviews

Recommended Interview Experience

Trending Developer Reads

Interview Process Overview

Round 1 : Distributed Systems, DSA & Low-Level Design

Distributed Systems Questions

DSA Problem :Container With Most Water

Low-Level Design Round – Design Uber/Ola

Round 2 : DSA Round

Problem 1 – Group Anagrams

Problem 2 – Permutations

Round 3 : Resume Discussion + Kafka + PostgreSQL + DSA

Kafka Questions

Scenario Question – 2 Partitions and 3 Consumers

PostgreSQL Questions

DSA Questions

1. Reverse a String Without Extra Space

2. Find Kth Smallest Element in Array

Final Result & Overall Experience

Preparation Tips for Kotak SDE-1 Interviews

Recommended Interview Experience