Still a very good brand name, and there are still a lot of talented individuals around the company. If you landed on a good manager and project, you will feel great; otherwise, it is all downhill.
Unstable both financially and in company direction.
It is a very strange environment. They have tons of good engineers (okay, most of the engineers are good, only a small portion of them underperform), but the end results are far from satisfactory.
Not all management are bad, to be fair. However, there are a few bad ones that do a lot of damage to the organization, and usually, those damages are much greater than the work done by good management.
Lot of overhead in terms of process. You don't yet have a successful product launch, but you already have the bureaucracy come as a free lunch. 300 men working on an app launch that only has 2 customers.
My biggest complaint is that Yahoo! created a lot of opportunities for people to grow, but this is the exact reason why Y! is going downward. Too many layers, too many people try to impose their will on others because they want to show they are growing. It is not natural; a lot of people suffer because they are impacted by these people's selfish motivations.
Why don't we let engineers vote for who to let go in the next round of layoffs, instead of it being purely done by some invisible management that still gets it wrong 50% of the time?
And maybe a 20% layoff just for manager titles, yeah, that will help.
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.