Good work-life balance. You can easily stay at T5 while working 40 hours a week.
Technical depth. Google has many projects that are very technically deep.
Bad career path.
Most people stop at T5. To reach T6, you have to fight for leadership and ownership.
Communication overhead due to the sheer size of the company.
Personal growth. While you are exposed to interesting and technical deep projects, you are likely to get lost on how the entire infrastructure works. Bad if you want to build skills for running or joining startups.
Quick phone sync, very simple questions, and an explanation of the interview process. Then, a 45-minute interview with a software engineer. My software engineer decided he had more important things to do and left the call for 10 minutes, returning t
I had two in-person interviews. The first interview went poorly, and the interviewer provided solid constructive criticism. The second interview went well. After some consideration, they requested a third interview, which also went well, but they
The recruiters are friendly and helpful. They send material to you to help you prepare for interview questions. The tech call interview mainly focuses on a programming test. The test is not difficult.
Quick phone sync, very simple questions, and an explanation of the interview process. Then, a 45-minute interview with a software engineer. My software engineer decided he had more important things to do and left the call for 10 minutes, returning t
I had two in-person interviews. The first interview went poorly, and the interviewer provided solid constructive criticism. The second interview went well. After some consideration, they requested a third interview, which also went well, but they
The recruiters are friendly and helpful. They send material to you to help you prepare for interview questions. The tech call interview mainly focuses on a programming test. The test is not difficult.