Track: Other

Meesho Other Roles Interview Briefing

Overview

The Other Roles category at Meesho includes diverse positions such as SQL-focused roles, HDL/DSA roles, and Product/Monetization Strategy roles. The interview process varies by role but typically involves technical rounds, case studies, or project discussions.

---

Round Breakdown and Key Questions

1. SQL-Focused Role

Duration: 1 hour Format: SQL queries and database design. Focus: Complex SQL queries, database modeling, and optimizations.

Commonly Asked Questions:

• 4-Table SQL Query: Optimizing joins and subqueries.

---

2. HDL/DSA Role

Duration: 1 hour Format: Hardware Description Languages (HDL) and DSA problems. Focus: HDL concepts, DSA proficiency, and problem-solving.

Commonly Asked Questions:

• HDL Questions: Logic design, FPGA, and ASIC concepts.
• DSA Problems: Arrays, Strings, Graphs, and Trees.

---

3. Product/Monetization Strategy Role

Duration: 1 hour Format: Product strategy, monetization models, and data analytics. Focus: Content creator monetization, subscription models, and ad-revenue sharing.

Commonly Asked Questions:

• Monetization Strategies: Brand partnerships, tiered subscriptions.
• Data Analytics: Tools for creators and performance tracking.

---

Key Takeaways

• Success: Candidates who demonstrate role-specific technical skills and problem-solving abilities tend to succeed.
• Rejection Reasons: Poor performance in technical rounds or lack of role-specific knowledge.
• Preparation Tips:
  • Study role-specific concepts (e.g., SQL for data roles, HDL for hardware roles).
  • Practice problem-solving and case studies.
  • Prepare for behavioral and situational questions.

---

Track: SDE-2

Meesho SDE-2 Interview Briefing

Overview

The SDE-2 role at Meesho emphasizes problem-solving, system design, and practical implementation. Candidates typically undergo 3-4 rounds, including Problem Solving/Data Structures and Algorithms (DSA), Machine Coding, System Design, and a Hiring Manager round. The process is rigorous, with a focus on scalability, edge cases, and real-world problem-solving. Rejections often occur due to incomplete implementations, time management issues, or mismatches in role expectations.

---

Round Breakdown and Key Questions

1. Problem Solving / DSA Round

Duration: 1 hour Format: 2-3 coding problems on platforms like HackerRank or LeetCode. Focus: Medium to hard-level problems, often involving Dynamic Programming, Graphs, or Trees.

Commonly Asked Questions:

