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)
- Software QA Engineer (5)
- Research Scientist (5)
- Human Resources (5)
- Senior Product Manager (5)
- Senior QA Engineer (5)
- Service Engineer (5)
- Project Manager (5)
- Director (5)
- Front End Engineer (5)
- Software Developer (5)
- Account Manager (5)
- Marketing Manager (5)
- Software Engineering (5)
- Manager (5)
- Summer Technical Intern (4)
- Marketing (4)
I applied through an employee referral. The process took 2 days – interviewed at Yahoo (Sunnyvale, CA) in March 2010.
An employee referred me to an Architect level software engineering position within the company. A couple weeks after he forwarded my resume to the hiring manager, I received an initial phone call from the hiring manager.
The hiring manager was pleasant and very easy to speak with. We made plans for phone interviews and on-site interviews. The manager sent me an official job description.
The job description clearly indicated that the job was an "architect" level position. However, my on-site invitation referred to the position as a "Sr Principal Engineer" role. Later, the recruiter verbally confirmed that Yahoo would offer me a "Principal Engineer" position.
Is this a bait-n-switch act. I don't know for sure, but I don't like the initial feelings I have about it. Over the course of a week, the architect job has disappeared and has rematerialized as a job title 2 or 3 levels lower. This simply does not agree with my initial expectations for the job role and title.
- How do you influence others to take a course of action when you have no direct authority over them? Answer Question
Reasons for Declining
I have decided to decline the offer if we cannot resolve this job role/title problem. Of course, I have no leverage once I've joined, so it is better to ask for what I really want at this point.
Other Interview Reviews for Yahoo
Architect InterviewAccepted OfferNegative ExperienceAverage InterviewAccepted OfferNegative ExperienceAverage Interview
I applied through an employee referral. The process took 3 weeks – interviewed at Yahoo (Sunnyvale, CA) in May 2009.
The hiring process is generally flawed because the managers are looking for reasons not to hire rather than strong reasons to hire. The feedback is not collected by the hiring manager by consensus but rather in private closed door meetings with individual interviewers.
- What do you think of the Architect role and why should it not be eliminated? Answer Question
Architect InterviewNo OfferNegative ExperienceAverage InterviewNo OfferNegative ExperienceAverage Interview
The process took 4 days – interviewed at Yahoo (Bangalore (India)) in February 2010.
I was called up for the architect position. After briefly asking me about my previous projects, it
straightaway went to strategies for searches for huge number of web pages followed by
searches in huge files. I explained that I have never done such a thing and gave it a try.
The interview was abruptly cut within 20 minutes making it clear that I am not answering to
the interviewers satisfaction.
- Sorting web pages based on number of hits per hour for a month Answer Question
Architect InterviewNo OfferPositive ExperienceAverage InterviewNo OfferPositive ExperienceAverage Interview
The process took 1+ week – interviewed at Yahoo (Bangalore (India)) in December 2009.
Had a couple of rounds of phone interviews. There were lots of questions about algorithms specific to hadoop. Interviewed initially for the grid computing team though the technical went well, some gaps were found and Yahoo is planning to interview me for a different