It's a big operation. You can learn a lot as an engineer or otherwise (spend 1 or 2 years here and then leave). You can learn a lot of "how-not-to"s that would be very valuable if you start your own shop or get in the driver's seat.
There are also a good set of Yahoo technologies/tools that you could learn about. They do have a good coffee bar (free, of course), freshly made to order. You could get free soda if you go down to the first floor but not on other floors (very Yahoo-like, huh?).
Also, I guess, having Yahoo on your resume helps (anyone?).
Too many layers are slowing progress and not a lot of room to learn stuff outside your project. Because of too many layers, there's not much room to grow, and if you do grow, not much can be done. Fragmented teams make it really hard to defend team boundaries just to support having different teams. There are a lot of smart people and, at the same time, a lot more of the opposite. So things could get frustrating when the latter start going up the chain.
It might be a subsidized cafeteria, but ask anyone who eats there more than once, and you will know that the only reason they are eating there is because they have no choice (so are most company cafeterias).
Get rid of senior management and middle management.
Currently, the company seems to have some ideas to execute against, but in the long term, this bureaucracy is a drag and will not let the company compete much further.
The phone interview focused on specific Java/J2EE technologies. Key questions included: * What is the difference between an interface and an abstract class? * Implement the Fibonacci series. Can you implement it using recursion? Which method is mor
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
Intro call System design Technical discussion Product collaboration Technical screening No DSA and LeetCode, no take-home assignment, which is nice. It's hard to prep for either you will pass or fail; there's nothing to really practice.
The phone interview focused on specific Java/J2EE technologies. Key questions included: * What is the difference between an interface and an abstract class? * Implement the Fibonacci series. Can you implement it using recursion? Which method is mor
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
Intro call System design Technical discussion Product collaboration Technical screening No DSA and LeetCode, no take-home assignment, which is nice. It's hard to prep for either you will pass or fail; there's nothing to really practice.