Yahoo Interview Questions

Try some questions now

We've helped several engineers get the job at Yahoo

Interview Cake is a tool that helps software engineers prepare to interview at top companies like Yahoo! Thousands of applicants interview with Yahoo! each year, and so many show up unprepared after only having done some basic interview prep. That’s not enough to land your dream job at Yahoo! We can help you ace your technical interview by giving you an interview strategy to prepare for even the toughest questions

Yahoo! has long been regarded as one of the top companies in the world. Their engineering team is top-of-the-line and are hyper-focused on groundbreaking solutions for the everyday user. With the competition constantly pressuring them to think out of the box, Yahoo! has high expectations for their engineering team. The interview at Yahoo! will challenge you. You will be expected to prove that you are the best of the best. Interview Cake’s strategic approach to interview prep will make sure that you’re covering all of the bases ahead of your interview with Yahoo!

Get ready for Yahoo with the free 7-day crash course!

In this free email course, you'll learn the right way of thinking for breaking down the tricky algorithmic coding interview questions Yahoo loves to ask.

Practice Questions for the Yahoo Interview

Yahoo!’s coding interviews are hard, but not impossible. It just takes some practice. Our program is a step-by-step guide to coding interview preparation.

2nd Largest Item in a Binary Search Tree »

Find the second largest element in a binary search tree. keep reading »

Reverse Words »

Write a function to reverse the word order of a string, in place. It's to decipher a supersecret message and head off a heist. keep reading »

In-Place Shuffle »

Do an in-place shuffle on an array of numbers. It's trickier than you might think! keep reading »

Does This Linked List Have A Cycle? »

Check whether a singly linked list has a cycle, using only O(1) additional space. A classic coding interview question, with a step-by-step solution. keep reading »

Delete Node »

Write a function to delete a node from a linked list. Turns out you can do it in constant time! keep reading »

Largest Stack »

Implement a stack with a get_max method that returns the largest item in O(1) time: the max stack problem, with a step-by-step solution. keep reading »

Merge Sorted Arrays »

Write a function for consolidating cookie orders and taking over the world. keep reading »

Bracket Validator »

Check whether a string's brackets, braces, and parentheses are properly nested and closed: the valid parentheses problem, solved step by step in O(n) time. keep reading »

Find Duplicate Files »

Your friend copied a bunch of your files and put them in random places around your hard drive. Write a function to undo the damage. keep reading »

Implement A Queue With Two Stacks »

Implement a queue with two stacks. Assume you already have a stack implementation. keep reading »

What people are saying about Yahoo's interview

Check out some of the positive highlights that others have written about their Yahoo! interview experience on Glassdoor:

  • ”Very straightforward. Lots of data structure and algorithm question. The interviewers were friendly and helped with the questions. The interview process took couple of hours. Lot's of white boarding. I will suggest practice question on whiteboard. It will help.”
  • ”The first phone interview was on an array problem. It involved finding lowest unique minimum. The second phone interview was a string DP problem - it was challenging. The interviewer was very kind and gave me extra time to write pseudo code as I came up with another solution (the first one I gave was incorrect) towards the end.”

And here are some of the negative experiences interviewees have reported to Glassdoor:

  • ”Three round, each 45minutes. Did not even have time to have lunch. First round about system design, second half system design, half coding. Third, a coding question which is really hard.”
  • ”It is a phone interview, asked some basic technical problems. The person interviewed me did not ask anything about my resume, just the basic principle I learned in class. I was asked some problem about OS, database and algorithm.”
. . .