BigBasket’s HR round is a 20-30 minute conversation after the technical rounds on communication, relocation to Bangalore, notice period, and whether your motivation fits grocery-scale logistics. The BigBasket HR interview questions that recur are “Are you willing to relocate to Bangalore?”, “Have you used the BigBasket app?” and “A customer received the wrong product, what do you do?”
What BigBasket HR usually tests
After technical clears, HR is often a 20-30 minute conversation on communication, Bangalore relocation (on-site roles are common in campus reports), notice period, and whether your motivation matches grocery-scale logistics. Panels sometimes ask if you have used the BigBasket app - honesty beats pretending familiarity if the service did not reach your city.
Treat the sample answers below as frameworks to adapt, not scripts. Keep timelines and project claims aligned with what you said in technical rounds; HR cross-checks.
What BigBasket HR is scoring
Customer recovery mindset, comfort with operational messiness, Bengaluru commitment, and honesty about shifts for roles that need them.
Common BigBasket HR questions (with sample answers)
1. Tell me about yourself
Framework: Present → Past → Future in 60-90 seconds. Close on why BigBasket engineering today.
Sample answer: “I am a final-year IT student with a 7.2 CGPA. I build full-stack projects - my main one was an inventory tracker with REST APIs, MySQL joins for stock reports, and JWT login. I interned on a small e-commerce module where I fixed a race that oversold the last SKU by moving the decrement into one SQL statement. I am interviewing at BigBasket because I want to work on catalog, slots, and fulfilment problems at real grocery scale, not only demo shops.”
Tips:
- End with grocery/logistics motivation - it matches how tech rounds are framed
- Name the one project your EM round will reopen
2. Why BigBasket?
What they’re looking for: Domain interest and one verifiable product or tech fact - not generic “Tata company” praise alone.
Sample answer: “BigBasket is India’s long-standing online grocery platform, now part of Tata Digital alongside Tata Neu - that means integration work on catalog, loyalty, and delivery at national scale. I am drawn to problems like slot capacity, perishable inventory, and order fulfilment under peak load. My project experience is in stock reservation and API design; BigBasket is where that work maps to customer-facing reliability.”
Facts worth verifying before the interview:
- Majority ownership by Tata Group (Tata Digital) post-2021 acquisition
- Core hubs include Bengaluru; campus HR often confirms relocation there
- Engineering stacks in reports include Java/Python, Django on some off-campus SE-I posts, and modern web (Next.js) on intern loops
Tips:
- Tie to one problem type: inventory, slots, catalog search, or last-mile - pick what you can defend
3. Why should we hire you?
Sample answer: “Three proofs. First, delivery under constraints: I built cart reservation with TTL so abandoned checkouts release stock. Second, debug depth: I traced a JWT expiry bug to clock skew and added refresh handling. Third, teamwork: during a hackathon my teammate and I split OA prep - I owned SQL aggregations while they owned Trie inserts - we both cleared the screen. That maps to shipping reliable grocery features, not only solving isolated LeetCode.”
Tips:
- Inventory, catalog, or order-flow examples land better than generic ‘hard worker’
- Keep under 90 seconds
4. Strengths and weaknesses
Sample answer: “Strength: I explain trade-offs clearly - in my project I chose normalized order tables because refunds and partial picks are common in retail-style flows. Weakness: I used to skip SQL until after DSA grind; I lost time on join questions in a mock OA. I now do two timed SQL drills weekly and can write a top-N-per-category query without looking up syntax.”
Tips:
- Weakness must be real with a visible habit change
- Avoid ‘I work too hard’
5. Where do you see yourself in 5 years?
Sample answer: “In five years I want to own a slice of the catalog or fulfilment stack - the services behind search, availability, or slot booking - and mentor newer engineers on idempotent APIs and data modelling for high-traffic SKUs. I am not optimizing for a title; I am optimizing for depth in grocery-tech systems inside BigBasket or similar scale.”
Tips:
- Show engineering depth, not startup-exit fantasy in year two
6. Tell me about a conflict in a team
Sample answer (STAR): “Situation: my team disagreed on using MongoDB vs Postgres for a fest ticketing app. Task: decide before integration week. Action: I listed access patterns - we needed joins for seat maps and refunds - and we ran a small load test on both. Result: we chose Postgres; reconciliation matched cash collections and we shipped on time.”
Tips:
- Emphasize listening and evidence, not winning the argument
7. Are you willing to relocate to Bangalore / work shifts?
Sample answer: “Yes. Campus SDE reports describe Bangalore on-site roles, and I am prepared to relocate for the team assignment. If I need a short transition window for housing, I will state that upfront - not after the offer. I understand grocery operations can involve peak-hour or weekend load even for engineering, and I am open to discussing shift expectations for the specific team.”
Tips:
- GeeksforGeeks campus write-ups cite relocation as a firm filter - bluffing hurts after offer
- Hyderabad and Mumbai appear in some job posts; confirm against your drive mail
8. Explain a gap / low score / job hop
Sample answer: “I had a semester dip to 6.8 after a family health issue. I retook two courses, kept a consistent project schedule, and my last three semesters are 7.5+. The gap in my internship search was two months while I completed an online backend course and shipped a portfolio API - here is the repo and commit history.”
Tips:
- One sentence own the issue; rest is evidence of recovery
9. What do you know about BigBasket?
Sample answer: “BigBasket operates online grocery and daily essentials delivery across Indian cities, with engineering centered on catalog, warehouse/dark-store logistics, and customer apps. It sits inside Tata Digital’s retail ecosystem, which affects integrations with Tata Neu and shared identity or catalog initiatives. Technically, hiring reports emphasize DSA, SQL, and full-stack project depth rather than whiteboard system-design theatre for most fresher loops.”
Tips:
- Candidate-reported fresher CTC spans roughly ₹9-14 LPA on campus and ₹6-10 LPA on some SE-I bands - treat forums as ranges; trust the written offer letter
- Prepare three facts: business line, one Tata/ecosystem point, one engineering focus
10. Have you used the BigBasket app?
Sample answer (if no): “Not regularly - the service was not available in my hometown during college. I have read about slot booking, subscription baskets, and express delivery tiers. I would learn the product quickly on joining and already think about engineering constraints like perishables and cut-off times.”
Sample answer (if yes): “Yes, for weekly staples. I noticed slot selection and substitution flows when items are out of stock - that made me curious how availability is synced from dark stores to the app.”
Tips:
- A reported selected candidate answered ‘no’ honestly and still cleared - willingness to learn matters
11. Walk through a feature you’d build for grocery delivery
Sample answer (outline): “I would sketch slot booking: customers pick a delivery window; the service checks dark-store capacity and route density, reserves a slot idempotently at checkout, and releases it if payment fails. Data: slots table keyed by store and time band; Redis or DB row locks for hot slots; async notification on slot changes. I would call out failure modes - double booking, stale inventory - and how idempotency keys on order POST prevent duplicates.”
Tips:
- Keep it conversational; HR sometimes uses this as a lightweight design check after tech rounds
12. Do you have any questions for us?
Sample answer questions:
- “What does the first 90 days look like for a fresher on your team - onboarding vs production fixes?”
- “How are catalog and inventory services split between teams post Tata Neu integration?”
- “What does on-call or incident rotation look like for customer-facing APIs?”
Tips:
- Avoid leading with CTC or WFH
- Culture and WLB questions are fine if sincere - they appear in public campus reports
Real examples to prepare before BigBasket HR
11. A customer received the wrong product - what do you do?
Framework: Empathy → verify order → resolution path (replace/refund) → prevent via process note. Sample direction: “I would apologize, verify the SKU and slot, arrange the fastest replacement or refund per policy, and flag the pick-pack mismatch so the dark store can fix the root cause - not only soothe the chat.”