Zepto SDE-1 Interview Experience (Backend Developer) : Real DSA, LLD, Chess Game Design

Sonam Gupta

Last Updated : 26 May 2026

1.86K Views

#interview-experience

#interview-preparation

#technical-interview

#coding-interview

Adℹ

I interviewed for an SDE-1 Backend Developer role at Zepto and the entire experience felt very similar to a fast-paced product-company backend interview process. The rounds were highly focused on problem-solving speed, clean coding, low-level design, database schema design and practical backend engineering discussions.

At the time of the interview, I had around 1 year 4 months of experience as a Backend Developer. Unfortunately, my previous startup company in Hyderabad had gone through layoffs, so I was actively looking for opportunities. I applied for the role through a Google Form shared by a Zepto employee on LinkedIn and after a short wait, I started receiving interview communication.

One thing I realized very quickly during this process was: Zepto expects strong execution speed. It’s not enough to just know DSA or system design concepts. The interviewers expect you to: think fast, communicate clearly, code cleanly and optimize quickly. especially during the BarRaiser rounds.

The overall difficulty level of the process was medium to hard, mainly because of the time pressure and interviewer expectations. If you’re preparing for:

Zepto SDE-1 interview
backend developer interviews
BarRaiser coding rounds
chess game low-level design
DSA interviews for product companies

then this detailed experience can genuinely help you understand what to expect.

Interview Process Overview

The process mainly consisted of 2 technical rounds.

Round	Focus Area
Round 1	DSA + Problem Solving
Round 2	Low-Level Design + DB Schema + APIs

Both rounds were conducted on BarRaiser. Even though there were only two rounds, the discussions were intense and heavily technical.

Round 1 : DSA & Problem Solving Round

This round was entirely focused on coding. The interviewer clearly mentioned at the beginning that the expectation was: Solve 2 DSA questions within roughly 25 minutes each That immediately created pressure because both correctness and speed mattered heavily. The interviewer was collaborative but also closely evaluated: coding speed, optimization, communication, naming conventions and thought process.

One thing I noticed was that they were not interested in brute-force thinking. They expected optimized solutions almost immediately.

Problem 1 : Minimum Cost For Tickets (Leetcode)

The first problem asked was: Minimum Cost For Tickets This is actually considered a fairly difficult dynamic programming problem, especially under interview pressure.

The problem gives:

a list of travel days
ticket costs for:
- 1-day pass
- 7-day pass
- 30-day pass

Example :


Input: days = [1,4,6,7,8,20], costs = [2,7,15]
Output: 11

The goal is: Find the minimum total cost required to cover all travel days. At first glance, the problem can feel confusing because there are multiple overlapping choices at every step. The interviewer mainly wanted to evaluate:

recursive thinking
dynamic programming optimization
state transition understanding

My Initial Thought Process

I first explained the brute-force recursive idea. At every travel day: buy 1-day pass or 7-day pass or 30-day pass and recursively compute the minimum remaining cost. After discussing recursion, I optimized it using memoization because overlapping subproblems were clearly visible.

Honestly, this problem consumed much more time than expected. The interviewer expected it to be solved within around 25 minutes, but I took nearly 35 minutes to fully complete and explain the optimized solution. Still, the interviewer appreciated the approach because I continuously communicated my reasoning instead of staying silent.


class Solution {

    public int mincostTickets(int[] days, int[] costs) {
        Integer[] dp = new Integer[days.length];
        return solve(0, days, costs, dp);
    }

    private int solve(int index, int[] days, int[] costs, Integer[] dp) {
        if (index >= days.length) {
            return 0;
        }
        if (dp[index] != null) {
            return dp[index];
        }
        int oneDay = costs[0] + solve(index + 1, days, costs, dp);
      
        int i = index;
        while (i < days.length && days[i] < days[index] + 7) {
            i++;
        }
        int sevenDay = costs[1] + solve(i, days, costs, dp);

        i = index;
        while (i < days.length && days[i] < days[index] + 30) {
            i++;
        }
        int thirtyDay = costs[2] + solve(i, days, costs, dp);

        return dp[index] =
                Math.min(oneDay,
                Math.min(sevenDay, thirtyDay));
    }
}

Key Learning from This Problem

One important thing I learned from this round was: Interviewers value communication during difficult problems Even if you are stuck temporarily, continuously explaining:

what you are thinking
why a solution fails
how you are optimizing

creates a much better impression. Silence during interviews usually hurts more than imperfect approaches.

Problem 2 – Daily Temperatures (Leetcode)

