Smart engineers. Fun people to work with. Lively and happy atmosphere. Very good work/life balance. Good use of (some) open source code and tools. Good benefits for full-time employees.
No clear direction for engineering. Not able to take engineering risks to innovate. Pressure to launch without much thought on maintenance. Strong "not invented here" pressure against non-Yahoo code.
First, I introduced myself to the interviewer. He then asked me some questions regarding my resume. After that, he asked me some common interview questions and one coding question.
The hiring process started with a recruiter, followed by a simple 1:1 phone interview. It involved an easy question to solve a BST. Any computer science student should know all algorithms when applying to Yahoo!
Phone interview and then onsite. 1. Merge sorted list. 2. HashMap implementation. 3. Is Palindrome.
First, I introduced myself to the interviewer. He then asked me some questions regarding my resume. After that, he asked me some common interview questions and one coding question.
The hiring process started with a recruiter, followed by a simple 1:1 phone interview. It involved an easy question to solve a BST. Any computer science student should know all algorithms when applying to Yahoo!
Phone interview and then onsite. 1. Merge sorted list. 2. HashMap implementation. 3. Is Palindrome.