There are a lot of interesting projects. The benefits are attractive; the compensation is reasonably high. Excellent work-life balance; it is easy to go part-time and to shift work hours around with ease.
Huge codebases accumulated over years imply a lot of mundane work to keep them in good shape, and added costs for making code changes for new features. Google does a better job of keeping code in a maintainable state than other companies I've worked for, but size still matters.
A straightforward process, exactly what the recruiter described. It involved several technical interviews and some personal interviews. When it wasn't clear if they could hire or reject me, they gave me an additional technical interview.
I applied for a Google SWE position and went through a recruiter call first. The recruiter was very friendly and clear about the process. My phone screen had two coding questions: * One on arrays (two sum variant) * Another on dynamic programming (u
First, an online assessment, then the HR call, then several rounds of technical interview (you need to solve data structure/algorithm problems), and finally a manager interview (mostly behavioral questions).
A straightforward process, exactly what the recruiter described. It involved several technical interviews and some personal interviews. When it wasn't clear if they could hire or reject me, they gave me an additional technical interview.
I applied for a Google SWE position and went through a recruiter call first. The recruiter was very friendly and clear about the process. My phone screen had two coding questions: * One on arrays (two sum variant) * Another on dynamic programming (u
First, an online assessment, then the HR call, then several rounds of technical interview (you need to solve data structure/algorithm problems), and finally a manager interview (mostly behavioral questions).