"Openness", which means you can see and submit diffs on almost everyone's code, and you can see the direction and accomplishments of other teams.
"Move fast and break things" applies to internal tools and infrastructure. Things broke often enough that I remember it as an annoyance.
I had one interview on campus, and then after one week, I had an onsite call. I went to the headquarter in Menlo Park for the onsite. At the onsite, I had five 1:1 interviews. The interviewers were very friendly. Just an advice: always try to go t
One phone screen followed by four on-campus interviews. Standard coding questions, one highly scalable design question, and questions about past projects. Check out David Malan's scalability lecture on YouTube. That's a good starting point. Write
For the on-site interview, I had two rounds of algorithms questions and one behavioral round. The coding rounds were each an hour long and asked two questions. Overall, the process felt pretty organized and standardized.
I had one interview on campus, and then after one week, I had an onsite call. I went to the headquarter in Menlo Park for the onsite. At the onsite, I had five 1:1 interviews. The interviewers were very friendly. Just an advice: always try to go t
One phone screen followed by four on-campus interviews. Standard coding questions, one highly scalable design question, and questions about past projects. Check out David Malan's scalability lecture on YouTube. That's a good starting point. Write
For the on-site interview, I had two rounds of algorithms questions and one behavioral round. The coding rounds were each an hour long and asked two questions. Overall, the process felt pretty organized and standardized.