Academic snapshot
Floor: Often 7.0 / 70%
Degrees: B.Tech/B.E./M.Tech (CS/IT/ECE+)
Backlogs: None active
Year: Final year / recent grad
Meesho Placement Papers 2026
Meesho is an Indian social commerce and reseller marketplace founded in 2015. It is known for enabling small sellers through WhatsApp-first commerce and a large consumer app. Engineering teams build marketplace, logistics, and seller tools at scale.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Meesho fresher eligibility for campus drives
Meesho does not publish one universal CGPA cutoff for every India SDE drive. What students see depends on campus JD wording vs careers portal / referral posts. Treat numbers below as candidate-reported (as of August 2026) - not a guarantee from Meesho HR.
Who this hub is for
- For: Students targeting SDE-1 / Software Development Engineer roles on Meesho’s social-commerce platform teams - mostly Bengaluru-centred engineering stories.
- Not the same track: Pure business / reseller-ops roles, or assuming “e-commerce = same paper as Flipkart.”
- Experienced hires: Mid-level loops may add deeper LLD/backend and different CTC. Use fresher sections as a base.
Degree, projects, and “is 7.0 enough?”
Yes - 7.0 / 70% meets the commonly reported floor on many posts. It is not a selection guarantee. A 7.2 with two fully passing OA solutions and a clear inventory/order story beats an 8.8 who freezes on graphs.
Projects that help: catalog search, order workflows, recommendation demos, inventory sync, or any API with real failure modes. A ML certificate stack with zero systems talk rarely impresses Round 2.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT timing, college CGPA list when printed | Coding bar, interview depth |
| Careers portal / referral | Resume screen volume; sometimes softer published CGPA language | Still expect OA + tech loop |
| Intern → full-time | Conversion interviews may skip a stage | You still defend projects and code |
Off-campus does not mean easier coding. It often means more applicants fighting the same 60-90 minute filter.
Documents and portal hygiene
- Keep academic marks consistent with the careers form - BV catches typos.
- If you have internship NDAs, prepare a public version of your project story you can still defend.
- Screenshot the invite’s duration and language list; “my senior’s OA was 120 minutes” is useless without your own mailer.
- For referrals, still treat OA as the exam - referrals skip lines, not coding bars.
- When year pages disagree with this hub on CTC midpoints, prefer the hub band for expectation-setting and the year page for question flavour.
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.0+ CGPA / ~70% across 10th, 12th, graduation | Verify every drive |
| Degree | B.Tech / B.E. / M.Tech | Related computing degrees on many posts |
| Branch | CS, IT, ECE (and related) | Strong DSA can help adjacent branches |
| Year | Final year + recent grads (~1 year) | Internship → conversion paths also appear |
| Backlogs | No active backlogs | Clear before offer paperwork |
| Coding languages | C, C++, Java, Python, JavaScript | Stick to one for OA + interviews |
| Gap years | Often max ~1 year | Explain with skills |
Skills & focus
Primary: Medium DSA
Secondary: E-commerce system design
First filter: Timed OA (2-3 problems)
Differentiator: Pragmatic scale talk for catalog/orders
Selection feel by CGPA band
| CGPA range | Rough chances | Reality check |
|---|---|---|
| 7.0-7.4 | Meets many reported floors | Need strong OA + design talk |
| 7.5-8.0 | Common in shortlisted chatter | Helps resume screen; OA still decides |
| 8.0+ | Strong for competitive pools | CGPA alone never clears Round 2 |
| Below printed floor | Often filtered before OA | Focus on drives where you qualify |
Meesho previous year papers & PDFs
Download 2026 Meesho placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Meesho previous year papers actually train
Meesho does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers for OA and early technical rounds - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed accuracy on 2-3 medium DSA problems (60-90 min) |
| Technical 1 | Live coding narration: brute → optimize → edge cases |
| Technical 2 | Catalog/orders/recommendations design + advanced DSA |
| Managerial / HR | Ownership, impact, Why Meesho, Bengaluru logistics |
Themes that keep repeating (2024-2026)
- 2024 cycles: OA stayed coding-heavy (2-3 mediums). Arrays, trees, graphs, and DP dominate. Interviews already asked e-commerce design at fresher depth. Students who only drilled Easy problems without timeboxes lost the OA shortlist.
- 2025 loops: Stronger pressure on optimal solutions and scale chatter after code. Some campus write-ups describe pen-and-paper group coding before design-style rounds. Domain vocabulary - catalog, inventory, order state machines, recommendations - separates Round 2 clears from buzzword rejects.
- 2026 prep expectation: Keep medium DSA warm and add social-commerce pragmatism (reseller/supplier constraints, cheap devices, high SKU counts). Treat PDF packs as pattern catalogs, not scripts of tomorrow’s live OA.
How to use one paper set in a single sitting
- Timed: run a full 60-90 minute mock with 2-3 coding prompts in your OA language.
- Untimed review: rewrite the cleaner solution; list three e-commerce edge cases (out-of-stock, duplicate order, empty catalog).
- Map each miss to a theme (DP / graph / tree / hashing) and pull two cousins from coding questions.
- Spend 15 minutes explaining a catalog → cart → order happy path + one failure out loud.
- Log one STAR story the session reminded you of (ownership, conflicting requirements, performance bug).
Related problems to practice
| Theme you saw in a set | What to drill next | Why Meesho asks it |
|---|---|---|
| Top-K products / sellers | Heaps + hashing | Feed and ranking intuition |
| Inventory updates | Concurrency mental model + locking talk | Oversell prevention |
| Order state machine | Graphs / enums + transitions | Lifecycle correctness |
| Recommendation pairs | Hashing / graphs / DP | Social-commerce relevance |
| Coupon / pricing rules | Greedy + edge cases | Promo correctness |
| Shortest path in warehouse | BFS/Dijkstra | Logistics flavour |
2025 PDFs often drill “dedupe product IDs in window W.” Own the sliding-window + hash template, then drill a related problem for reseller catalogs. That transfers; memorising the story text does not.
From application to offer at Meesho
Meesho hires freshers through campus placement cells (often IITs/NITs/IIITs/BITS and selected private colleges), the careers portal, referrals, and internship conversion. After resume screen, the shape is product e-commerce: timed OA, DSA, system design, managerial fit, then HR.
Application methods
Campus recruitment
Through college placement cells - PPT, then OA and interviews on a batch timeline.
Online applications
Apply on Meesho careers for early-career / fresher tech roles; follow the invite for platform and duration.
Referrals
Employee referrals improve visibility. You still need passing OA code and clear interviews.
1. Resume / eligibility screen
Placement cell or recruiter checks degree, CGPA floor when printed (7.0+ / 70% commonly reported), backlogs, and year of passing. Internships and systems-flavored projects help when volumes are high. This is a gate - OA coding is the hard filter.
2. Online Assessment - 60-90 min
Candidate reports commonly describe 2-3 medium coding problems on HackerRank or similar. No long TCS-style aptitude battery as the main story.
| Component | Typical shape (reported) | Focus |
|---|---|---|
| Coding problems | 2-3 medium | Arrays, strings, trees, graphs, DP |
| Duration | 60-90 min | Full solutions + edge cases |
| Languages | C/C++/Java/Python/JS | Confirm invite list |
| Advance bar (reported) | Often ≥2 fully correct | Optimal complexity preferred |
Student tip: Skim all prompts in 4 minutes. Bank the solvable medium first. Invent two edge cases before submit.
Example timing for a 90-minute OA
| Minute | Move |
|---|---|
| 0-5 | Skim all statements; mark easy wins |
| 5-40 | Fully solve problem 1 with tests |
| 40-75 | Solve problem 2; protect edge cases |
| 75-90 | Attempt problem 3 only if 1-2 are solid; else harden tests |
Candidate chatter often puts OA clear rates around 30-40% - treat that as orientation, not a sealed statistic.
Deeper OA notes: Meesho Online Assessment.
OA sample themes
- Top-K products by score in a stream
- Merge overlapping warehouse time windows
- Detect cycles in supplier dependency graphs
- Coupon stacking with constraints
- Shortest path across fulfillment nodes
TLE on large n is a common reject - always state complexity and watch nested loops.
3. Technical interview 1 - DSA (~45-60 min)
Video shared editor - or, on some campus drives, pen-and-paper group coding (candidates write for ~30 minutes, then explain; only a few advance). Patterns: arrays, trees, graphs, DP, hashing, heaps.
You should:
- Clarify constraints
- Narrate brute force → bottleneck → target complexity
- Code without syntax stalls
- Walk edge cases and complexity
Interviewers care about debugging out loud. Silent staring after a failed mental test case is a common reject signal.
4. Technical interview 2 - System Design + advanced DSA (~45-60 min)
Fresher depth, not staff-architect theater. Typical prompts:
- Design a product catalog / search
- Shopping cart and order management
- Inventory consistency across warehouses
- Recommendation feed for resellers
- Payment / refund basics at e-commerce depth
Start with users → entities → APIs → failure modes. Plain language beats “Kafka + Redis” with no requirements.
Worked mini-outline - order placement:
- Actors: reseller/buyer app, catalog, inventory, pricing, payment, logistics.
- Happy path: reserve stock → price → pay → confirm order → create shipment.
- Failure: payment succeeds but inventory race → compensate / cancel cleanly.
- Consistency: strong vs eventual for stock; say what you can build as a fresher.
- Observability: order IDs, mismatch rates, replay/idempotent callbacks.
Some drives use design-style DSA hybrids (e.g. parking-lot / OOPs modelling) before classic LLD labels - stay flexible.
Worked mini-outline - recommendation feed for resellers:
- Goal: surface products a reseller is likely to list/sell this week.
- Signals: past orders, category affinity, price band, geography, seasonality.
- Pipeline: candidates → score → diversify → cache.
- Failure: cold start for new reseller → popular-in-geo fallback.
- Trade-off: precision vs freshness vs compute cost on cheap devices.
Why Meesho OA feels harder than services coding rounds
Services NLT-style coding often rewards one clean array problem. Meesho OA expects medium thinking under a clock with large inputs. Students who only practised 20-minute Easy problems hit TLE or incomplete second prompts. Train with 45-50 minute medium pairs weekly so the real OA tempo feels familiar.
Also budget emotional energy: shortlist rates in candidate chatter sound harsh after OA. That is normal for product companies. Your control knob is mocks and error logs - not refreshing CutoffBot blogs.
5. Managerial round - ~45 min
Mix of behavioral and light technical. Expect ownership under ambiguity, impact stories, teamwork, and sometimes a follow-up on your Round 2 design. Use STAR. Meesho cares whether you can ship for messy real-world constraints (price-sensitive users, high SKU counts).
6. HR round - ~20-30 min
Why Meesho (social commerce / building for Bharat), Bengaluru logistics, notice/exams, CTC context around ₹25-35 LPA, and joining timelines. Ask one real question about team surface (catalog, logistics, recommendations) - it beats “what is the culture?”
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA (coding) | 60-90 min | Timed DSA correctness |
| 2 | Technical 1 | 45-60 min | Code + narration |
| 3 | Technical 2 | 45-60 min | E-commerce systems + DSA |
| 4 | Managerial | ~45 min | Ownership + fit |
| 5 | HR | 20-30 min | Logistics + motivation |
Some drives merge 4-5. Trust the invite.
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week then OA window |
| OA → shortlist | Often 3-5 days | Competitive pools |
| Interview loop | ~1-2 weeks | Tech 1 → Tech 2 → Managerial → HR |
| Offer / paperwork | 1-2 days after final round common | Written offer wins |
| End to end | ~2-3 weeks | Off-campus can stretch |
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Coding Q1-Q3 | Arrays, trees, graphs, DP | Two timed mediums back-to-back |
| Edge cases | Empty, duplicates, large n | Write tests before submit habit |
| Design follow-ups | Catalog, orders, inventory | Explain one flow in 3 minutes aloud |
| HR | Why Meesho, Bengaluru | Two STAR stories + relocation answer |
Where to practise for Meesho
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
How students actually prep for Meesho
If a Meesho invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Meesho sits around ₹25-35 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Meesho eligibility for freshers 2026 is candidate-reported: often 70% or 7.0+ CGPA across 10th, 12th, and graduation; B.Tech/B.E./M.Tech in CS, IT, ECE or related fields; final-year students and recent graduates; no active backlogs. Strong DSA and e-commerce systems thinking matter more than a marginal CGPA difference once you clear screening. Always verify the campus JD or Meesho careers post.
What you are training for: Meesho fresher SDE loops commonly run: Application / resume screen → Online Assessment (60-90 min, 2-3 medium coding problems on HackerRank or similar) → Technical Round 1 (DSA) → Technical Round 2 (system design / advanced DSA) → Managerial → HR. Total timeline is often 2-3 weeks for campus batches.
Short version of the prep split: Split time roughly: 40% DSA (arrays, trees, graphs, DP), 30% timed coding practice, 20% e-commerce system design, 10% behavioral/STAR and company fit. Aim for 100+ medium problems and weekly OA mocks on HackerRank-style platforms.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Meesho previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Meesho drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Meesho usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Meesho?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Meesho-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Meesho story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Meesho PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Meesho papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Meesho papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Meesho-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed Meesho paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Meesho. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
What to carry into the interview room
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Meesho, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
Tracking that does not become a second job
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Meesho mistakes, you are collecting content, not preparing.
Extra drill block (1)
Sit one more mixed Meesho set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
What Meesho pays freshers (candidate-reported)
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on role, college tier, interview performance, and written components. Meesho does not officially publish these midpoints.
Fresher bands students ask about
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| SDE-1 fresher | ₹25-35 LPA | Primary band for this hub; base often ~₹15-20 LPA + bonus/ESOPs |
| Exceptional / top-college chatter | Sometimes ₹35-45 LPA | Not a guarantee - written offer wins |
| SDE-2 / senior | Higher bands | Outside fresher default |
Confirm base, bonus, ESOP, and benefits on the written offer.
Benefits students actually care about
- ESOPs / equity participation
- Health insurance
- Learning budget / conferences
- Hybrid norms (team-dependent)
- Meal / transport allowances on some teams
Ask HR for the breakup rather than debating Telegram midpoints.
How to talk CTC in HR without sounding lost
Know the ₹25-35 LPA fresher context, ask how the package splits (fixed vs variable vs ESOP), and clarify joining date vs final exams. One calm clarifying question beats aggressive negotiation with no market anchor.
Recent Meesho placement trends
- OA remains the volume filter - 2-3 medium coding problems on HackerRank-style platforms.
- System design emphasis in Round 2 continues - catalog, orders, inventory, recommendations.
- Pen-and-paper / group coding appears in some campus write-ups - be ready to explain code without an IDE.
- Treat ₹25-35 LPA as a reported SDE-1 band, not a promise for every college.
- Most engineering conversations still centre on Bengaluru.
- Internship → FTE conversion remains a useful alternate path when available.
What “building for bharat” means in interviews
When panels push on domain, they want:
- Awareness of price-sensitive users and high SKU diversity
- Trade-offs between consistency and availability for inventory
- Simple explanations over buzzword stacks
- One project story that shows ownership under messy constraints
“I love startups” without a social-commerce angle is a soft signal.
Networking and referral note
Referrals help resume visibility; they do not skip OA. If someone offers a referral, still prepare as if the coding bar is unchanged - because it is. Keep your careers form academics consistent with marksheets; background verification catches typos.
Documents and portal hygiene
- Screenshot the invite’s duration and language list; “my senior’s OA was 120 minutes” is useless without your own mailer.
- If you have internship NDAs, prepare a public version of your project story you can still defend.
- For pen-and-paper rounds, carry a simple template: constraints → approach → complexity → edge cases.
Common questions about Meesho hiring
Process & papers
What is the Meesho placement process for freshers?
Typical SDE path: Application screen → Online Assessment (60-90 min, 2-3 coding problems) → Technical 1 (DSA) → Technical 2 (design/advanced DSA) → Managerial → HR. Timeline often 2-3 weeks for campus batches.
How many interview rounds does Meesho usually have?
Most fresher loops report about five stages (OA + two tech + managerial + HR). Some drives merge later rounds. Count the mailer.
Can I download Meesho placement papers PDF for free?
Yes. Free Meesho placement papers PDF and 2024-2026 style practice sets are on this site - pattern trainers for OA and interviews, not leaked live tests. Start with the 2026 PDF.
What does the Meesho OA look like?
Candidate-reported formats: 2-3 medium coding problems in 60-90 minutes on HackerRank or similar. Focus arrays, trees, graphs, DP. Aim to fully clear at least two with solid complexity.
Eligibility & offer
What eligibility / CGPA do fresher Meesho drives usually expect?
Commonly reported: 7.0+ CGPA / 70% across academics, CS/IT/ECE (related), no active backlogs, final-year or recent grads. Your drive notice overrides this page.
What is Meesho fresher salary in India?
Candidate-reported SDE-1 CTC often lands around ₹25-35 LPA (as of August 2026). Confirm base/bonus/ESOP on the written offer.
Do I have to relocate to Bengaluru?
Most engineering stories are Bengaluru-centred. HR usually checks preference and joining logistics. Be honest early.
Prep & Meesho-specific
How should I prepare for Meesho?
Split time roughly 40% DSA, 30% timed coding, 20% e-commerce design, 10% behavioral. Details: preparation guide.
What languages can I use in the OA?
Typically C, C++, Java, Python, JavaScript. Pick one you can debug live under time pressure.
Meesho vs Flipkart vs Zomato - how should I choose?
Choose by domain and written offer. Meesho = social commerce; Flipkart = large-scale e-commerce; Zomato = hyperlocal food. Compare hubs: Flipkart · Zomato.
Is pen-and-paper coding real at Meesho?
Some GFG campus write-ups describe group pen-and-paper DSA rounds. Formats vary - prepare to explain code without relying on IDE autocomplete.
What design topics should I prioritise?
Product catalog, cart/orders, inventory consistency, recommendations, and basic payment/refund flows at fresher depth.
Any pro tip that actually changes outcomes?
Clear two OA mediums fully before chasing a third hard. Keep an error log. Rehearse one catalog/order design aloud weekly. Make Why Meesho about social commerce constraints, not generic startup energy.
Where can I read real interview experiences?
Start with Meesho interview experience on this site, then cross-check reputable public write-ups. Use them as maps, not scripts.
What branches are eligible?
CS, IT, ECE and related engineering streams appear most often. Strong DSA can help adjacent branches when the JD allows it - read the notice.
What recent candidates reported
Campus SDE-I colour (2025)
During an August 2025 campus SDE-I drive, a candidate on GeeksforGeeks said round two “was on pen and paper”: groups of 6-7 got the same LeetCode medium-hard prompt, wrote code for 30 minutes, then explained it - only 1-2 per group advanced. They noted it was fine to ship a slower O(n² log n) solution if you could also discuss the optimal approach, before a later HackerEarth design-style round (parking lot) that felt more DSA + OOPs than classic LLD.
Takeaways that transfer:
- Be ready to write and explain without IDE comfort.
- Discuss optimality even if your first code is slower.
- Design rounds may look like OOPs modelling, not only “design Instagram.”
- OA still decides who even reaches these rooms.
What selected profiles usually show
Strong medium DSA under time, one project with metrics, a clean inventory/order or systems story, and a Why Meesho answer that mentions social commerce or Bharat-scale constraints. Empty “I love e-commerce” lines get challenged.
After you clear OA - waiting-week plan
- Two timed mediums every other day - protect trees/graphs/DP.
- Rewrite two STAR stories with sharper metrics.
- Sketch catalog → cart → order with one failure mode.
- Practice explaining code on a whiteboard or paper.
- Sleep and Bengaluru logistics answer.
Do not binge 40 new LeetCode tags. Deepen patterns you already miss.
Experience story bank
| Story type | Prompt you should answer | Metric to include |
|---|---|---|
| Ownership | Led a feature end-to-end | Latency / users / bugs fixed |
| Ambiguity | Unclear requirements | How you scoped and delivered |
| Conflict | Disagreement on approach | What changed |
| Failure | Missed a deadline or broke prod/demo | What you changed next time |
| Impact | Helped users or teammates | Before → after number |
If a story has no number, it is not ready for managerial.
Mini OA drill students should rehearse cold
Prompt: Given a stream of product view events, return the Top-K product IDs by view count in the last W minutes.
- Clarify: ties, late events, clock skew, K vs unique products.
- Brute: filter window then sort - too slow for large streams.
- Better: sliding window + hash counts + heap of size K.
- Edges: empty stream, K larger than uniques, duplicate event IDs.
- Say complexity before coding.
Speak the plan in 60 seconds, then code under a timer. That transfer skill matters more than memorising a PDF story.
What hurt other candidates
- Perfect resume with weak OA timing
- Design answers that name Kafka/Redis with no requirements
- STAR stories that stop at “we worked as a team”
- Arguing CTC midpoints from Telegram without a written offer
- Treating pen-and-paper rounds as optional fluff
More narratives: Meesho interview experience.