The second question was Daily Temperatures. This problem is a classic stack-based problem and comparatively easier once you identify the pattern.

Given an array of temperatures, for every day we need to determine: How many days must pass before a warmer temperature appears If no warmer day exists, return 0 for that position.

Example:


Input:
[73,74,75,71,69,72,76,73]

Output:
[1,1,4,2,1,1,0,0]

The interviewer specifically mentioned that this was a variation of a standard monotonic stack problem.

My Approach

The brute-force approach would compare every future temperature for every index, leading to O(N²) complexity. Instead, I used a monotonic decreasing stack.

The idea is:

maintain indices in decreasing order of temperatures
whenever a warmer temperature appears, resolve pending indices

This reduces complexity to O(N). I solved this problem in around 10 minutes because I had practiced similar stack problems before.


class Solution {

    public int[] dailyTemperatures(int[] temperatures) {
        int n = temperatures.length;
        int[] result = new int[n];
        Stack<Integer> stack = new Stack<>();
        for (int i = 0; i < n; i++) {
            while (!stack.isEmpty() &&
                    temperatures[i] > temperatures[stack.peek()]) {
                int index = stack.pop();
                result[index] = i - index;
            }
            stack.push(i);
        }
        return result;
    }
}

After the round, I received positive feedback from the interviewer. The interviewer mentioned that problem-solving ability was good and optimization understanding was decent. but suggested improving variable naming, coding speed and implementation fluency under pressure

Honestly, this feedback was very fair. At product companies, even small improvements in coding speed make a huge difference because interviewers intentionally keep time pressure high.

I received the Round 2 interview invitation around two days later.

Round 2 : Low-Level Design + Database Schema + APIs

This round was much more backend engineering focused. The interviewer asked me to: Design a Chess Game

Initially, it sounded simple, but the discussion quickly became deep. The interviewer expected:

class structures
design patterns
APIs
database schema
move validation logic
extensibility discussions

This was not just a UML exercise. The interviewer wanted to understand how I think while designing real systems.

Chess Game LLD Discussion

I started by identifying the major entities: Player, Board, Piece, Move, Game and Position. Then I discussed how inheritance can be used for chess pieces. For example: King, Queen, Bishop, Knight, Rook and Pawn. Can inherit from a base Piece class.

I also discussed: encapsulation, abstraction and polymorphism. during the design.

Design Patterns Discussion

The interviewer specifically asked where design patterns could be useful.

I discussed:

Factory Pattern for piece creation
Strategy Pattern for move validation
Singleton Pattern for game manager (optional discussion)

The interviewer seemed more interested in my reasoning than memorized definitions.

Database Schema Design

The next discussion focused on schema design.

I designed tables for players, games, moves and match history. I also explained relationships between entities and why indexing would matter for querying ongoing games efficiently.

The interviewer asked follow-up questions around:

scalability
storing board state
move history optimization

which made the discussion feel very practical.

API Design

The interviewer then asked me to define APIs.

I designed APIs such as:

Start New Game
POST /games/start
Make Move
POST /games/{id}/move
Fetch Game State
GET /games/{id}

I also explained request payloads, responses, status codes and validation handling.

This part of the interview honestly felt very similar to real backend development discussions.

Overall Experience at Zepto

Technically, the interview process at Zepto was genuinely good. The interviewers were technically strong and the rounds tested:

DSA fundamentals
optimization skills
object-oriented design
backend engineering thinking
API design capability

The main challenge was speed, time pressure and implementation clarity.

Important Preparation Advice

If you're preparing for backend-focused SDE-1 interviews at product companies like Zepto, focus heavily on:

dynamic programming
stack problems
recursion + memoization
LLD fundamentals
API design
database schema design
OOP principles
design patterns

Most importantly: Practice solving problems under time pressure Because knowing the solution and implementing it quickly are two completely different skills during interviews.

Recommended Interview Experience

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

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 mainly consisted of 2 technical rounds.

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

Round	Focus Area
Round 1	DSA + Problem Solving
Round 2	Low-Level Design + DB Schema + APIs

Both rounds were conducted on BarRaiser. Even though there were only two rounds, the discussions were intense and heavily technical.

Round 1 : DSA & Problem Solving Round

One thing I noticed was that they were not interested in brute-force thinking. They expected optimized solutions almost immediately.

Problem 1 : Minimum Cost For Tickets (Leetcode)

The first problem asked was: Minimum Cost For Tickets This is actually considered a fairly difficult dynamic programming problem, especially under interview pressure.

The problem gives:

