Redbus Interview Questions (2026)
2 questions · GeeksforGeeks (2)
RedBus Interview Experience for Software Engineer | On-Campus 2021
Question Details
redBus visited our campus in the month of September 2021 for Software Engineer role. The shortlist for the online test was done on the basis of 2 parameters:
Parameter 1: 10th & 12th/Diploma marks - 87% & above Parameter 2: BE CGPA - 8.5 & above Round 1(Online Test): Test was moderate with 23 MCQs and 3 programming questions. MCQs were easy with questions on java concepts, c++ code snippets and moderate aptitude questions. Coding was a bit tough. One of the questions that I remember is: Write a program in the language of your choice to find out how many minutes M will it take for a phone to reach from charge A to charge B (A and B are inputs, M should be the output). The rate at which it gets charged at different levels was given. For example: 0<= C <= 10 : 8 mins 11<= C <= 50 : 6 mins And so on Sample: If A= 0 and B=5 then M is 8 because in 8 minutes it reaches 10 charge which is greater than 5. Getting the output for at least 1 program along with decent performance in MCQs was sufficient to clear the test. 46 out of 211 students were shortlisted for the
next round Round 2:(Technical Interview 1): Introduce yourself Coding questions to solve ( first occurrence of a number, binary search (palindrome, sorting for others)) and even explain the approach used with time complexity Questions regarding projects mentioned in the resume were asked. I was asked to show the code if the code is there in the system They shared a document having 2 coding questions (divisibility by 3, 5, or 10 & print element that is in the same position in 2 unequal length lists), 2 MCQ of guess the output (pointer questions), and 2-3 logical questions (relationship, number pattern, etc) which I was asked to solve 30 students were shortlisted for the
next round. Round 3(Technical Interview 2): Introduce yourself Technical questions regarding oops concepts of java, joins and normalization in DBMS etc Questions and discussions regarding projects Advantages of python and java over each other Coding question on finding the minimum element appearing before the maximum element in a list 20 students were shortlisted for the
next round. Round 4(HR Round): Technical questions like the implementation of stacks, stacks using queues or vice versa Design a database table for a bus travelling from so and so time to so and so destinations. HR questions like what was the most difficult situation encountered in life How did you handle differences between your project partner while working on the project etc? What are you passionate about in life? Which technology would you like to work on in redBus? 8 students were selected for a full-time offer.
Topics
More from Redbus
Related companies
Redbus Interview Process Overview
The Redbus 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 Redbus runs a calibrated process consistent with industry norms for companies of its tier.
Difficulty calibration: Redbus 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 Redbus Question Reports
Real candidate-reported interview questions are a calibration tool, not a memorization target. Redbus 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 Redbus 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 Redbus'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 Redbus Interview Mistakes
Reports tagged "no hire" at Redbus 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.