The first interview was a phone interview. It wasn't terribly hard in concept, but it was challenging given the number of problems that were asked of me over the phone in about 30 minutes. One of the questions was a data structure question, and another two were design pattern questions. Of those, one focused on multi-threaded implementation, and another on general object-oriented design.
They were prompt in responding, and I was invited onsite. Onsite interviews were moderately hard technically, but extremely challenging given the number of questions asked in a single interview session. I had a total of five 1:1 interviews, which included a lunch interview. There was never a moment during my onsite where I was at ease; I was constantly writing code on a whiteboard, one after another. A lot of focus is given to your thought process, ability to improvise, and identifying issues with scenarios that are described to you.
I would recommend preparing well for onsites. It is not just your knowledge that will be tested, but also your speed and ability to switch context from one topic to another.
Various questions on design patterns. Various questions on multithreading concepts. Various questions on web service development.
The following metrics were computed from 35 interview experiences for the Yahoo Senior Software Engineer role in United States.
Yahoo's interview process for their Senior Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Yahoo's Senior Software Engineer interview process in United States.