Oyo Rooms Interview Experience for FTE (On-Campus)
Interview Experience
I recently got Placed in Oyo Rooms through an On-Campus Drive. Here I am Sharing My complete Recruitment Process (Online Test and Technical Interviews). Hope You All Find ...
Full Details
I recently got Placed in Oyo Rooms through an On-Campus Drive. Here I am Sharing My complete Recruitment Process (Online Test and Technical Interviews). Hope You All Find this Helpful !!! Criteria : BTech(IT, EC), Dual (IT & EC) with no active backlog. The selection process had 3 rounds — a coding test, and 2 technical interviews (There was no HR round). The entire process happened virtually through Google Meet.
Round 1 Online Test This round was conducted on HackerEarth platform. It had 2 sections and candidates were given a time of 1 hour 30 minutes. Programming MCQs — 18 MCQs (each of 2 marks) Questions were a little tricky. it tested upon one’s programming fundamentals. It had C/C++
output questions , pseudocode questions, Operating systems and sql queries.
Coding 2 ( one contains 75 marks and the other contains 100 marks ) 1. https://www.geeksforgeeks.org/dsa/count-of-ways-to-travel-a-cyclic-path-in-n-steps-in-a-triangular-pyramid/ 2. https://leetcode.com/problems/delete-and-earn/ Ours scores of the first 2 sections weren’t revealed. My MCQs went really well. I solved 2 coding question in the coding section. Only 15 students got selected for the interview round, and I was one of them.
Round 2
Technical Interview 1 This round was scheduled for 1 hour and the panel had 1 interviewer. Being a virtual interview, the first challenge that I faced was that the interviewer was not audible. I suggest you to not panic in such a situation and use the chat box feature (or contact the HR if need be) to figure out something that works for you and the panel. We later connected over voice call (over phone) with our videos ON (over laptop) and continued with the interview. The interview started with my introduction followed by these questions: 1. https://www.geeksforgeeks.org/dsa/median-of-stream-of-integers-running-integers/ 2. https://www.geeksforgeeks.org/dsa/boundary-traversal-of-binary-tree/ 3. https://www.geeksforgeeks.org/dsa/find-four-numbers-with-sum-equal-to-given-sum/ The interview was very calm and helpful. I was able to solve all questions and I explained different approaches to solve the questions. Once he was convinced of my solution, he asked me to write the code on my own IDE.
Round 2
Technical Interview 2 This round was also based on your knowledge of DSA. I was asked 3 coding questions. 1. https://leetcode.com/problems/rotting-oranges/ 2. zigzag string question. 3. https://www.geeksforgeeks.org/dsa/coin-change-dp-7/ he understood my situation and asked me to explain my approach. i started with brute force and optimized it. Then he asked a couple of questions from OS and DBMS which were pretty easy. At last we ended the interview on a good note.
Result The interviews had gotten over by noon, and the results were declared in the evening. 3 students were selected, I was one of them. Tip: Be confident and focus more on solving DSA problems as they test your programming skills and problem-solving skills.
About This Question
This is a candidate experience report from a oyo rooms interview for a swe role during the oa round reported in 2025.
It covers the following topics: Trees, Strings, Dynamic Programming, Binary Tree, Sql, Os .
Difficulty rating: Easy
Topics
More Oyo Rooms Interview Questions
About Oyo Rooms Interview Reports
This question was reported by a candidate who interviewed at Oyo Rooms. 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 Oyo Rooms are the higher-signal extractions to take from this report.
For broader preparation context, the Oyo Rooms 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 Oyo Rooms reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Oyo Rooms 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 Oyo Rooms 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.