a list of travel days
ticket costs for:\n
- 1-day pass
- 7-day pass
- 30-day pass
\n

Example :

\nInput: days = [1,4,6,7,8,20], costs = [2,7,15]\nOutput: 11\n

recursive thinking
dynamic programming optimization
state transition understanding

My Initial Thought Process

\nclass Solution {\n\n    public int mincostTickets(int[] days, int[] costs) {\n        Integer[] dp = new Integer[days.length];\n        return solve(0, days, costs, dp);\n    }\n\n    private int solve(int index, int[] days, int[] costs, Integer[] dp) {\n        if (index >= days.length) {\n            return 0;\n        }\n        if (dp[index] != null) {\n            return dp[index];\n        }\n        int oneDay = costs[0] + solve(index + 1, days, costs, dp);\n      \n        int i = index;\n        while (i < days.length && days[i] < days[index] + 7) {\n            i++;\n        }\n        int sevenDay = costs[1] + solve(i, days, costs, dp);\n\n        i = index;\n        while (i < days.length && days[i] < days[index] + 30) {\n            i++;\n        }\n        int thirtyDay = costs[2] + solve(i, days, costs, dp);\n\n        return dp[index] =\n                Math.min(oneDay,\n                Math.min(sevenDay, thirtyDay));\n    }\n}\n

Key Learning from This Problem

One important thing I learned from this round was: Interviewers value communication during difficult problems Even if you are stuck temporarily, continuously explaining:

what you are thinking
why a solution fails
how you are optimizing

creates a much better impression. Silence during interviews usually hurts more than imperfect approaches.

Problem 2 – Daily Temperatures (Leetcode)

The second question was Daily Temperatures. This problem is a classic stack-based problem and comparatively easier once you identify the pattern.

Given an array of temperatures, for every day we need to determine: How many days must pass before a warmer temperature appears If no warmer day exists, return 0 for that position.

Example:

\nInput:\n[73,74,75,71,69,72,76,73]\n\nOutput:\n[1,1,4,2,1,1,0,0]\n

The interviewer specifically mentioned that this was a variation of a standard monotonic stack problem.

My Approach

The brute-force approach would compare every future temperature for every index, leading to O(N²) complexity. Instead, I used a monotonic decreasing stack.

The idea is:

maintain indices in decreasing order of temperatures
whenever a warmer temperature appears, resolve pending indices

This reduces complexity to O(N). I solved this problem in around 10 minutes because I had practiced similar stack problems before.

\nclass Solution {\n\n    public int[] dailyTemperatures(int[] temperatures) {\n        int n = temperatures.length;\n        int[] result = new int[n];\n        Stack<Integer> stack = new Stack<>();\n        for (int i = 0; i < n; i++) {\n            while (!stack.isEmpty() &&\n                    temperatures[i] > temperatures[stack.peek()]) {\n                int index = stack.pop();\n                result[index] = i - index;\n            }\n            stack.push(i);\n        }\n        return result;\n    }\n}\n

Honestly, this feedback was very fair. At product companies, even small improvements in coding speed make a huge difference because interviewers intentionally keep time pressure high.

I received the Round 2 interview invitation around two days later.

Round 2 : Low-Level Design + Database Schema + APIs

This round was much more backend engineering focused. The interviewer asked me to: Design a Chess Game

Initially, it sounded simple, but the discussion quickly became deep. The interviewer expected:

class structures
design patterns
APIs
database schema
move validation logic
extensibility discussions

This was not just a UML exercise. The interviewer wanted to understand how I think while designing real systems.

Chess Game LLD Discussion

I also discussed: encapsulation, abstraction and polymorphism. during the design.

Design Patterns Discussion

The interviewer specifically asked where design patterns could be useful.

I discussed:

Factory Pattern for piece creation
Strategy Pattern for move validation
Singleton Pattern for game manager (optional discussion)

The interviewer seemed more interested in my reasoning than memorized definitions.

Database Schema Design

The next discussion focused on schema design.

I designed tables for players, games, moves and match history. I also explained relationships between entities and why indexing would matter for querying ongoing games efficiently.

The interviewer asked follow-up questions around:

scalability
storing board state
move history optimization

which made the discussion feel very practical.

API Design

The interviewer then asked me to define APIs.

I designed APIs such as:

Start New Game
POST /games/start
Make Move
POST /games/{id}/move
Fetch Game State
GET /games/{id}

I also explained request payloads, responses, status codes and validation handling.

This part of the interview honestly felt very similar to real backend development discussions.

Overall Experience at Zepto

