I applied through a recruiter and the process took 2 weeks - interviewed at Yahoo in September 2013.
Interview Details – There are two phone interviews before the onsite interviews. I made to the second phone interview. The goal of the first interview seemed to mainly be about getting a good feel for the candidate. The interviewer asked me about past projects I had worked on and any problems that I had to overcome. The second phone interview was a technical test. He asked me technical questions, many of which I had found online from past candidates. The twist was how well you knew the subject, and not necessarily whether or not you got the correct answer. This interviewer's tactic was to continuously ask me "how can you make that solution better" after each question. He told me I got most answers correct, yet I stumbled each time he asked me to find a better solution. The stumbling, I feel, kept me from the onsite interviews.
Interview Question – How can you tell if a linked list is circular (goes on forever because it connects to a previous node)? View Answer
I applied through a recruiter and the process took 4 days - interviewed at Yahoo in July 2013.
Interview Details – I was asked about circular linked list, quick and merge sort algorithms. Also couple of questions on Hashing and then moved to Sets and Maps. Overall it was easy. Waiting for the interview results.
Interview Question – No questions were unexpected. Most of them on expected lines on algorithms. Answer Question
I applied through an employee referral and the process took 2 weeks - interviewed at Yahoo in May 2012.
Interview Details –
Interviewed for backend position.
Phone screening was mostly revolved around servers scalability issues and connection stacking.
Personal interview is mainly based on my previous projects and technologies.
Whole experience was smooth
Interview Question – How to deal with the scenario of connection stacking and number of open connections in a mail server? Answer Question
The process took 2 weeks - interviewed at Yahoo in April 2012.
Interview Details –
Very important: I had 2 interviews for 2 separate positions. In one I was interviewed by random people, and the other I was interviewed by my future team members. Guess which one game offer? The one where team members did interview.
Phone interview consisted mostly of Java core questions and may be be some threading. Was interviewed by my future manager.
On site, got interviewed by many people:
2) Java - language knowledge, and I think solve a problem
3) Threading, general how would you design a system.
No Google/Microsoft type questions.
When I was already working at Yahoo my team members when did interviews asked to solve real life problems which we had in our product and then saw if that matched our solutions.
The process took 2+ weeks - interviewed at Yahoo in August 2011.
Interview Details –
I was contacted by a hiring manager to go over my background and some screening questions such as race conditions, deadlocks, some C++ questions etc. He told me he'd like to schedule an on site interview - which was setup by their HR folks.
The onsite interview was a underwhelming. The guys supposed to interview me were not on time. One interview related to software design (patterns etc.) went really well. Second interview was more focused on C++ internals and other coding which went well. Interview related to data structures and algorithms was my weakest. I also met a director of engineering and had lunch with him. That also went fine.
Overall I thought their screening process could have been better. They were looking for some one well versed in web technologies and with expertise in algorithms whereas my past experience is in firmware, middle-ware and UI for handsets. I thought it was wastage of time for both parties and I had to burn a day of vacation.
They were right to not make me an offer. It was a bad match for both parties. I wish I had probed more to ensure that it was going to be something I would like to do and would match my skills.
I applied through a staffing agency and the process took 2 days - interviewed at Yahoo in April 2011.
Interview Details –
Phone interview was more about specifics of Java/J2EE technology.
1. What's the diff between interface and abstract class
2. Implement Fibonacci series. Can you implement the same using recursion? Which one is more efficient? why ?
3. What are the steps involved in creating a complete workflow of a module in Spring and Hibernate
4. What is dependency injection? Why is it good?
5. Explain many-to-many mapping concept using Hibernate
6. Write the query to find duplicates
1:1 interview had 3 rounds
1. You have a Employee class and Dept class. Give a complete design and implementation to get all Employees grouped by Departments
- Many-to Many mapping again with spring injections, they also checked why would you use certain data structures
2. Second round was based on the Producer Consumer problem and involved many threading concepts
3. Third round was based on design and performance oriented thinking. Let's say you had a 10Gigs of a text file and you were to collect a certain pattern of string and store it in DB. What was the most efficient way of doing it ?
The advice is:
Be good in Collections, Threads and Performance related questions
Work culture is good but very hectic. Agile, scrum methodologies are followed and there are pretty stringent deadlines. People are co-operative but one must have a lot of energy to find your way through gigantic code base and slightly complicated procedure to build and test the code. Good luck.
I applied through a recruiter and the process took 2 weeks - interviewed at Yahoo in August 2010.
Interview Details – Recruiter introduced me to the hiring team. There's a team of people dedicated to hiring at the time. Initial phone screen was pretty easy. Onsite interview consists of 5 people. A lot of grilling from 3 out of 5. The other 2 are more behavioral.
I applied online and the process took 4 weeks - interviewed at Yahoo in June 2010.
I applied through a recruiter and the process took a day - interviewed at Yahoo in May 2010.
Interview Details – While happy with my current job, I got connected to the recruiter through LinkedIn who forwarded my resume to one of the teams. I had a phone interview with Yahoo! Mail Search team. Questions asked were something like finding possible substrings in the string and some C++ concept questions. The interviewer was the worst interviewer I have ever experienced. I was pretty sure that she didn't bother going through my resume before the phone interview. She was very rude and was not paying attention to my answers. At the end, we ran out of time and she didn't let me ask questions because she was in hurry to get off the phone.
Interview Question – write a program that finds all repeated substrings in the string and provide the complexity of this program. how can you make it to perform better in time and memory? Answer Question
Pros: Free food, flexible work hours, CEO with vision, company on the rise – Full Review
Your feedback has been sent to the team and we'll look into it.
The difficulty rating is the average interview difficulty rating across all interview candidates.
The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.
Your response will be removed from the review – this cannot be undone.
Simply post an anonymous review for a recent interview experience or current/former employer. Your post is anonymous – and if you're worried someone will be able to identify your review, you can even post without telling us your job title and location. Learn More.
No thanks –