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: 1...
Full 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.
About This Question
This is a reported interview question from a redbus interview for a swe role during the oa round reported in 2022.
It covers the following topics: Sorting, Binary Search, Sql, Strings .
Difficulty rating: Easy
Topics
More Redbus Interview Questions
About Redbus Interview Reports
This question was reported by a candidate who interviewed at Redbus. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Redbus are the higher-signal extractions to take from this report.
For broader preparation context, the Redbus interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Redbus reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Redbus Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Redbus reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.