Yahoo Interview | Set 3
Question Details
I would like to express my gratitude towards the GeeksforGeeks team, whose help saw me through to Amazon's interview rounds and getting placed at Yahoo. Number of Rounds: ...
Full Details
I would like to express my gratitude towards the GeeksforGeeks team, whose help saw me through to Amazon's interview rounds and getting placed at Yahoo. Number of Rounds: 1 written, 1 coding and 4 interview rounds Written Aptitude Round: 30 questions were given and time was 60 minutes. The questions had varying difficulty. Subjects included Mathematical Aptitude (5-6), Graphs, OOPs, OS, DBMS, Networking and C. Strong subject knowledge was required to clear this round and it was a very tough elimination round.
Coding Round : 2 hrs This was 1 of the toughest coding rounds as the only language given was C and we needed to parse a XML file of the following format:
Interview Round 1 - 1 hour: Was asked several basic algorithm questions such as in-order is given, what more is needed for creating a tree, add multiple linked list represented decimal numbers etc. Then few Graphs related questions such as a hill is present, few taps are present, all connected to other taps above/below, find which tap will be the last one to get water from a spring on the top of the mountain. At first the graph was a tree structured then he generalized it to graphs. Finally he asked me to implement an efficient Web Crawler with 100 seed URLs. Conditions were added ,define efficiency, how many threads will be needed, mutex/semaphores pros and cons, Data structure required,efficient query on them, Denial of Service avoidance etc. I had prior experience with both Web Crawling and Huge Graph Clustering techniques so was able to answer all questions asked. I would advice everyone to prepare multiple subjects thoroughly, at least OS, Networking and DBMS.
Interview Round 2 - 30 minutes: It was basically a test of my OOPs knowledge, was told to approach the XML parsing in OO paradigm. Design a couple of classes, explained all the basic OO fundamentals were being followed. Interviewer continued to ask me to do better, no hints were provided, he was not completely satisfied but felt the design was sufficient. HR-Semi Technical Interview
Round 3 30 minutes: All round questions were asked from background to future prospects, and I had an internship in IIT KGP, so was asked about the project and how my project could contribute to the real world. Do prepare your projects specially the motivation behind it. HR Interview with
Manager 30 minutes : Questions like how can you improve this Interview procedure, what challenges will you face when you join us, how can you make us better were asked. After my final round, an hour later the results were announced. I and another one of my peers got
HIRED This article is compiled by Pratyay Banerjee. Many Many congratulations to Pratyay. All Practice Problems for Yahoo !
About This Question
This is a reported interview question from a yahoo interview for a swe role (intern level) during the phone screen round reported in 2025.
It covers the following topics: Linked List, Trees, Sql, Graph, Stack Queue, Os, Graphs, Stack .
Difficulty rating: Easy
Topics
More Yahoo Interview Questions
About Yahoo Interview Reports
This question was reported by a candidate who interviewed at Yahoo. 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 Yahoo are the higher-signal extractions to take from this report.
For broader preparation context, the Yahoo 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 Yahoo reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Yahoo 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 Yahoo 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.