BigBasket SDE and intern loops reward solid medium DSA plus honest full-stack project depth. Notes below are from public GeeksforGeeks and LinkedIn candidate reports.
Longer calendar (weeks between OA and HR) vs compressed campus days
Stack emphasis: Python/Django, REST, Git, MySQL/Postgres in multiple SE-I postings
OA still mixes medium DSA with SQL; project defence remains the differentiator in later rounds
Location questions may include Bengaluru, Hyderabad, Mumbai depending on req
Key takeaways: Match prep to the posting stack - Django roles will ask framework specifics, not only arrays.
Sample answers for high-frequency questions
Technical
Q. SQL vs NoSQL / why MongoDB? A. SQL for relational integrity and joins; Mongo for flexible documents and fast iteration. Tie to your project’s access patterns - never “because tutorial.”
Q. Move zeroes to end? A. Two pointers: write non-zeroes forward, fill rest with 0. O(n) time, O(1) space. Mention stability if required.
Q. LRU Cache? A. Hash map + doubly linked list: O(1) get/put; evict tail on capacity. State concurrency caveats if asked.
Q. POST vs GET? A. GET safe/idempotent/cacheable; POST for state-changing bodies. Using POST for reads breaks HTTP semantics and caching.
HR
Q. Willing to move to Bangalore? A. Yes with a concrete reason (team/office/product). If constraints exist, state them early - do not surprise HR later.
Common questions checklist
OA
Matrix DP; Trie; greedy array/string; LRU; SQL
Interview
Medium DSA with dry-run; web stack defence; ACID; HTTP; sorts; OS
Projects end-to-end
HR
Bangalore; product awareness; background
Tips from successful candidates
Assessment tips
Practise Trie before BigBasket OA - hard word-matching shows up
Greedy digit/slot problems: sort per spin, aggregate columns
Interview tips
Dry-run before claiming done; EM rounds probe stack choices
Know merge vs quick trade-offs cold
HR tips
Be honest about app usage; commit clearly on location
These links are research inputs we used to map round structure and recurring questions - not copied page mirrors. We reorganized reports into process tables, outcome notes, and prep takeaways for BigBasket.