Free food.
Pay is good.
Friendly people (faked sometimes, but not backstabbing in my experience).
Free gadgets from vending machines.
No real owners on code, so in theory, you can make changes to any team's codebase (it can backfire, though).
Up or out culture: if you don't get promoted to a certain level in a set time, you're fired.
Poor work-life balance due to the up or out culture.
If more seniors on your team are workaholics, you are compared against them harshly.
Oncall infra can be nightmare-inducing.
Again, you must really love what you do and your team if you want to be happy here.
It's difficult to move to another team if you get a 'Meets Most' rating in a half. HR won't help you since it's a hard rule (I think it was updated to 2 halves recently).
Aggressive goals can cost the health (physical and mental) of employees. People who just enjoy their work but don't love it will have a hard time with the constant threat of getting fired or stuck on a team.
Calibrations is only a 3-minute exposition per person. It's difficult to show the whole 6 months of a person's activities in that time. Also, the calibration bar seems to be pushed up by workaholics, so other people are reviewed more harshly.
There was a 45-minute phone interview where I was asked to write code in an online editor, and then a 45-minute onsite interview where they flew me out to the Menlo Park campus. Overall, the recruiters were super friendly, and I really enjoyed the ex
Initial 45-minute screen: whiteboard coding problem, algorithmically simple, but with oddities. Full loop: 6 x 45-minute sessions: * 2 coding * 2 design * 1 cultural/technical (tell a story about a difficult experience and how I overcame) * 1 lunch
I decided to do the phone interview onsite. The interviewer was friendly and helpful, and I solved the question fairly easily. My onsite interview included: * One behavioral question * Three coding rounds, each with two questions. Since I completed
There was a 45-minute phone interview where I was asked to write code in an online editor, and then a 45-minute onsite interview where they flew me out to the Menlo Park campus. Overall, the recruiters were super friendly, and I really enjoyed the ex
Initial 45-minute screen: whiteboard coding problem, algorithmically simple, but with oddities. Full loop: 6 x 45-minute sessions: * 2 coding * 2 design * 1 cultural/technical (tell a story about a difficult experience and how I overcame) * 1 lunch
I decided to do the phone interview onsite. The interviewer was friendly and helpful, and I solved the question fairly easily. My onsite interview included: * One behavioral question * Three coding rounds, each with two questions. Since I completed