• Minimum Steps to Reach Target by a Knight
• Remove All Adjacent Duplicates in String II
• Course Schedule II
• Container With Most Water
• Number of Islands
• Infinite Grid Problem (Knight's Possible Ways)
• Asteroid Collision
• Matrix Connected Components Problem

---

2. Machine Coding Round

Duration: 1.5–2 hours Format: Design and implement a scalable system with specific functionalities. Focus: Low-Level Design (LLD), OOP principles, and practical implementation.

Commonly Asked Questions:

• Snake & Ladder Game Design (with extensions like player interactions).
• Facebook APIs Design (Create Post, Delete Post, Get Feed, Get Feed Paginated, Follow, Unfollow).
• Splitwise-like Application (Expense splitting logic: EQUAL, EXACT, PERCENTAGE).
• Elevator System Design (Thread handling, OOP principles).
• Inventory Management System (Order confirmation, stock blocking).
• Restaurant Rating System (Multi-branch support, rating aggregation).

---

3. System Design Round

Duration: 1 hour Format: High-Level Design (HLD) and Low-Level Design (LLD) discussion. Focus: Scalability, microservices architecture, and trade-offs.

Commonly Asked Questions:

• Twitter News Feed Design (HLD).
• Rating and Review System for E-commerce (HLD + LLD).
• Custom Ad Service Design (Scalability, microservices).
• Online Examination System (Database schema, tech stack).
• Trading Platform Design (Similar to existing systems).

---

4. Hiring Manager Round

Duration: 1 hour Format: Project discussion, behavioral questions, and role-specific scenarios. Focus: Depth of experience, problem-solving approach, and cultural fit.

Commonly Asked Questions:

• Project Deep Dive: Detailed discussion on past projects, challenges, and solutions.
• Behavioral Questions: Situational scenarios, teamwork, and conflict resolution.
• Java Optimization Techniques: Garbage collection, system monitoring, and debugging.
• Database Design: Normalization, indexing, and query optimization.

---

Key Takeaways

• Success: Candidates who demonstrate clarity in thought, scalability awareness, and clean code tend to succeed.
• Rejection Reasons: Incomplete implementations, poor time management, or lack of depth in system design discussions.
• Preparation Tips:
  • Practice DSA problems on HackerRank/LeetCode.
  • Focus on design patterns and OOP principles for Machine Coding.
  • Study system design concepts (scalability, microservices, database design).

---

Track: Intern

Meesho Intern Interview Briefing

Overview

The Meesho Intern hiring process is highly competitive and involves 4 rounds: a screening test, a coding round, a low-level design (LLD) round, and a hiring manager round. The process is designed to assess problem-solving, system design, and practical implementation skills in entry-level candidates. Success depends on clean code, scalability awareness, and structured problem-solving.

---

Round Breakdown and Key Questions

1. Screening Test (NextLevel App)

Duration: 30 minutes Format: 20 MCQs + verbal questions (AI-evaluated). Focus: CS fundamentals (OS, DSA, Networks, Error Handling).

Commonly Asked Questions:

• Operating Systems: Process vs. Thread, Memory Management, Paging.
• Data Structures and Algorithms: Arrays, Strings, Graphs, Sorting.
• Computer Networks: TCP/IP, DNS, OSI Model.
• Error Handling: Debugging, Exception Handling.

---

2. Coding Round (HackerRank)

Duration: 105 minutes Format: 3 coding problems (Medium to Hard). Focus: DSA, problem-solving, and time management.

Commonly Asked Questions:

• Binary Search
• Dynamic Programming
• Segment Tree
• Check if a Point Lies Inside a Triangle
• Sum of All Possible Expressions (Insert '+' Operator)
• Sum of Digits at Even and Odd Places

---

3. Low-Level Design (LLD) Round

Duration: 90 minutes Format: Design a system with specific functionalities. Focus: OOP principles, SOLID principles, and practical implementation.

Commonly Asked Questions:

• Inventory Management System (Add products, get inventory, create orders, confirm orders).
• Food Order System (Database schema, APIs, and flow).
• Chat Application (Database schema, APIs, and flow).

---

4. Hiring Manager Round

Duration: 45 minutes Format: Project discussion, behavioral questions, and situational scenarios. Focus: Depth of experience, problem-solving approach, and cultural fit.

Commonly Asked Questions:

• Project Deep Dive: Detailed discussion on past projects, challenges, and solutions.
• Behavioral Questions: Situational scenarios, teamwork, and conflict resolution.
• System Design: Scalability, database design, and trade-offs.

---

Key Takeaways

• Success: Candidates who demonstrate clean code, structured problem-solving, and scalability awareness tend to succeed.
• Rejection Reasons: Poor time management, incomplete implementations, or lack of depth in discussions.
• Preparation Tips:
  • Practice DSA problems on HackerRank/LeetCode.
  • Focus on design patterns and OOP principles for LLD.
  • Study CS fundamentals (OS, Networks, DBMS).

---

Track: SDE-3 / Senior

Meesho SDE-3 Interview Briefing

Overview

The SDE-3/Senior Engineer role at Meesho is designed for experienced engineers (4+ years of experience) and involves 3-5 rounds, including Machine Coding, System Design, Technical Rounds, and a Hiring Manager Round. The process is rigorous, with a strong emphasis on scalability, system design, and leadership qualities. Candidates are expected to demonstrate deep technical expertise, architectural skills, and problem-solving abilities.

---

Round Breakdown and Key Questions

1. Machine Coding Round

Duration: 2 hours Format: Design and implement a scalable system with specific functionalities. Focus: Low-Level Design (LLD), OOP principles, and practical implementation.

Commonly Asked Questions:

• N Elevator System (Thread handling, OOP principles).
• Inventory/Order Management Service (Concurrent users, thread safety).
• Restaurant Rating System (Multi-branch support, rating aggregation).

---

2. System Design Round

Duration: 1–1.5 hours Format: High-Level Design (HLD) and Low-Level Design (LLD) discussion. Focus: Scalability, microservices architecture, and trade-offs.

Commonly Asked Questions:

• Custom Ad Service Design (Scalability, microservices).
• Trading Platform Design (Similar to existing systems).
• Rule Engine System (Scheduling millions of rules, handling collisions).

---

3. Technical Round (Production-Ready Code)

Duration: 1 hour Format: Focus on writing production-ready code and detailed follow-up questions. Focus: Code quality, edge cases, and scalability.

Commonly Asked Questions:

• Cross-Questions on Production-Ready Code (e.g., handling concurrency, thread safety).
• Design Patterns: Singleton, Factory, Observer, etc.

---

4. Hiring Manager Round

Duration: 1 hour Format: Project discussion, behavioral questions, and role-specific scenarios. Focus: Depth of experience, leadership qualities, and cultural fit.

Commonly Asked Questions:

• Project Deep Dive: Detailed discussion on past projects, challenges, and solutions.
• Behavioral Questions: Situational scenarios, teamwork, and conflict resolution.
• Architectural Decisions: Trade-offs, scalability, and system design choices.

---

Key Takeaways

• Success: Candidates who demonstrate deep technical expertise, leadership qualities, and scalability awareness tend to succeed.
• Rejection Reasons: Poor system design choices, lack of depth in discussions, or inability to articulate trade-offs.
• Preparation Tips:
  • Focus on advanced DSA and system design (scalability, microservices).
  • Study design patterns and architectural principles.
  • Practice writing production-ready code and handling edge cases.

---

Track: SDE-1 / New Grad

Meesho SDE-1 Interview Briefing

Overview

The SDE-1 role at Meesho is designed for entry-level engineers and typically involves 4-5 rounds, including an Online Assessment (OA), 2-3 technical rounds, and an HR round. The process is rigorous but fair, with a strong emphasis on problem-solving, system design, and practical implementation. Candidates are expected to demonstrate clean code, scalability awareness, and a structured approach to problem-solving.

---

Round Breakdown and Key Questions

1. Online Assessment (OA)

Duration: 60–100 minutes Format: Coding problems + MCQs (CS fundamentals). Focus: Medium to hard-level problems, often involving DSA, SQL, and problem-solving.

Commonly Asked Questions:

• Coding Problems:

  • Weighted Job Scheduling
  • Water the Plants
  • Activity Selection Problem
  • Minimum Degree of a Connected Trio in a Graph
  • Rectangle Area II
  • CountGoodSubsequences
  • Binary Search
  • Dynamic Programming (Palindromic Strings)
  • Graph Colouring

• MCQs:

  • Operating Systems (Semaphores vs. Mutex, Paging, Virtual vs. Physical Memory)
  • Computer Networks (ARP, DNS, OSI Model)
  • DBMS (SQL vs. NoSQL, Normalization, ACID Properties)
  • OOPs (Inheritance, Polymorphism, Abstraction)
  • C++/Java (STL, Garbage Collection, Vectors)

---

2. Technical Interview 1 (Coding Round)

Duration: 1–1.5 hours Format: 2-3 coding problems on HackerRank/LeetCode. Focus: DSA, problem-solving, and clean code.

Commonly Asked Questions:

• Longest Substring with At Least K Repeating Characters
• Making a Large Island
• Number of Visible People in a Queue
• Find the Longest Equal Subarray
• Stack-Based Balls Collision
• Hashmap and String-Based Problems

---

3. Technical Interview 2 (System Design / LLD Round)

Duration: 1–1.5 hours Format: Design a system with specific functionalities. Focus: Low-Level Design (LLD), OOP principles, and practical implementation.

Commonly Asked Questions:

• Cab Booking System Design (Add drivers, riders, update locations, book rides).
• Social Media System (Create Post, Delete Post, Get Feed, Follow/Unfollow).
• Inventory Management System (Add products, create orders, confirm orders).
• Facebook Newsfeed System (Posting, following users, feed generation).

---

4. HR / Managerial Round

Duration: 1 hour Format: Project discussion, behavioral questions, and role-specific scenarios. Focus: Depth of experience, problem-solving approach, and cultural fit.

Commonly Asked Questions:

• Project Deep Dive: Detailed discussion on past projects, challenges, and solutions.
• Behavioral Questions: Situational scenarios, teamwork, and conflict resolution.
• Java Optimization Techniques: Garbage collection, system monitoring, and debugging.
• Database Design: Normalization, indexing, and query optimization.

---

Key Takeaways

• Success: Candidates who demonstrate clarity in thought, clean code, and scalability awareness tend to succeed.
• Rejection Reasons: Incomplete implementations, poor time management, or lack of depth in discussions.
• Preparation Tips:
  • Practice DSA problems on HackerRank/LeetCode.
  • Focus on design patterns and OOP principles for system design.
  • Study CS fundamentals (OS, Networks, DBMS).

---

Track: Data Science / ML

Meesho Data Science / ML Interview Briefing

Overview

The Data Science/ML role at Meesho involves 4 rounds, including SQL, Spark, Data Modeling, and a Hiring Manager Round. The process is designed to assess technical skills in data engineering, SQL, and Spark, as well as problem-solving abilities.

---

Round Breakdown and Key Questions

1. Technical Round 1 (SQL + Spark Coding)

Duration: 1 hour Format: SQL queries, Spark coding, and data modeling. Focus: SQL proficiency, Spark fundamentals, and data engineering.

Commonly Asked Questions:

• SQL Queries: Complex joins, subqueries, and window functions.
• Spark Coding: Data transformations, aggregations, and optimizations.

---

2. Technical Round 2 (SQL + Data Modeling)

Duration: 1 hour Format: SQL queries, data modeling, and Spark fundamentals. Focus: Data modeling, SQL optimizations, and Spark internals.

Commonly Asked Questions:

• Data Modeling: Schema design, normalization, and indexing.
• Spark Internals: Partitioning, caching, and performance tuning.

---

3. Technical Round 3 (Spark Coding + Internals)

Duration: 1 hour Format: Spark coding and internals. Focus: Spark optimizations, data transformations, and performance.

Commonly Asked Questions:

• Spark Coding: Efficient data processing pipelines.
• Spark Internals: RDDs, DataFrames, and execution plans.

---

4. Hiring Manager Round

Duration: 1 hour Format: Project discussion, behavioral questions, and role-specific scenarios. Focus: Depth of experience, problem-solving approach, and cultural fit.

Commonly Asked Questions:

• Project Deep Dive: Detailed discussion on past projects, challenges, and solutions.
• Behavioral Questions: Situational scenarios, teamwork, and conflict resolution.

---

Key Takeaways

• Success: Candidates who demonstrate strong SQL, Spark, and data engineering skills tend to succeed.
• Rejection Reasons: Poor problem-solving or lack of depth in discussions.
• Preparation Tips:
  • Practice SQL queries and Spark optimizations.
  • Study data modeling and performance tuning.
  • Prepare for behavioral and situational questions.

---

Track: Staff / Principal

Meesho Staff / Principal Engineer Interview Briefing

Overview

The Staff/Principal Engineer role at Meesho is designed for seasoned professionals with extensive experience (8+ years). The interview process focuses on deep technical expertise, leadership, and strategic thinking. Candidates are expected to demonstrate strong architectural skills, problem-solving abilities, and a track record of driving engineering excellence.

---

Round Breakdown and Key Questions

1. Technical Round

Duration: 1 hour Format: Discussion on past projects and challenging technical problems. Focus: Depth of experience, problem-solving, and leadership.

Commonly Asked Questions:

• Toughest Project Discussion: Detailed discussion on the most challenging project you’ve worked on.
• Technical Trade-offs: Scalability, performance, and architectural decisions.
• Leadership Scenarios: How you mentored teams or drove engineering initiatives.

---

Key Takeaways

• Success: Candidates who demonstrate deep technical expertise, leadership, and strategic thinking tend to succeed.
• Rejection Reasons: Lack of depth in discussions or inability to articulate architectural decisions.
• Preparation Tips:
  • Focus on high-level system design and architectural trade-offs.
  • Study leadership principles and team management.
  • Prepare for behavioral and situational questions.

---

Track: Product / Frontend

Meesho Product / Frontend Interview Briefing

Overview

The Product/Frontend role at Meesho involves 3 rounds: JavaScript Fundamentals, React and Problem-Solving, and a Hiring Manager Round. The process is designed to assess technical skills in JavaScript, React, and problem-solving, as well as behavioral fit.

---

Round Breakdown and Key Questions

1. JavaScript Fundamentals Round

Duration: 60 minutes Format: JavaScript concepts, coding tasks, and problem-solving. Focus: Hoisting, closures, deep copying, and practical coding.

Commonly Asked Questions:

• Hoisting: Explanation and examples.
• Deep Copying Objects: Methods and applications.
• Variable Scoping: var, let, const.
• Closures: Practical examples and use cases.
• Memoization: Creating a memoized function.
• Array Flattening: Using the reduce method.

---

2. React and Problem-Solving Round

Duration: 60 minutes Format: React concepts, LeetCode problems, and system design. Focus: React internals, problem-solving, and practical implementation.

Commonly Asked Questions:

• React setState Batching: Before v18 vs. After v18.
• LeetCode Problem: Missing Number
• Tree to Adjacency List Conversion
• Immutable Updates: How to immutably update complex values.
• Redux: State management and architecture.

---

3. Hiring Manager Round

Duration: 1 hour Format: Project discussion, behavioral questions, and role-specific scenarios. Focus: Depth of experience, problem-solving approach, and cultural fit.

Commonly Asked Questions:

• First Contentful Paint (FCP): Explanation and optimization.
• Next.js Architecture: React Server Components and Next.js 13.
• SSR vs. CSR: Trade-offs and use cases.
• Project Discussion: Detailed discussion on past projects.

---

Key Takeaways

• Success: Candidates who demonstrate strong JavaScript, React, and problem-solving skills tend to succeed.
• Rejection Reasons: Poor performance in coding tasks or lack of depth in discussions.
• Preparation Tips:
  • Practice JavaScript fundamentals and React internals.
  • Study Next.js architecture and performance optimization.
  • Prepare for behavioral and situational questions.