Getting an Interview
Getting an Interview
Interviews for Top Jobs at Yahoo
- Software Engineer (143)
- Intern (26)
- Senior Software Engineer (26)
- Software Engineer Intern (18)
- Technical Yahoo (17)
- Product Manager (10)
- Program Manager (8)
- Engineer (8)
- Technical Yahoo - Software Engineer (8)
- Web Developer (7)
- Senior Program Manager (7)
- Systems Engineer (7)
- QA Engineer (6)
- Technical Intern (5)
- Manager (5)
- Research Scientist (5)
- Senior Product Manager (5)
- Project Manager (5)
- Service Engineer (5)
- Senior QA Engineer (5)
- Director (5)
- Software Developer (5)
- Front End Engineer (5)
- Software QA Engineer (5)
- Account Manager (5)
- Marketing Manager (5)
- Software Engineering (5)
- Architect (4)
- Software Intern (4)
- Human Resources (4)
Service Engineer Interview
I applied in-person. The process took 2+ months – interviewed at Yahoo (Sunnyvale, CA) in August 2014.
I was advised it was going to be a 2 months process.
I had already contract for Yahoo so I went directly to the 5-hour interview with five interviewers.
- Interview was very technical, ranging from easy questions such as how to get the return code for a command ($?), how to find out swapping usage, how to troubleshoot an slow web site( cluster of 400 hosts) to how to troubleshoot one specific ads not showing on the web site. Questions about scripting, such as how parallelize a curl to different hosts. How to implement monitoring (either passive or active and why). Explain SSL handshake. Implement manually a log rotation. Troubleshoot machine rebooting very often. Unix internals: concept of stack,heap. Describe in detail your biggest accomplishments. Answer Question
Other Interview Reviews for Yahoo
Service Engineer InterviewAccepted OfferNeutral ExperienceAverage InterviewAccepted OfferNeutral ExperienceAverage Interview
I applied through a staffing agency. The process took 2 days – interviewed at Yahoo (Sunnyvale, CA) in February 2012.
The interview was good, the problem was parking was a pain to figure out where the guest parking was. I hate the stupid questions on tech like "if you had this problem, how would you fix it?" Really most of the questions are good for people with less then 10 years of experience but if you been doing it for a long time, you grow tired of the silly questions like "how do you reboot a computer".
Told them this is what I want, they said this is what we can pay, and we met i the middle.
Service Engineer InterviewNo OfferNegative ExperienceEasy InterviewNo OfferNegative ExperienceEasy Interview
I applied through a recruiter. The process took 2 weeks – interviewed at Yahoo (Sunnyvale, CA) in October 2009.
Both were phone interviews they didnot call for onsite after second round. Both interviews lasted 45 mins
First interview was straight forward screening interview . Interviewer just wanted to check if I knew basic tools and basic concepts about debugging. simple questions about what is ACL , If you have a network problem how will you go about debugging it.
Second interview was a bad experience. First of all the interviewer called 45 minutes late saying he forget he had to call me. Then for 10 mins he was wondering what to ask me. Then he picked up a web project I had worked on and started asking silly and random debuggng questions. The questions were so general I really didnot know what he was looking for whether he was looking for any specific tools or names ? The questions didnot seem to test my skills to much extent. The whole interview had a subjective feel to it and I cannot say they rejected me as I gave wrong answers in second interview rather he didnot like my answers.
Service Engineer InterviewAccepted OfferAccepted Offer
Service Engineer InterviewAccepted OfferNeutral ExperienceEasy InterviewAccepted OfferNeutral ExperienceEasy Interview
I applied through college or university. The process took 2 days – interviewed at Yahoo (Bangalore (India)) in March 2008.
Yahoo! came to our college as the campus hiring process. We had following rounds in the interview:
1. Written test: This was the tricky part, if you answer more Unix/Script related questions interviewer will select you for systems engineering regardless of your answer in Programming side (Probably because not many people will master this).
2. 3 technical discussions: Generic questions, few can be tricky
3. 1 programming round
4. HR Round.
- Search for a string in a file with efficiency O(1). (Trick: Ask more about the data being stored). Answer Question
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review