The pay and the benefits are nice.
There's a pretty decent work-life balance, but it can be bad depending on the team.
There are some genuinely smart people working there.
There's a solid mission that I believe a few people actually believe in.
Some ancient technologies and processes (SVN, JSPs, bad tooling, etc.). Getting code reviewed and deployed is a painful process. The tooling hinders more than it helps.
Trying to become an "engineering culture" place, but it isn't a technology company. This seems to be driven from management as opposed to from the ground up, in an attempt to attract more Bay Area talent away from companies like Facebook and Google.
Current turbulence as large restructuring in departments occurs and the stock price has fallen over 50%, causing a pivot in business plans.
If you truly wish to be "member's first", take a hard look at the dark patterns and the anti-member behavior/spam on the site and fix the experience.
Stop gauging things off of b.s. metrics and figure out if the product has actual utility and how to enhance that.
The process began with a technical 1:1 phone screen. This part was not very difficult; they tested basic algorithms and data structures knowledge. You had to code online and in real time with the interviewer using CollabEdit. The onsite interview wa
A very nice process, including an OA, phone screen, and then a Technical/Behavioral final round. I genuinely enjoyed the process and met some great people, which led me to accept the offer. Just make sure you have knowledge of your projects and can s
The interview was conducted over the phone, using a shared text editor from a testing site. The interviewer began with general experience questions and then moved on to technical questions about items listed on my resume. There was a basic question
The process began with a technical 1:1 phone screen. This part was not very difficult; they tested basic algorithms and data structures knowledge. You had to code online and in real time with the interviewer using CollabEdit. The onsite interview wa
A very nice process, including an OA, phone screen, and then a Technical/Behavioral final round. I genuinely enjoyed the process and met some great people, which led me to accept the offer. Just make sure you have knowledge of your projects and can s
The interview was conducted over the phone, using a shared text editor from a testing site. The interviewer began with general experience questions and then moved on to technical questions about items listed on my resume. There was a basic question