Great work environment, especially in regards to work-life balance.
Great teams with talented and smart people.
Good benefits (Gym, Cheap Food, Health, Dental, 401k 1.5 match) and compensation inline with the market and sometimes higher than the average.
Working on some of the biggest products on the internet with hundreds of millions of users.
Working on high-scale and high-performance challenges.
Lots of learning opportunities when you have a good coach/manager.
Focus resources on bold bets, get rid of non-growing businesses or make them as cost-effective as possible, and invest in disruptive/high-growth opportunities.
Create multi-functional, product-focused teams, not discipline groups. You end up with discipline silos that don't care much about the product they are building and more about their specific roles. This environment creates little connection between people and the products they work on.
Invest in modernizing tools and fix the platforms. Make the internal platforms compete with external services like Amazon and others. Nothing like competition to shake things up.
Focus on continuous delivery, small and incremental development.
The interview process started with a phone screen. This was followed by a full-day, on-site interview. During the on-site interview, there were detailed questions about my experience. The full day involved interviews with various members of the te
I was scheduled for a phone screen, and then an engineer called me. He asked me some algorithmic questions about data structures and about how to implement a calculator. He also posed a brainteaser-type question.
This was by far the best interview experience I had. I had two short phone interviews, which went pretty well. There were no weird questions, just all fundamental and basic questions. Then I was invited for an on-site interview, which was very well
The interview process started with a phone screen. This was followed by a full-day, on-site interview. During the on-site interview, there were detailed questions about my experience. The full day involved interviews with various members of the te
I was scheduled for a phone screen, and then an engineer called me. He asked me some algorithmic questions about data structures and about how to implement a calculator. He also posed a brainteaser-type question.
This was by far the best interview experience I had. I had two short phone interviews, which went pretty well. There were no weird questions, just all fundamental and basic questions. Then I was invited for an on-site interview, which was very well