--- title: "Meesho interview process and practice questions | Orbit" description: "How Meesho interviews, as candidates commonly report it: the rounds, what interviewers listen for, and 13 practice questions with what a good answer covers." canonical: https://orbitanswer.com/companies/meesho last_reviewed: 2026-10-18 --- [Companies](https://orbitanswer.com/companies) [Roles](https://orbitanswer.com/roles) [Free warm-up](https://orbitanswer.com/warmup) - [Home](https://orbitanswer.com/) - [Companies](https://orbitanswer.com/companies) - Meesho Company interview guide # Meesho interview process and practice questions Candidates commonly report that Meesho's engineering interviews include an online coding test, problem-solving rounds, a low-level design or machine coding round and, for experienced roles, system design, followed by a hiring manager conversation. Meesho's marketplace serves small sellers and value-conscious buyers, many in smaller towns, so questions often turn to those users, regional languages and keeping costs low at scale. As candidates commonly report it; it varies by team, level and year. Last reviewed 18 October 2026. [Practise a mock interview in Meesho's style](https://orbitanswer.com/register) [Warm up free on these questions](https://orbitanswer.com/warmup?track=company%3Ameesho) ## The interview process - 1 Online coding test (for many engineering roles) - 2 Problem-solving / data structures interviews - 3 Low-level design or machine coding round - 4 System design (for experienced roles) - 5 Hiring manager round - 6 HR or culture conversation ## What interviewers listen for - Putting users first: buyers, sellers and delivery partners - Speed: shipping a first version fast and improving it - Acting like an owner of the outcome - Thinking big and long term, not only about the next quarter - Starting from the problem before the solution - Keeping costs low so the product stays affordable - Speaking up, and disagreeing respectfully ## Behavioral questions ### Tell me about a time you shipped a first version quickly and improved it based on what users did. A good answer covers - What the first version included and what you left out on purpose - What users' behaviour showed you - The changes you made and the result ### Describe a time you put your company's or team's goal ahead of your own project. A good answer covers - The conflict between the two - Why you chose the bigger goal and what it cost you - What it achieved for the team ### Tell me about a time you spoke up because you thought a plan was wrong. A good answer covers - What was wrong and how you knew - How you raised it, and with whom - What changed, or what you did if the plan went ahead ### Tell me about a decision you got wrong. How did you find out, and what did you change? A good answer covers - The decision and why it seemed right then - The signal that showed it was wrong - The fix, and what you now check before deciding ## Role and technical questions ### How would you design a catalogue upload flow for small sellers who list products from their phones? A good answer covers - A simple mobile flow: photos, a few fields, bulk upload for many items - Checks: image quality, duplicates, banned items, with clear feedback to the seller - Processing in the background, and support for regional languages ### How would you recommend products to buyers who are new to online shopping and browse in their own language? A good answer covers - Starting with little history: what is popular in their region and category - Learning quickly from views, wishlists and orders - Judging success by orders kept, not only clicks, so returns count against it ### Returns are high in one clothing category. How would you reduce them without hurting sales? A good answer covers - Finding the reasons from return data: size, quality, product not as pictured - Fixes: better size guides, clearer photos, seller quality scores - Watching return rate, orders and ratings together ### How would you keep infrastructure costs low for a service with heavy traffic and low-value orders? A good answer covers - Measuring cost per request or per order first - Caching, cheaper storage tiers, right-sized servers, batch jobs at quiet hours - Where you wouldn't save money: reliability of checkout and payments ### How would you design an API and app to work well on slow mobile networks and low-end phones? A good answer covers - Small responses, pagination and compression - Images sized for the device, and caching on the phone - Safe retries for requests that time out ### How would you detect sellers listing fake or misleading products across a very large catalogue? A good answer covers - Signals: returns and complaints, copied images, prices far below normal - Automated rules or models first, then human review - Penalties and an appeal process, and the cost of wrongly flagging honest sellers ### Estimate how many new sellers could be brought onto the platform from one textile hub, such as Surat, in a year. A good answer covers - A clear structure: businesses in the hub, the share ready to sell online, the share you can reach - Limits such as onboarding capacity and seller support - A sanity check on the final number ## Why Meesho? Fit and HR questions ### Why Meesho? What do you understand about the buyers and sellers it serves? A good answer covers - Who the buyers and sellers are, in a sentence each - Why building for them interests you - How your skills would help them ### Are you comfortable building for users whose lives are very different from yours? How would you learn about them? A good answer covers - An honest answer, with an example of learning about unfamiliar users - Methods: talking to users, watching recordings, reading support tickets - How what you learn would change what you build ## Tips - Keep Meesho's users in mind: buyers watching every rupee and sellers running small businesses. Bring them into design and product answers. - Practise low-level design: clear classes and interfaces and a working demo within the time. - Treat cost as a design constraint; cost per order matters a lot for a marketplace built around low prices. - Use the app as a buyer before the interview, and look at the seller side if you can, so you can talk about real flows. ## Practise it out loud A mock interview asks the way Meesho's interviewers are known to, follows up on your answers and gives you a report. The warm-up is free, needs no account and checks five of these questions as you answer. [Practise a mock interview in Meesho's style](https://orbitanswer.com/register) [Warm up free on these questions](https://orbitanswer.com/warmup?track=company%3Ameesho) ## About this guide Written by Orbit from Meesho's own public pages and what candidates commonly report. Orbit isn't affiliated with Meesho. The questions are practice questions in the style of its interviews, not questions taken from them. Processes change, so check the job post and what your recruiter tells you. ## Role guides to read with this one - [Software engineer Software engineer interviews usually combine coding (solving a problem out loud, often in a shared editor), computer science fundamentals and a discussion of… 17 practice questions](https://orbitanswer.com/roles/software-engineer) - [Backend developer Backend developer interviews usually focus on APIs, databases and how a service behaves under load or failure, alongside coding in the role's main language… 17 practice questions](https://orbitanswer.com/roles/backend-developer) - [Frontend developer Frontend developer interviews usually test JavaScript, HTML and CSS fundamentals, then a framework such as React, often through a live exercise building or… 17 practice questions](https://orbitanswer.com/roles/frontend-developer) - [Product manager Product manager interviews usually test product sense (designing or improving a product for a group of users), analytical thinking (metrics, estimates and… 17 practice questions](https://orbitanswer.com/roles/product-manager) ## More guides: indian product companies - [Nykaa Candidates commonly report that Nykaa's interviews depend on the role: engineering roles include coding, problem-solving and design rounds, while category,… 13 practice questions](https://orbitanswer.com/companies/nykaa) - [Ola Candidates commonly report that Ola's engineering interviews include a coding test, problem-solving rounds, a design round and a hiring manager conversation,… 14 practice questions](https://orbitanswer.com/companies/ola) - [OYO Candidates commonly report that OYO's engineering interviews include problem-solving, design and hiring manager rounds, while business and operations roles… 13 practice questions](https://orbitanswer.com/companies/oyo) - [Paytm Candidates commonly report that Paytm's engineering interviews include an online coding test, two or more technical rounds on problem-solving, design and past… 14 practice questions](https://orbitanswer.com/companies/paytm) - [PhonePe Candidates commonly report that PhonePe's engineering interviews include problem-solving rounds, a machine coding or low-level design round and, for… 13 practice questions](https://orbitanswer.com/companies/phonepe) - [Policybazaar Policybazaar, part of PB Fintech along with Paisabazaar, is an online marketplace where people compare and buy insurance; Paisabazaar does the same for loans… 14 practice questions](https://orbitanswer.com/companies/policybazaar) [All 100 company guides](https://orbitanswer.com/companies) [Guides by role](https://orbitanswer.com/roles)