Ibibo Interview Questions (2026)
1 questions · GeeksforGeeks (1)
Top topics
Why I didn't go for lucrative offers of Ibibo/ZoomCar and decided to go for an entrepreneurial journey in the current Startup I am working for
Question Details
ZoomCar Interview experience: Few weeks ago, I got a mail from Zoomcar HR saying that the CTO of the company wanted to have In-person interview with me.I was a bit shocked and confused, Since Zoomcar is now mid-size startup ,having a tech-team of 50+ people.But since the CTO directly called me for the interview so I decided to go and visit him. First Round with CTO Duration : 1 hour 30 min General Questions about the key roles which I am playing currently like leading tech team in the current startup i am working for, advising startups and advising students on programming. How I built the Bi-directional syncing architecture in my current startup, then he put some constraints to improve it to make scalable and reliable. How I build the Muliti-tenant server architecture in current working startup. We discussed on haproxy,Master-Slave configuration,Replication and redundancy. Basic Questions on Rails architecture and REST . Basic Algo Questions : a.Implement queue using two stacks ,in the most optimized way possible. b.Remove duplicates from linked list . Basic questions from Ruby about block , proc and lambda. Second Round with Technical Lead Duration : 1 hour TL entered into the conference room and went through my resume . He asked me about my Google interview experience. We discussed about my college project Search engine. He asked about the data structure to store index and algorithms involved in building search index , he also asked me about how google stores their index on multiple machines . He asked me how to build a spell correction if there were no dictionary, then he asked me to implement Trie . Finally we discussed on how Google spell correction works , discussion went on bayes theorem and NLP. He also asked me a few more data structures question on hashmap,stacks,Linkedlist,Heap,B-tree etc. We also had a discussion about Zoomcar server-side architecture . He also asked me some advance ruby concepts like metaprogramming , modules , etc Finally, CTO entered the conference room and asked me about my expectation, since I hadn’t prepared my mind to go and crack the interview, so I roughly gave them one BIG number, next day I got a call from HR saying that they are ready to hire me for the same. BOOM! IBIBO Interview experience : All interviews were taken by Tech Head of the product team. First Round : Which is more secure get or post. Discussion on REST architecture. What are the different dynamic ways to call a function. How modules and Class store in memory. Discussion on meta-programming in ruby. Find the missing and repetition number in an array. Discussion on Bi-directional sync architecture apps and server. Second Round : Asynchronous function call in ruby. Threads in ruby. Modules and Classes in ruby. Symbol and variable in ruby and python. How Zookeeper works. How to delete nodes in a heap. Third Round : Closures in javascript. Basic Jquery questions. Single and Multi-column index in mysql How prototype works in javascript. Active Record and Action controller in Rails. Discussion on my college project Search Engine. The Interviewer also told me about work culture at ibibo office . Fourth Round : Build a Rails app for authentication of users which consumes Rest api and oauth2 implementation. There were some other constraints also in terms of UI like page should refresh and UI should be attractive etc. After being interviewed and getting feedbacks from HR of both the companies, I was bit confused whether I should go for these companies or I should work for growing startup , So I had a talk with my founder over drinks that I really wanted to groom myself as an entrepreneur , but if i join any of them , I will grow as a developer. So my founder gave me an opportunity to groom as co-founder and lead in tech, Operations and represent the company to investors for fund raising. So I recommend all the students that you should invest early stage of your career working amongst passionate people in a small companies where you will be have more responsibilities and you will be able to prove yourself that will help you in grooming more compare to other big tech companies. You can know more about me at www.codedoctorx.com , Happy Coding :)
Topics
Related companies
Ibibo Interview Process Overview
The Ibibo interview process typically includes a recruiter screen, one to two technical phone screens, and a 4-6 round on-site or virtual on-site loop. Each round serves a distinct calibration purpose: coding rounds measure correctness, code quality, and complexity reasoning; system design rounds measure architectural judgment at the appropriate level; behavioral rounds measure ownership, leadership scope, and collaboration. Reports tagged on LeakCode from 2024-2026 show Ibibo runs a calibrated process consistent with industry norms for companies of its tier.
Difficulty calibration: Ibibo coding rounds typically run medium difficulty with follow-up depth as the senior discriminator. System design rounds expect production-grade trade-off articulation at L4+ levels. Behavioral rounds expect quantified outcomes ("reduced p99 latency from 800ms to 120ms") rather than vague impact claims. The candidates who advance consistently demonstrate clear thinking out loud rather than perfect final answers.
How To Use Ibibo Question Reports
Real candidate-reported interview questions are a calibration tool, not a memorization target. Ibibo updates its question pool every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage approach: identify the patterns that appear repeatedly in Ibibo reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions above by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Ibibo's pool. Reports tagged with quantified difficulty and explicit round type are higher-signal than reports without those tags. The metadata filters help you build a focused study plan in 1-2 hours rather than 8-10 hours of unstructured browsing.
Common Ibibo Interview Mistakes
Reports tagged "no hire" at Ibibo consistently surface a few patterns: jumping into code without clarifying requirements, coding silently for extended periods, missing edge cases (empty input, single element, large input, overflow), producing working code the candidate cannot refactor when probed, and behavioral stories that use "we" instead of "I" diluting individual signal. Strong candidates explicitly avoid these patterns by following a consistent round template.
The single most predictive failure mode in recent reports: not asking clarifying questions. Interviewers are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into implementation immediately. Strong candidates also verbalize their approach before writing code; weak candidates code in silence and lose the communication dimension of the round's calibration.