Great pay, and it just comes with performance and promotions; you don't need to negotiate it. You get the chance to work with and learn from some amazing people. Very high code quality, not just at the level of coding style or individual classes, but the overall system architecture. Things tend to be really thought through, and stupid things don't happen.
The company is very helpful with immigration issues.
Good 401k program.
Google's tech stack is big and complex. You will be spending a lot of time figuring out how to plug together various systems and APIs.
You may be spending a lot of time looking at various status pages, trying to understand whether your tasks are doing what they should with acceptable performance, why not, and which obscure configuration option you need to tweak to make them.
A lot of what you will need to learn to do the job will be specific operational knowledge about how to work that unwieldy beast that is Google's infrastructure.
The code complexity is considerable, which means that implementing simple features can take much more time than you'd think it should. It also means it can take a lot of time to get to the point when you feel like you at least somewhat know what you're doing.
The company keeps the copyright to all your hobby projects. They have a system through which you can ask that the copyright be released to you on a case-by-case basis. Sometimes they'll say yes; sometimes they'll say no.
Keep up the good work.
I had one technical phone screen remotely and then flew to Mountain View for a day of in-person interviews. The in-person interviews were all technical and included coding elements. One interview was a bit more design-heavy. Travel is booked throug
I had two phone interviews. Both went well. The recruiter said they went well and wanted to bring me on-site. Then another recruiter called me and said they were not moving forward. There was no explanation or apology from either. It was a very s
An HR representative emailed me to schedule a phone interview. I suggested a date eight days from that Thursday. However, I was surprised when they called the next day. Since it was just the HR round, I provided some basic information about myself an
I had one technical phone screen remotely and then flew to Mountain View for a day of in-person interviews. The in-person interviews were all technical and included coding elements. One interview was a bit more design-heavy. Travel is booked throug
I had two phone interviews. Both went well. The recruiter said they went well and wanted to bring me on-site. Then another recruiter called me and said they were not moving forward. There was no explanation or apology from either. It was a very s
An HR representative emailed me to schedule a phone interview. I suggested a date eight days from that Thursday. However, I was surprised when they called the next day. Since it was just the HR round, I provided some basic information about myself an