Witeso

Rank	Topic	Frequency	Percentage
1	Array	19	43.2%
2	String	10	22.7%
3	Hash Table	9	20.5%
4	Database	8	18.2%
5	Dynamic Programming	7	15.9%
6	Math	5	11.4%
7	Greedy	4	9.1%
8	Two Pointers	4	9.1%
9	Sorting	4	9.1%
10	Heap (Priority Queue)	3	6.8%
11	Stack	3	6.8%
12	Sliding Window	3	6.8%
13	Depth-First Search	2	4.5%
14	Binary Search	2	4.5%
15	Geometry	2	4.5%
16	Linked List	2	4.5%
17	Design	2	4.5%
18	Graph Theory	2	4.5%
19	Prefix Sum	2	4.5%
20	Divide and Conquer	1	2.3%
21	Union-Find	1	2.3%
22	Ordered Set	1	2.3%
23	Bit Manipulation	1	2.3%
24	Matrix	1	2.3%
25	Simulation	1	2.3%
26	Data Stream	1	2.3%
27	Combinatorics	1	2.3%
28	Enumeration	1	2.3%
29	Breadth-First Search	1	2.3%
30	Monotonic Stack	1	2.3%
31	Counting	1	2.3%
32	Eulerian Circuit	1	2.3%

No.	Question Title	Link	Difficulty
1	Sum of Perfect Square Ancestors	Visit	Hard
2	Design Exam Scores Tracker	Visit	Medium
3	Number of Unique XOR Triplets II	Visit	Medium
4	Number of Unique XOR Triplets I	Visit	Medium
5	Number of Possible Sets of Closing Branches	Visit	Hard
6	Restricted	Restricted	Hard
7	Restricted	Restricted	Hard
8	Restricted	Restricted	Hard
9	Restricted	Restricted	Hard
10	Restricted	Restricted	Hard
11	Restricted	Restricted	Hard
12	Restricted	Restricted	Hard
13	Restricted	Restricted	Hard
14	Restricted	Restricted	Hard
15	Restricted	Restricted	Hard

Frequently Asked Questions

Common questions about Meesho interviews

Meesho interviews are medium to hard, emphasizing DSA, scalability, and their 14 leadership principles. Dedicate 2-3 months to preparation: solve 150-200 LeetCode problems (focus on medium/hard), master behavioral stories using the STAR method, and study system design fundamentals for scalability. The Bar Raiser round uniquely assesses cultural fit, so practice linking your experiences to Meesho's values of ownership and customer obsession.

Prioritize DSA (arrays, trees, graphs, DP) and system design basics (APIs, databases, caching). For SDE-2+/3 roles, deepen knowledge in distributed systems, microservices, and scalability trade-offs. Review Meesho's engineering blog for their tech stack (React, Python, Java) and incorporate real-world e-commerce scenarios (e.g., high-traffic catalog searches) into your solutions.

Failing to ask clarifying questions before coding, overlooking edge cases or scalability constraints, and giving generic answers disconnected from Meesho's business context. Avoid rushing through the Bar Raiser; instead, prepare structured stories highlighting ownership and data-driven impact. Also, not practicing communication of thought process aloud during coding rounds is a frequent pitfall.

Demonstrate explicit ownership by discussing projects where you drove end-to-end delivery and handled trade-offs. Show scalability thinking—mention techniques like sharding or CDNs relevant to e-commerce. Naturally weave Meesho's leadership principles into your answers, and ask insightful, technical questions about their infrastructure challenges during the interview.

You can expect feedback within 2-4 weeks after the final round, though the Bar Raiser review may extend this. Recruiters typically provide updates within 10 business days post-final interview. If communication lags, send a polite follow-up email to your recruiter referencing your interview date and continued enthusiasm for the role.

SDE-1 focuses on implementing well-defined tasks and learning the codebase; SDE-2 owns feature delivery, mentors juniors, and contributes to design discussions; SDE-3 sets technical vision, architects large-scale systems, and influences product strategy. Interview depth increases with level—expect more architectural and cross-team impact questions for senior roles.

Use LeetCode (prioritize medium/hard problems), Grokking the System Design Interview, and 'Designing Data-Intensive Applications' for depth. Study Meesho's engineering blog and Glassdoor reviews for recent question patterns. Practice behavioral responses with Meesho's leadership principles as prompts, and conduct mock interviews focusing on the Bar Raiser's cultural assessment format.

Meesho thrives on high ownership, fast-paced execution, and data-centric decision-making. Engineers are expected to operate autonomously, scale systems for millions of users, and directly impact business metrics. Be ready to discuss past ambiguity-handling and how you balance speed with robustness—their culture rewards initiative and measurable results over rigid hierarchy.

Meesho Questions

Topic Frequency Analysis

All Topics

Frequently Asked Questions