HR interview questions
Common Blinkit HR questions, sample answer frames, and STAR tips.
Blinkit Interview Experiences
How Blinkit fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
Blinkit placement process includes: 1. Online Assessment (OA) (90 minutes) - 2-3 medium coding problems, 2. Technical Interview Round 1 (45 minutes) - Data structures and algorithms, 3. Technical Interview Round 2 (45 minutes) - System design and detailed technical discussion, 4. Managerial Round (45 minutes) - Behavioral and technical discussion, 5. HR Round (30 minutes) - Final discussion. Total duration: 2-3 weeks from application to offer.
Eligibility (from student reports): 7.0+ CGPA in 10th, 12th, and graduation.
Fresher package ballpark (from student reports): SDE: ₹18-25 LPA. Confirm on your offer letter.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 90 min | 2-3 coding problems |
| Technical Round 1 | 45-60 min | DSA + project discussion |
| Technical Round 2 | 45-60 min | System design (orders / logistics) |
| HR | 20-30 min | Behavioural + culture fit |
Real interview experiences
Section titled “Real interview experiences”Documented on-campus drive: Zomato x Blinkit, SDE-I (2024)
Section titled “Documented on-campus drive: Zomato x Blinkit, SDE-I (2024)”Blinkit hires on campus jointly with Zomato, and this write-up is the most useful fresher-facing account available because the candidate recorded the funnel at every stage.
Online assessment (90 minutes, HackerRank)
- 20 MCQs on core CS subjects - OS, computer networks, DSA, OOPs, DBMS - plus 3 coding problems.
- 18 candidates advanced out of 220.
Round 1 - technical interview
- Project discussion, then a wide sweep: machine learning concepts (RAG pipelines, neural networks, Word2Vec), DevOps (Docker, Kubernetes, Redis), system design (load balancing, consistent hashing), and networking (DNS, TCP vs UDP).
- One DSA problem: Maximal Square.
- The candidate credited using diagrams and sketches to explain answers.
- 8 candidates advanced.
Round 2 - advanced technical interview
- Implementing backend logic in Golang using its concurrency features.
- A system design task: design a rate limiter, with the interviewer pushing on practical implementation and edge cases.
- 3 candidates advanced.
Round 3 - HR
- Motivation for joining, and weaknesses. All three finalists received offers.
Worth noting: this candidate’s profile was projects-heavy (60+ GitHub repositories, a personal DSA log), and Round 1 ranged far outside DSA - ML, DevOps, and networking all came up because they were on the resume.
Documented experienced/referral track: SDE-1 Backend - rejected at system design
Section titled “Documented experienced/referral track: SDE-1 Backend - rejected at system design”A candidate with about six months of internship experience interviewed via employee referral. Three rounds, each eliminatory:
Technical Round 1 (60 minutes) - cleared
- Five modified algorithmic problems. The first was house robber with circular and weighted constraints across three follow-ups; the second was a narrative-framed question that required topological sorting plus graph colouring.
- Also asked why they would pick a given database, and about monitoring tooling (Grafana).
Technical Round 2 (system design) - the elimination
- Asked to design a tracking system for a single user. The interviewer was looking for a file-system-based solution, not a database; the candidate lost significant time working through SQL, NoSQL, and in-memory options.
- Also: debugging Python code, a prefix-string counting problem using tries (where the interviewer indicated a better solution existed), and questions on indexing and sharding, which the candidate estimated they answered 60-70% correctly.
Outcome: rejected, with the gap identified as trade-off reasoning in system design rather than raw problem-solving. Their own stated lessons were to think beyond the tools you already reach for, to understand what the problem actually requires before choosing a solution, and to keep communication clear throughout.
Takeaway: Blinkit’s coding rounds lean on modified standard problems - expect house-robber and grid-DP style questions with constraints bolted on rather than clean LeetCode restatements. Core CS subjects (OS and networking especially) are tested in the OA and again in interviews. And the round that most often ends candidacies is system design, where naming a familiar database is worse than reasoning out loud about what the requirements actually demand.
Sources:
- Zomato x Blinkit Interview Experience for SDE-I, On-Campus 2024 - GeeksforGeeks (student write-up, offer)
- Blinkit Interview Experience for SDE-1 Backend - GeeksforGeeks (candidate write-up, rejected)
- Blinkit Interview Experience for SDE-1 - GeeksforGeeks (candidate write-up)
- Blinkit Interview Experience for SDE Internship - GeeksforGeeks (student write-up)
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Top-K frequent elements. Usually expects heap / bucket sort
- Shortest path in a grid. Usually expects BFS
- Merge overlapping delivery slots. Usually expects interval merge
- Discussion on inventory sync and 10-minute delivery SLA, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why this product?
- Working with unclear requirements
- On-call or weekend comfort
- Relocation
Practical tips for Blinkit
Section titled “Practical tips for Blinkit”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain inventory sync in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of Blinkit panels. Do not skip fundamentals.
- HR answers should be concrete. One story with a result beats five slogans.
- If you do not know something, say so and outline how you would find out.
HR interview
Section titled “HR interview”After technical rounds, Blinkit usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.