Bigbasket.com Engineering Manager Interview: Questions, Experience & Prep (2026)

Bigbasket.com is India's largest online grocery platform, operating both scheduled delivery and quick-commerce (BB Now) across major cities. Engineering Managers here typically lead teams working on supply chain tech, catalogue systems, last-mile logistics, mobile apps, and data infrastructure.

As of July 2026, knok jobradar tracks 4 open Engineering Manager roles at Bigbasket, within a national market of 975 Engineering Manager openings. Bangalore leads with 182 of those roles, followed by Delhi (53), Pune (20), Chennai (20), Hyderabad (16), and Mumbai (12).

Knok jobradar market data shows these typical salary bands for the Engineering Manager track:

The interview process candidates report typically involves an HR screening call, a technical or system design round, a people management and behavioural round, and a final leadership panel. The exact sequence can vary by team and hiring manager, so go in prepared for all of these.

These questions draw on what candidates report and on Bigbasket's publicly known engineering priorities around scale, quick-commerce, and last-mile logistics.

1. Bigbasket runs both scheduled grocery delivery and BB Now quick-commerce. How do you align your team's priorities when the two products have very different SLAs and constraints?
2. Describe a time your team had to scale a backend service rapidly, for example during a festive season sale. What was your role and what did you change?
3. How do you balance shipping new features quickly against paying down growing technical debt in a fast-moving e-commerce environment?
4. Walk us through how you built or significantly restructured an engineering team. What gaps did you identify, and what did you change?
5. How do you handle a situation where a product manager and your engineers strongly disagree on the right technical approach?
6. Bigbasket's platform depends on operations, supply chain, and vendor systems. How do you ensure your team ships reliably when your work is tightly coupled to other squads?
7. Tell us about a critical production incident you personally owned. How did you coordinate the response and communicate with stakeholders?
8. How do you measure the health and performance of your engineering team? What signals matter most to you?
9. Bigbasket competes with Zepto, Blinkit, and others in a fast-moving space. How do you keep your team motivated and shipping consistently under competitive pressure?
10. How have you handled an underperforming engineer? Walk us through the steps you took and how the situation resolved.
11. What is your hiring philosophy? How do you evaluate both technical depth and how someone will contribute to team culture?
12. How do you think about on-call culture and platform reliability when downtime directly affects delivery SLAs and customer trust?

Use the STAR method for every behavioural question: Situation, Task, Action, Result. At the manager level, spend most of your time on Action. Aim for roughly two minutes per answer when speaking aloud.

Q: Tell us about a critical production incident you personally owned.

*Situation:* At my previous company, our order management service failed during a peak sale event. Customers were seeing payment errors and orders were not being placed.

*Task:* I was the Engineering Manager on call. My job was to coordinate the technical response, keep leadership informed, and make sure the team did not freeze under pressure.

*Action:* I set up a virtual war room immediately, assigned one engineer as the primary investigator, and asked others to check dependent services in parallel. I sent a brief, factual status update to the VP every few minutes so leadership was never left guessing. We found that a third-party vendor SDK had a silent failure mode we had not tested for. I made the call to roll back to the previous stable build while the fix was being prepared, rather than attempting a patch in production under pressure.

*Result:* The service was restored within the same session. We ran a blameless post-mortem, added the vendor failure scenario to our integration test suite, and shared the learnings with adjacent teams. Leadership later used our communication cadence as a reference model for future incident responses.

---

Q: How have you scaled an engineering team from scratch?

*Situation:* I joined a startup as its first Engineering Manager when the product had strong growth but no engineering structure to support it.

*Task:* My goal was to scale the team in a way that preserved the speed of a small group while adding the reliability a growing user base demanded.

*Action:* I started with one-on-ones and code reviews to map the team's actual strengths and gaps. I introduced lightweight sprint rituals, not heavy processes, just enough to give visibility. I wrote honest job descriptions that attracted engineers who wanted ownership rather than ticket-takers. I also set up an on-call rotation so incidents stopped falling on the same two or three people every time.

*Result:* The team grew steadily over the following quarters, attrition stayed low, and we shipped a core platform rewrite without missing any customer commitments. Two engineers from that cohort have since moved into senior technical roles.

---

Q: How do you handle a conflict between product and engineering?

*Situation:* A product manager wanted to add a new feature in the same sprint as a major infrastructure migration my team had already committed to.

*Task:* I needed to protect my team's capacity without damaging the relationship with the PM or leaving an important customer need unaddressed.

