Compensation is very good.
There are some extremely good engineers working at Yahoo.
It can be fun, but it isn't always.
In general, I have loved working at Yahoo.
Just not sure what I think of it lately.
I'll have to see how Ross works out as CEO.
At least he's human and a reasonable one at that.
Management is in constant turmoil.
Promotions to Architect are very difficult to come by; it's more like an old boys club.
You depend on a lot of other teams doing their part for you to be able to ship. Some of those teams are very poorly staffed and/or managed. Those teams always seem to miss their dates and their code quality is poor. There needs to be more accountability in the organization.
2 telephonic rounds: Questions are on basics. 7 technical rounds, face-to-face (company paid airfare and guesthouse). No direct questions, more tricky or experiential questions. To be better prepared, check for Yahoo! open-sourced products. All que
How to find the inorder successor of a node in a tree?
The interview process was quick, but I thought the position was being oversold and the interviewing process was very unstructured. I had to fly in for the interview, and they didn't have the interviewer ready. A few interviewers walked in randomly to
2 telephonic rounds: Questions are on basics. 7 technical rounds, face-to-face (company paid airfare and guesthouse). No direct questions, more tricky or experiential questions. To be better prepared, check for Yahoo! open-sourced products. All que
How to find the inorder successor of a node in a tree?
The interview process was quick, but I thought the position was being oversold and the interviewing process was very unstructured. I had to fly in for the interview, and they didn't have the interviewer ready. A few interviewers walked in randomly to