The benefits are good, but not much else.
Frankly, Yahoo is one of the worst places I've ever worked in my entire career. The management churn and constant re-organization is abominable. I had five managers in the space of eight months, the last of whom laid me off under false pretenses, pretty much because he didn't like me personally, this after seven years of success with the company.
Yahoo HR absolutely lied about my being placed upon a PIP before being laid off. (PIP = Performance Improvement Plan.) The HR rep said that I'd be placed on a PIP with an opportunity to "improve" before any lay-off. Lies, lies. I never had any PIP in place before I was suddenly "laid off."
Even though via the lay-off I was provided with an opportunity to re-hire with Yahoo, I would never, ever think of doing so again.
Unless you're a newbie just starting out and you don't know any better, stay away from this company. They'll screw you at their earliest opportunity.
Fire and replace all of your so-called management. They haven't a clue what it takes to make a company like Yahoo successful. Really, they don't. Dump them all and start all over again.
Two phone screens were involved. Live coding in a shared document. Then an on-site interview with several engineers. Lots of writing code on whiteboards. It was long and thorough, but not uncomfortable. Everyone was pretty friendly and supportive.
The phone interview was quite easy. It covered standard algorithm questions, threads, performance analysis of C++ processes on Unix/Linux systems, and some C++ questions on pointers. The 1:1 interview was a little more theoretical, focusing on desig
First, I had a phone interview. During the interview, the interviewer asked C++ questions and puzzles. The C++ questions were easy (standard questions), but the puzzles were a little difficult. I never expected puzzles in a phone interview. "Huh... w
Two phone screens were involved. Live coding in a shared document. Then an on-site interview with several engineers. Lots of writing code on whiteboards. It was long and thorough, but not uncomfortable. Everyone was pretty friendly and supportive.
The phone interview was quite easy. It covered standard algorithm questions, threads, performance analysis of C++ processes on Unix/Linux systems, and some C++ questions on pointers. The 1:1 interview was a little more theoretical, focusing on desig
First, I had a phone interview. During the interview, the interviewer asked C++ questions and puzzles. The C++ questions were easy (standard questions), but the puzzles were a little difficult. I never expected puzzles in a phone interview. "Huh... w