Interview Experience with Yatra(Hyderabad) | Set 3 (For Senior Software Engineer)
Interview Experience
I had a total of 5 rounds.Initially I thought there will be only 3 rounds. Round 1:1. Rotate a matrix by 90 degrees clockwise.( He asked me have you heard of question.I sa...
Full Details
I had a total of 5 rounds.Initially I thought there will be only 3 rounds.
Round 1 1. Rotate a matrix by 90 degrees clockwise.( He asked me have you heard of question.I said Yes.Then he asked me to code) 2. Find vertical sum of nodes present in same vertical line in binary tree. ( He again asked me have you heard of question. I have heard it but didn't remember the approach. It took some time and then I started telling my approach.He aasked me to write code and question regarding get sums from left to right , for which I made use of linked hashmap) Overall It was very cool for me
Round 2 1.Reverse K blocks of nodes in linked list. There are two interviewers this time, probably, guy was senior he was asking me question.He was very particular in coding. Checked every edge case.and asked me evrything.Initially I told the approach and then started coding. 2.Find min in stack in O(1) Pretty straightforward written code.Again he checked all edge cases with my code. 3. Then asked about counting sort and its code. 4. And a simple question on array sorting. Round 3 (Manager round): I thought this was last round as they have said like.She asked me about my strengths and challenges I faced.How I overcame through it 1.Basic question on oops concepts.(runtime polymorphism). 2.Design tables for getting all employees under manager. I screwed it little bit.But some how I got answer which I was not satisfied as well. I was expecting result either yes/no.But they called me for another round of interview may be because of my expected salary which was high compared to my previous. Round 4 (Technical): 1.Given "aaabbbccc" it should return "a3b3c3" in place. Initially I explained brute force approach then he said array has 2n space.I was able to remember approach for quicksort and started explaining after which I grew confident on it.He was satisfied.Questions on time complexity of algo and space complexity discussions. 2.Again a question on OOPs.This time I was completely wrong in answering it.I thought interview with yatra was closing for me.He was not satisified much with this. Luckily, there was another round with manager. Round 5( Manger) 1.He asked me to find words which are having particular pattern.Then I said it was KMP algo. Can I explain it ?? I started explaining approach, may be he was busy with something, he asked me to write pseudo code.He left the room for 15 mins then he came back I had almost completed the code, which he was satisified. Some basic questions on spring ( my previous work was related to it). Then my expected salary and my position If I got selected in yatra were discussed.
About This Question
This is a candidate experience report from a yatracom interview for a swe role (senior level) during the phone screen round reported in 2015.
It covers the following topics: Linked List, Trees, Matrix, Arrays, Binary Tree, Stack Queue, Sorting, Hash Table, Stack .
Difficulty rating: Easy
More Yatracom Interview Questions
About Yatracom Interview Reports
This question was reported by a candidate who interviewed at Yatracom. 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 Yatracom are the higher-signal extractions to take from this report.
For broader preparation context, the Yatracom 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 Yatracom reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Yatracom 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 Yatracom 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.