Same as other big N companies. The coding experience is seamless, and there weren't any serious pain points. You don't have to think about testing, building, deploying, and so on, because everything has already been done for you.
I preferred Google's work culture. I didn't really get to know the team, and I felt that generally, people were less engaged and personally interested in the work. In comparison, it almost felt a bit... enterprise?
The interview process involved two phone screening interviews and one on-site interview. The on-site interview consisted of five 45-minute sessions. These sessions covered the following areas: * Systems * Systems design * Coding * Behavioral * Net
I was contacted by a Facebook recruiter in April for a data engineering position in their Menlo Park location. I scheduled my phone screen in May and passed it. It mainly consisted of SQL questions, as mentioned in other posts here. The next part wa
Did three rounds of interviews. First round: design a system to detect homeworking copying, which means input two strings and an integer K. If there is a common substring of them with a length larger than K, return true; else, return false. Second
The interview process involved two phone screening interviews and one on-site interview. The on-site interview consisted of five 45-minute sessions. These sessions covered the following areas: * Systems * Systems design * Coding * Behavioral * Net
I was contacted by a Facebook recruiter in April for a data engineering position in their Menlo Park location. I scheduled my phone screen in May and passed it. It mainly consisted of SQL questions, as mentioned in other posts here. The next part wa
Did three rounds of interviews. First round: design a system to detect homeworking copying, which means input two strings and an integer K. If there is a common substring of them with a length larger than K, return true; else, return false. Second