Blinkit hub
Blinkit Online Assessment
Overview
Blinkit online assessment (OA) is the first hard filter for many fresher and lateral engineering drives. This page covers format, sample Blinkit OA questions, an 8-week prep plan, and mistakes that sink strong candidates.
Patterns are from student reports for 2025-2026. Confirm your invite.
Blinkit hiring flow after the OA
| Stage | What candidates report | What you must show |
|---|---|---|
| 1. Online assessment | Timed DSA OA | Correctness + reasonable complexity |
| 2. Technical interviews | DSA + projects + delivery scenarios | Explain approach and edge cases |
| 3. Later rounds | HM / HR | Depth + communication |
| 4. HR / offer | Role, location, CTC | Consistency with resume |
Blinkit Online Assessment format
| Component | From student reports details |
|---|---|
| Platform | HackerRank / similar |
| Duration | About 90-120 minutes |
| Question mix | 2-3 DSA problems |
| Languages | Java, C++, Python |
| Scoring | Automated tests |
| Advance rate | Competitive |
What makes Blinkit OA feel distinct
- Quick-commerce flavor: ETA, batching, geo/grid
- Standard DSA underneath
- Speed + correctness both matter
- Operations product sense appears more in interviews than OA
Question types
Core
- Heaps, BFS on grids
- Intervals / sweep line
- Hashing on event streams
- Greedy batching
Secondary
- Distance metrics (Manhattan vs Euclidean)
- Latency/availability trade-talk in interviews
Usually not in OA
- Full OR-Tools routing exams
- Long verbal essays
Sample Blinkit Online Assessment questions
Question 1: nearest dark store assignment
Question 2: max overlapping delivery slots
Question 3: eta heap updates
Question 4: batch orders within k minutes
Question 5: grid blocked roads BFS
Question 6: top-k busy zones
8-Week prep plan
| Weeks | Focus | Exit criteria |
|---|---|---|
| 1-2 | Arrays, hashing, two pointers | 40+ clean easy/medium |
| 3-4 | Trees/graphs/heaps as relevant | Implement BFS/DFS cold |
| 5-6 | Domain-flavored drills for Blinkit | Timed section comfort |
| 7 | Full mocks at OA duration | Finish required problems with tests |
| 8 | Weak-topic repair | Re-solve misses in 48 hours |
Daily loop
- One timed medium problem
- Write complexity + 3 edge cases before coding
- Log misses by pattern
- Weekly full mock
Common mistakes
- Wrong distance assumptions
- Priority-queue comparator bugs
- No sweep-line practice for overlap problems
- Ignoring constraints
- Cannot explain OA code later
Day-of checklist
- Skim all problems for 3-4 minutes and order by familiarity
- Submit a correct simpler solution before over-optimizing if time is tight
- Invent edge cases the samples omit
- Do not leave a problem fully blank if a partial tested approach can score
- After the test, write down every problem from memory for interview prep
Interview transition plan (48 hours after OA)
- Re-solve your OA problems cleanly
- Prepare STAR stories (ownership, conflict, failure, impact)
- Revise OOPs, DBMS, OS one-pagers
- Rehearse a 2-minute project narration