Academic snapshot
Marks: 7.0+ CGPA / 70% throughout (candidate-reported)
Degree: B.Tech / B.E. / M.Tech
Backlogs: None active
Year: Final-year and recent grads (~2 years)
Blinkit Placement Papers 2026
Blinkit is Eternal Limited’s quick commerce brand delivering groceries in minutes across Indian cities, formerly known as Grofers. Engineering teams within Eternal’s consumer tech stack build ordering, logistics, and fulfillment systems that power Blinkit and related products.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Blinkit fresher eligibility for campus drives
Blinkit SDE hiring is a product + logistics loop. The printed floor is often 7.0 / 70%. Two passing OA solutions still decide the shortlist. Read whether the PPT says Blinkit, Zomato, or Eternal.
Who this hub is for
- For: Students targeting SDE / backend / full-stack roles on order, inventory, rider, or app teams.
- Not the same track: Dark-store ops, rider-ops, or pure sales. Those bars do not map to this OA → DSA → design loop.
- Experienced hires: Mid-level loops add deeper service design and different CTC.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, college CGPA list when printed | Coding bar, interview depth |
| Careers / LinkedIn | Branding may say Eternal or Zomato | Still expect OA + two tech rounds |
| Referral | Faster visibility | You still need passing OA code |
Degree, projects, and “is 7.0 enough?”
Is 7.0 CGPA enough? It matches the commonly reported floor. A 7.1 with clean timed coding beats an 8.5 that cannot explain a sliding-window order batch. Stronger CGPA (8.0+) helps resume screens; it does not replace OA.
Branches: CS/IT dominate. Related streams show up when DSA is solid.
Gaps and backlogs: Active backlogs are a hard blocker. Recent grads within about 2 years appear on many posts.
What helps: One project with a latency or inventory metric, any internship with ownership. See certifications after fundamentals.
Branch & skills
Preferred: CS / IT and related
Languages: Python, Java, JavaScript, C++, C
Focus: DSA, quick-commerce design lite
Differentiator: 10-minute SLA + dark-store sketches
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.0+ / ~70% across 10th, 12th, graduation | Verify every drive |
| Degree | B.Tech / B.E. / M.Tech | Related computing degrees on many posts |
| Branch | CS, IT | Strong DSA can help adjacent branches |
| Year | Final year + recent grads (~2 years) | Intern conversion also appears |
| Backlogs | No active backlogs | Clear them before paperwork |
| Employer name | Blinkit / Zomato / Eternal | Read the letter |
| Coding languages | Python, Java, JS, C++, C | Stick to one |
Blinkit CGPA criteria
The minimum CGPA required is commonly 7.0+ CGPA / 70% throughout. Treat it as a shortlisting filter when printed.
| Academic Level | Minimum (typical) | Notes |
|---|---|---|
| 10th | 7.0+ / 70% | When the JD lists all three |
| 12th | 7.0+ / 70% | Diploma holders: follow JD |
| Graduation | 7.0+ / 70% | No active backlogs |
| Backlogs | None active | Cleared backlogs generally accepted |
Blinkit placement papers - last few years
Download 2026 Blinkit placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What these papers train for aptitude and coding filters
Blinkit does not publish one permanent official paper set. Papers on this site are pattern trainers. A “Blinkit aptitude test questions PDF” is offline practice for the same skills: mostly direct coding, sometimes a short MCQ block.
| Round (typical) | What to practice |
|---|---|
| Online assessment | 2-3 medium DSA in 90 min; aptitude if named |
| Technical 1 | Live coding narration + edge cases |
| Technical 2 | 10-minute delivery / inventory design lite |
| Managerial | Impact, ops awareness, teamwork |
| HR | Why Blinkit, city, CTC band |
Themes that keep repeating (2024-2026)
- 2024 cycles: 90-minute coding OA. Sliding windows on timestamps, array batching, and graph-ish routing intuition show up in practice sets.
- 2025 loops: Same coding-heavy first filter. Tech 2 leans dark stores, SLAs, stock-outs. Parent-brand confusion (Zomato/Eternal) shows up in student groups.
- 2026 prep expectation: Keep two complete OA solutions warm. If the invite mentions aptitude, add percentages and one DI table. Treat PDF packs as pattern catalogs.
How to use one paper set in a single sitting
- Timed: 90-minute mock (2-3 coding; add 15 aptitude items if your invite has MCQs).
- Untimed review: rewrite the cleaner solution; list three edge cases.
- Map each miss to a theme and pull two cousins from coding questions.
- Spend 15 minutes explaining 10-minute delivery out loud.
- Log one STAR story (peak hour, stock-out, unclear requirement).
Sample practice flavors (not leaked live items)
- Quant: Rider 12 km at 24 km/h, return at 36 km/h → harmonic mean 28.8 km/h.
- Logic: Dark-store slots A-E, no two adjacent same category; A = Grocery, C = Electronics → B can only be Personal Care.
- Coding flavor: Order timestamps + window W → max orders in any contiguous W (sort + two pointers).
- DI-lite: Hourly orders 40, 55, 70, 65, 90 → peak vs average of others ≈ 56.5% higher.
Related problems to practice
| Theme you saw in a set | What to drill next | Why Blinkit asks it |
|---|---|---|
| Sliding window / timestamps | At-most-K, variable window | Order batching, peak load |
| Arrays / hashing | Frequency, grouping | SKU counts, dark-store slots |
| Graphs / BFS | Shortest path lite | Rider / delivery intuition |
| Greedy interval | Merge, overlap | Slotting, batch windows |
| Aptitude (if present) | Percentages, averages, DI | Campus mixed papers |
Using Blinkit papers to train quick-commerce loops
Week-by-week calendars live on the preparation guide. This section is the focus split so you do not study like you are sitting TCS NQT and a staff-level logistics thesis on the same night.
Time split that matches the filter
| Bucket | Share | What “done” looks like |
|---|---|---|
| Timed DSA / OA | ~45% | Two of three mediums fully passing in 90 minutes |
| Design lite | ~25% | 90-second 10-minute delivery + stock-out story |
| Aptitude (if invite has it) | ~10-20% | Percentages, averages, one DI table |
| Project + HR | ~10-20% | Metric + Why Blinkit + city answer |
If your invite is coding-only, fold aptitude time back into DSA. If it names MCQs, do not skip them.
This week, not “someday”
- One full timed mock from coding questions plus online assessment.
- Two medium problems submitted end-to-end in Python or Java.
- Speak a dark-store + rider sketch once without notes.
- Record “Why Blinkit” once naming SLA and inventory, not “10-minute is cool.” Record again.
- Error log: three DSA misses, one design blank, one aptitude type if relevant.
What not to waste time on
- Ignoring the employer name (Blinkit vs Eternal vs Zomato food)
- Memorising PDF samples as if they will repeat
- Starting a second language the week of the OA
- Staff-level Kafka diagrams for a fresher cabin
- Skipping aptitude when the mailer listed it
Dark-store sketch students should rehearse
One order, one dark store, 10-minute SLA:
- Actors: customer, inventory, picker, rider, order service.
- Happy path: reserve SKUs → pick path → hand to rider → GPS to door.
- Stock-out: substitute with consent or cancel that line; never silent drop.
- Peak: if pick queue blows the SLA, say so in the app; do not promise 10 minutes you cannot hit.
- Scale later: only after the above is clear. Do not lead with “we will use Kafka for every SKU event.”
Aptitude only when the invite names it
A printable PDF is useful. A live SDE drive is often coding-only. If the mailer is silent on MCQs, spend the hour on another timed medium, not on more percentages. If the mailer lists quant/logic, treat empty aptitude as a sectional fail even with two passing programs.
Offer-stage discipline
- Read employer legal name (Blinkit vs Eternal vs Zomato)
- Read city and hybrid/shift language
- 10th/12th/degree % must match
- Verbal classroom “selected” is not an offer PDF
- Do not quote a Zomato food-tech blog CTC on a Blinkit letter, or the reverse
Blinkit hiring rounds in 2026
Blinkit/Eternal hires freshers through campus cells, careers pages, and referrals. After resume screen, the shape is product-company: timed OA, two technicals (second is design-heavy), managerial, HR.
Application methods
Campus placement
Through college placement cells. Confirm the employer name on the PPT.
Direct application
Careers page or LinkedIn. Follow the invite for platform and duration.
Referrals
Employee referrals improve visibility. You still need passing OA code.
1. Resume / eligibility screen
Recruiter checks degree, 7.0+ / 70% when printed, backlogs, and year of passing. This is a gate. Coding is the hard filter.
2. Online Assessment (~90 min)
Candidate reports commonly describe a 90-minute assessment with 2-3 medium coding problems. Some campus notices add a short aptitude/MCQ block.
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Coding | 2-3 problems | Most of 90 min | Arrays, strings, DP, graphs |
| Aptitude (if present) | Short MCQ set | Shared / prior block | Quant, logic, DI-lite |
Platforms: HackerRank or similar. Languages: Python, Java, JavaScript, C++, C. Pass habit: at least 2 correct, near-optimal solutions. Roughly 30% clearing OA is a common rumour, not a promise.
Student tip: Read constraints first. Bank the solvable two. If aptitude is present, do not leave it for “after coding” and run out of time.
Deeper OA notes: Blinkit online assessment.
3. Technical interview 1 (~45 min)
Virtual or onsite. 2-3 coding problems, approach, complexity, communication.
4. Technical interview 2 (~45 min)
Quick-commerce design plus project deep dive.
Worked mini-outline - 10-minute delivery:
- Actors: customer, dark store, picker, rider, order service.
- SLA: accept → pick → dispatch → drop inside the window.
- Stock-out: substitute or cancel with a clear message; do not silently drop.
- Peak: queue pickers; do not promise 10 minutes if the store is overloaded.
- Scale later: only after the above is clear.
5. Managerial (~45 min)
Impact, teamwork, how you debug under time. They may probe whether you understand ops without pretending you want to be a rider.
6. HR (~30 min)
Why Blinkit, Gurgaon or city, joining date, CTC. Know the ₹18-25 LPA SDE band.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA | ~90 min | Timed accuracy |
| 2 | Technical 1 | ~45 min | Code + narration |
| 3 | Technical 2 | ~45 min | Logistics design lite |
| 4 | Managerial | ~45 min | Impact, fit |
| 5 | HR | ~30 min | Logistics, integrity |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | Confirm employer brand |
| OA → shortlist | A few days common | Trust the invite |
| Interview loop | ~1 week | Tech 1 → Tech 2 → Managerial → HR |
| Offer / paperwork | 1-2 days after final | Written offer wins over verbal |
| End to end | ~2-3 weeks campus often | Off-campus can stretch |
How Blinkit differs from a generic food-delivery interview
- Minutes and dark stores, not 30-minute restaurant delivery only.
- Inventory and stock-outs show up as much as routing.
- Parent-brand naming can confuse CTC comparisons with Zomato food tech.
OA skip rules that save the 90-minute paper
- Skim all 2-3 prompts in 4 minutes. Mark the one you can finish.
- Bank a complete passing solution before opening a hard graph.
- If aptitude is on the paper, do not leave it for the last 3 minutes.
- Sliding-window timestamp problems: sort first, then two pointers.
- Last 8 minutes: re-run tests, not a new algorithm.
Log every mock: which pattern ate the clock (windows vs graphs vs leftover MCQs). That log is the prep plan.
Weekend mock that matches a real loop
Saturday 10:00: 90-minute OA (2-3 mediums; two must fully pass). Add 15 aptitude items if your invite has MCQs.
Saturday 12:00: review misses into an error log.
Saturday 16:00: speak 10-minute delivery + stock-out, 90 seconds each, no notes.
Sunday 11:00: 45-minute live coding with a friend or a timer.
Sunday 12:00: Why Blinkit + city answer, recorded once. Name the employer brand you applied under.
Two weekends of that beat twelve nights of random quick-commerce YouTube. If the PPT says Eternal or Zomato, still run this mock; swap the HR story to match the brand.
Documents pack
Resume one page, 10th/12th/degree scans matching the 7.0 story, ID. Name and percentages must match the form. Keep a note of whether you applied as Blinkit, Zomato, or Eternal so HR answers stay consistent.
Night-before checklist
- Charger, ID, resume PDF
- One language chosen
- Two STAR stories and the delivery sketch already spoken once today
- Sleep. A 9 a.m. OA after a 3 a.m. mock is how easy array items go wrong
- Confirm employer name on the invite so you do not say the wrong brand
Blinkit practice pages
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.
What to practise before a Blinkit drive
If a Blinkit 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 Blinkit sits around ₹18-25 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): Candidate-reported campus floor is often 70% or 7.0+ CGPA across 10th, 12th, and graduation; B.Tech/B.E./M.Tech in CS, IT or related fields; final-year or recent grads (within about 2 years); no active backlogs. Confirm whether the posting is Blinkit, Zomato, or Eternal. Always verify the notice.
What you are training for: Typical SDE loop: Online Assessment (~90 min, 2-3 medium coding, sometimes a short aptitude block) → Technical 1 (~45 min) → Technical 2 (~45 min, quick-commerce design) → Managerial (~45 min) → HR (~30 min). Campus batches often finish in about 2-3 weeks.
Short version of the prep split: Split time roughly 45% DSA, 25% 10-minute delivery / inventory / dark-store design lite, 20% timed OA (plus aptitude if your invite has MCQs), 10% project + Why Blinkit. Languages: Python, Java, JavaScript, C++. Full week plan: /blinkit/preparation-guide/.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Blinkit 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 Blinkit 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 Blinkit 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 Blinkit?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. 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 Blinkit-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 Blinkit story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Blinkit 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 Blinkit 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 Blinkit papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Blinkit-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 Blinkit 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 Blinkit. 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.
Blinkit compensation & benefits
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on SDE vs backend vs full-stack, employer brand, location, and written components.
| Track | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| SDE (fresher) | ₹18-25 LPA | Primary band for this hub |
| Backend (0-1 yr notes) | ₹20-28 LPA | Same loop family |
| Frontend (0-1 yr notes) | ₹18-24 LPA | JS-heavy |
| Full stack (0-2 yr notes) | ₹22-30 LPA | Not every campus letter |
Confirm base vs variable and the employer legal name on the written offer.
Benefits students actually care about
Health cover, PF on the usual India pattern, learning after joining (manager-dependent), and city/hybrid language. Ops-heavy teams may talk shifts. Ask; do not assume startup WFH.
How to talk CTC in HR
Know ₹18-25 LPA SDE. Do not quote a Zomato food-tech blog number if your letter says Blinkit, or the reverse. One calm split question beats a screenshot war.
Backend and full-stack notes in the ₹20-30 LPA pocket are not a promise that your campus SDE letter will match. Ask base vs variable, joining city, and whether the legal employer is Blinkit, Eternal, or Zomato. That last question avoids a surprise bond or transfer clause copied from a different brand’s blog.
Rider-assignment sketch (fresher depth)
Order ready at the dark store:
- Actors: picker, rider pool, dispatch, customer.
- Rule: nearest available rider who can still hit the remaining SLA.
- Conflict: two orders, one rider: batch only if both still make the window.
- Failure: no rider → tell the customer; do not keep a spinning “arriving in 2 minutes.”
- Scale later: only after the above is clear.
Pair this with the dark-store sketch. Interviewers often ask both: stock then dispatch.
Recent Blinkit placement trends
Brand on the letter
Eternal / Zomato / Blinkit still get mixed in student groups. Read the employer line.
Coding-first OA
90-minute 2-3 problem papers remain the volume filter. Aptitude appears on some campus invites only.
Dark-store design
Tech 2 still rewards SLA + stock-out stories over generic URL shorteners.
Gurgaon hub story
HQ narrative stays NCR. Confirm city on the letter before you quote WFH.
Net for 2026: do not wait for Blinkit to become an aptitude-only company. Double down on timed DSA and one 10-minute-delivery sketch. Add MCQs only when the invite names them. Keep a Swiggy Instamart or Flipkart grocery-adjacent story warm so you are not stuck if the PPT says Eternal this year and Blinkit next year. The SLA sketch still transfers. After OA, redraw stock-out and rider-assign once, then sleep. Do not open a new graph pattern the night before Technical 1. If aptitude was on your paper, log the three MCQ types you slow on so the next mixed invite is not a surprise. Keep the same coding language for Tech 1. Switching to JavaScript the night before a Python OA is how easy array items fail on syntax.
FAQs students ask about Blinkit placements
Papers & process
Can I download Blinkit placement papers PDF for free?
Yes. Free Blinkit placement papers PDF and 2024-2026 style practice are on this site. Start with the 2026 PDF or the archive.
What is the Blinkit placement process for freshers?
Typical SDE path: Online Assessment (~90 min) → Technical 1 → Technical 2 (design) → Managerial → HR. Campus batches often finish in about 2-3 weeks.
How many interview rounds does Blinkit usually have?
Most fresher loops report five stages. Some invites merge rounds. Count the mailer.
What does the Blinkit Online Assessment look like?
Often 90 minutes with 2-3 medium coding problems. Some campus notices add a short aptitude block. Details: online assessment.
Eligibility & offer
What eligibility / CGPA do fresher SDE drives usually expect?
Commonly reported floor: 7.0+ CGPA / 70% across 10th, 12th, and graduation; CS/IT-related degrees; final-year or recent grads (~2 years); no active backlogs. Your notice overrides this page.
What is Blinkit fresher salary in India?
Candidate-reported SDE CTC often lands around ₹18-25 LPA (as of August 2026). Backend/full-stack notes can sit higher. The written offer is the only number that matters.
Is Blinkit the same as Zomato or Eternal?
Blinkit is Eternal’s (formerly Zomato) quick-commerce brand. Posts may use any of the three names. Read the employer line on the offer.
Prep & Blinkit-specific
How should I prepare for Blinkit?
Split time roughly 45% DSA, 25% delivery/inventory design lite, 20% timed OA (plus aptitude if named), 10% project/HR. Details: preparation guide.
Which programming languages are allowed?
Python, Java, JavaScript, C++, and C are the usual set. Confirm on the invite. Do not switch the week of the OA.
What product topics should I revise?
10-minute delivery, dark-store inventory, order batching, rider assignment, and peak-hour load at fresher depth: actors, SLAs, stock-outs.
Blinkit vs Swiggy vs Zomato for freshers?
All three care about DSA. Blinkit is minutes + dark stores. Swiggy has food plus Instamart. Zomato/Eternal may be the parent name on the letter. Share DSA; customise SLA stories.
Any pro tip that actually changes outcomes?
Confirm the employer name. Bank two fully passing OA solutions. Rehearse one 10-minute-delivery sketch. If aptitude is on the invite, do not skip it.
Where can I read real interview experiences?
Start with Blinkit interview experience on this site.
Will I have to relocate?
Gurgaon/NCR is the usual HQ story. HR checks city and hybrid. Answer honestly.
Is the first round an aptitude test or a coding OA?
Most SDE drives are a direct coding assessment (90 min, 2-3 mediums). Some campus notices add a short quant/logic block. Read the invite. Use the PDF and mock quiz if MCQs are named.
Do I need to solve all three OA problems?
The habit students repeat is two correct, near-optimal solutions. Leaving an easy array incomplete to chase a hard graph is a common reject. Confirm the bar on your mailer.
Blinkit - recent candidate experiences
Fresher SDE loops (2024-2025)
Profile patterns that got selected: B.Tech CSE/IT, roughly 7.0-8.5 CGPA, one internship or a strong backend project, steady DSA rather than last-week panic.
Online assessment: Timed coding on HackerRank or similar. Clean, fully passing solutions beat partial cleverness. Students who also faced a short aptitude block lost marks by saving MCQs for the last three minutes.
Technical rounds: Arrays, sliding windows on timestamps, hashing, graphs. Domain chat around 10-minute SLA, dark-store stock, and rider assignment. Project deep dive: hardest production-ish bug, what you would rebuild at order scale.
Managerial / HR: Why Blinkit? A time you shipped under a deadline? City comfort? Keep answers short: situation → what you did → result.
What hurt: coding before reading constraints; Kafka-first design with no SLA; mixing Zomato food CTC into a Blinkit HR; skipping aptitude when it was on the paper.
Story-shaped notes
Story 1 - Selected (CSE ~8.0): OA with two passing mediums → Tech 1 sliding window on order times → Tech 2 stock-out path in plain English → HR Why Blinkit with a metric from a college inventory project.
Story 2 - Brand confusion (IT ~7.3): Prepared a Zomato restaurant-search story for a Blinkit-branded loop. Interviewer asked dark-store picking. Takeaway: match the brand on the PPT.
After you clear OA
- Re-solve every miss from your last two mocks cold.
- Speak two STAR stories without notes.
- Sketch 10-minute delivery and a stock-out on a blank doc.
- Warm one array/window medium in your interview language.
- Sleep and Gurgaon logistics. Do not open a new advanced topic.
What quick-commerce volume means for your odds
A Blinkit/Eternal campus can still take a batch, but it is not TCS-scale. Aptitude (when present) still deletes a chunk. Easy coding still deletes people who never compile. Design still deletes people who only practised URL shorteners. Your job is to be easy to say yes to: two passing OA solutions, one SLA sketch, a project sentence with a metric, documents ready.
Keep a Swiggy or Flipkart loop warm until the offer PDF lands. Compare employer name, city, and joining date, not only the ₹18-25 LPA midpoint.
More fresher narratives: Blinkit interview experience.
Similar companies
Zomato · Swiggy · Flipkart · Paytm · Phonepe · Urban Company