*Action:* I asked the PM to walk me through the business reason for the urgency. It turned out a key account had flagged the feature gap as a blocker. I shared the engineering risk of splitting the team's focus, with concrete examples of quality issues from a similar situation in the past. We agreed on a phased approach: a lightweight version of the feature to address the account's immediate need, followed by the full implementation once the migration was complete.

*Result:* The account was retained, the migration shipped cleanly, and the PM later told me that the structured conversation helped her set stakeholder expectations much more confidently going forward.

The STAR method is the most reliable structure for behavioural questions. At the manager level, interviewers want to hear your reasoning, not just what happened. State the context briefly, spend most of your time on Action, and always close with a concrete Result, even if the outcome required a course-correction.

For system design questions, use a top-down approach: clarify the problem and constraints first, sketch the high-level components, then drill into the parts the interviewer cares about most. At Bigbasket, bring in grocery-specific constraints: perishable inventory, delivery slot availability, vendor SLA variability, and last-mile logistics. Designs that ignore these constraints miss the point of the question.

For people management scenarios, describe your decision-making process in detail. Bigbasket interviewers typically want to understand how you weigh individual needs against team outcomes. Avoid vague phrases like 'I had a conversation.' Describe what you said, what you listened for, and how you adjusted your approach.

For cross-functional conflict, the 'align on outcomes, not positions' frame works well. Show that you seek to understand the other party's constraints before defending your own.

Candidates who have gone through Bigbasket's engineering leadership process report a few consistent themes that interviewers focus on.

Ownership under pressure. Bigbasket's logistics-heavy business means outages have direct revenue and customer impact. Interviewers want to see that you stay calm, communicate clearly, and make decisions without waiting for permission.

Pragmatic technical depth. You are not expected to write code in the interview, but you must engage seriously with system design and architecture trade-offs. Familiarity with how quick-commerce platforms handle inventory consistency, slot management, and delivery routing is a strong signal.

People-first thinking. Bigbasket has scaled fast in a competitive talent market. Interviewers look for managers who can attract, grow, and retain engineers, not just close sprint goals.

Cross-functional comfort. Engineering at Bigbasket is tightly coupled with operations, supply chain, and product. Candidates who demonstrate experience navigating these dependencies earn strong signals.

Data-informed decisions. Whether the question is about team health or system reliability, grounding your answers in specific signals and metrics is valued over gut-feel reasoning.

Step 1: Understand Bigbasket's product landscape. Spend time using the app across both the scheduled delivery and BB Now flows. Notice where you see engineering trade-offs reflected in the user experience, from load times to slot availability to inventory accuracy.

Step 2: Prepare your incident story. Every EM candidate at a platform company needs a strong incident response story. Structure it using STAR and make sure you can speak clearly to your specific decisions, not just what the team collectively did.

Step 3: Practise system design for e-commerce scale. Work through scenarios like an order management service, a real-time inventory reservation system, or a delivery slot allocation engine. Focus on trade-offs relevant to grocery: consistency vs. availability, freshness constraints, and logistics integration with external vendors.

Step 4: Prepare people management stories. Have clear STAR examples ready for: handling an underperformer, building a team from scratch, resolving a product-engineering conflict, and helping an engineer grow into a senior role.

Step 5: Research the team and the company. Read Bigbasket's engineering blog, watch public tech talks from their engineers, and look for interviews or articles from their engineering leaders. This gives you language and context that interviewers notice.

Step 6: Practise out loud. Answers that flow well in your head often fall apart when spoken. Do at least two mock interviews before the real one, ideally with someone who can give honest feedback.

Saying 'we' when you mean 'I'. Interview questions ask what you did. Many EM candidates answer in the plural out of habit or humility. Interviewers need to hear your specific decisions and contributions, not the team's collective output.

Dropping the Result. STAR answers that end at Action leave the interviewer without closure. Always close with what happened: whether things improved, what changed concretely, or even that the approach did not fully work and what you adjusted afterward.

Being vague about people management. Saying 'I gave feedback and things improved' is not enough. Walk through what you said, how the person responded, and what changed over weeks or months.

Treating system design as purely technical. Bigbasket's engineering questions typically have an ops or business constraint baked in. Design a slot booking engine without accounting for last-mile variability or vendor SLA failures, and you will miss what the interviewer was listening for.

Under-preparing the 'why Bigbasket' question. Saying 'it's a great company' is a red flag at this level. Show genuine curiosity about the quick-commerce engineering challenge and the specific scale problems Bigbasket is solving.

Overloading answers with jargon. Speaking plainly and precisely signals confidence. Hiding behind industry buzzwords signals the opposite.