Technically, the interview process at Zepto was genuinely good. The interviewers were technically strong and the rounds tested:

DSA fundamentals
optimization skills
object-oriented design
backend engineering thinking
API design capability

The main challenge was speed, time pressure and implementation clarity.

Important Preparation Advice

If you're preparing for backend-focused SDE-1 interviews at product companies like Zepto, focus heavily on:

dynamic programming
stack problems
recursion + memoization
LLD fundamentals
API design
database schema design
OOP principles
design patterns

Most importantly: Practice solving problems under time pressure Because knowing the solution and implementing it quickly are two completely different skills during interviews.

Recommended Interview Experience

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

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":122,"userId":"MjlfNF84LVszNl0ybi10Q19BTmdlX19JdA==","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","bannerImage":"","seoDescription":" Zepto SDE-1 Backend Interview Experience covering DSA, Dynamic Programming, LLD, API Design, DB Schema, OOP & Product Company Rounds.","generatedOn":"2026-05-26T11:19:22","updatedOn":"2026-05-26T11:19:22"},"popularContents":[{"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-14T22:22:43.9421765Z","viewCount":0},{"id":168,"title":"Amazon SDE-2 Interview Experience (3 Years Experience)","url":"amazon-sde-2-interview-experience-3-years-experience","description":null,"seoDescription":" Read a real Amazon SDE-2 interview experience covering the online assessment, coding rounds, object-oriented design, leadership principles and system design.","contentType":5,"generatedOn":"2026-10-14T22:22:43.9421911Z","viewCount":0},{"id":83,"title":"Uber SDE 2 Interview Experience (5 Rounds, Selected) - Complete DSA Questions with solution, System Design & Managerial Round","url":"uber-sde-2-interview-experience","description":null,"seoDescription":"Uber SDE 2 interview experience with 5 rounds, real DSA questions, system design, coding round, and preparation tips to crack Uber interviews.","contentType":5,"generatedOn":"2026-10-14T22:22:43.9421855Z","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-14T22:22:43.9417089Z","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-14T22:22:43.9421934Z","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-14T22:22:43.9421968Z","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-14T22:22:43.9417143Z","viewCount":0},{"id":197,"title":"My Adobe SDE Interview Experience (Aug 2026) 5 Rounds, Selected","url":"my-adobe-sde-interview-experience-aug-2026-5-rounds-selected","description":null,"seoDescription":"Real Adobe SDE interview: 5 rounds, 4 DSA problems (Rotate Array, BSTs, Kth Smallest Matrix), code review & behavioral round. Full solutions + tips.","contentType":5,"generatedOn":"2026-10-14T22:22:43.9421949Z","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-14T22:22:43.9421892Z","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-14T22:22:43.9407167Z","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-14T22:22:43.9407218Z","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-14T22:22:43.9407235Z","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-14T22:22:43.940728Z","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-14T22:22:43.9407295Z","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-14T22:22:43.9407498Z","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-14T22:22:43.9407516Z","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-14T22:22:43.9407531Z","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-14T22:22:43.9407547Z","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-14T22:22:43.9407564Z","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-14T22:22:43.9460427Z","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-14T22:22:43.9460469Z","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-14T22:22:43.9460483Z","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-14T22:22:43.94605Z","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-14T22:22:43.9460515Z","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-14T22:22:43.946053Z","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-14T22:22:43.9460543Z","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-14T22:22:43.9460555Z","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-14T22:22:43.9460567Z","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-14T22:22:43.9460581Z","viewCount":0}]}}},"source":{"isMobile":false}}; window.__CLIENT_RENDER__ = false;

Zepto SDE-1 Interview Experience (Backend Developer) : Real DSA, LLD, Chess Game Design

Interview Process Overview

Round 1 : DSA & Problem Solving Round

Problem 1 : Minimum Cost For Tickets (Leetcode)

Problem 2 – Daily Temperatures (Leetcode)

Round 2 : Low-Level Design + Database Schema + APIs

Chess Game LLD Discussion

Design Patterns Discussion

Database Schema Design

API Design

Overall Experience at Zepto

Important Preparation Advice

Recommended Interview Experience

Trending Developer Reads

Interview Process Overview

Round 1 : DSA & Problem Solving Round

Problem 1 : Minimum Cost For Tickets (Leetcode)

Problem 2 – Daily Temperatures (Leetcode)

Round 2 : Low-Level Design + Database Schema + APIs

Chess Game LLD Discussion

Design Patterns Discussion

Database Schema Design

API Design

Overall Experience at Zepto

Important Preparation Advice

Recommended Interview Experience