Good pay; nice and intelligent people; good cafeteria; low pressure; no crazy deadlines.
I can always get time off for my own needs.
Managers are in cubes, not offices; this makes a huge difference for some reason.
Engineers are in cubes, not in ridiculous "pods" that are becoming trendy at some companies.
Linux and FreeBSD workstations with big monitors.
Sane technologies; Y is mostly too smart to buy shrinkwrap junk.
Total paralysis by red tape. With thousands of engineers, almost nothing gets done. There is no clear delineation of responsibility. Too many chefs with fingers in too many pies. We will spend months discussing whether it's worthwhile to build a system that would actually take a weekend to code.
The org is impossibly deep; last time they tried to flatten it, it got deeper. We are more focused on means than ends. We are totally committed to our rules, systems, and procedures, and totally oblivious to the outside world.
The executives are amazingly out of touch. Every few months they have a new "trend" which has no relation to what engineers are doing. At one point, they claimed everyone should have one number they were being judged on - whether it was sales per quarter, site uptime, etc. Of course, nothing was done about this.
Yahoo welcomes ideas from engineers, but almost always discards them. We have built a lot of cool features which would have put Y ahead of Google in small areas, but the public will never see them. The only thing Y reliably cares about is more ads.
I don't know how to solve Yahoo's problems. We were basically the same under Semel. Changing leadership didn't help; constant reorgs haven't helped.
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.