Pros
Google, despite its problems, is a great place to work for. With a few caveats, anyone interested in challenges should consider working here. 1. In contrast to recent complaints within the company about compensation, you are well compensated in engineering here. Period. You might be able to find better at a startup or another big tech firm, but make no mistake, Google pays highly overall. Look at the salaries page here on Glassdoor and you'll see that right away. 2. The office atmosphere in Boulder is great. As a satellite office with experienced-trending engineers, it's more relaxed than Mountain View with most of the same perks. A decent gym, bouldering wall, and full cafeteria are all things to mention. 3. Work life balance, while very team dependent, is generally superb . I work 8 hours a day, don't carry a pager, and feel no pressure to work more than that. I don't feel the slightest bit of scrutiny if I need to work from home, or go to a comfy nook somewhere out of sight to get some work done. 4. Again, in contrast to recent complaints from Googlers, the senior leadership at Google (thinking of Sundar here) is *very* open. Find me another 80,000 person company that has its CEO answer crowd-sourced questions on very emotional issues like compensation and diversity. 5. I generally have positive human interactions here. There's the typical swath of introverted and occasionally awkward engineers, but generally speaking everyone is "Googley", i.e. considerate at a level above the average human on the street.
Cons
The big cons fall into two categories: engineering and company. Engineering specific: 1. The internal tools, compared to open source projects and other companies, suffer from immense proliferation and domain overlap. There are too many ways to deploy code, too many ways to look at a metric graph, too many ways to build a Java library, too many ways to spin up an RPC server, and the list goes on. This ultimately means that none of the products are very satisfactory. There's too much license to "innovate" on the fundamental building blocks, and the engineering culture as a whole needs to enforce more standards. 2. It's an extremely common practice for engineers (i.e. with a title of software engineer) to have direct reports. The result is a bunch of very technical leaders who don't care as much about people operations. This is great when you need backing for a proposal, but sub-par when you need to talk about career development or other non-technical topics. 3. Technical Googlers are promoted predominately for "impact" - think launching a new service, or saving the company $Xm. There does not seem to be heavy motivation to promote engineers who work hard to maintain stable and important systems. It's a running joke that in order to get promoted, it's better to deprecate something reliable and create something new. In other words, Google is an excellent place to gain experience, but to get "promoted", you're probably better off seeking out new opportunities. 4. While mostly good people (especially at a company of 80k), Googlers can sometimes come across as entitled. Yes, finances in the Bay Area is hard even on a salary of $120k+, but the perspective on how much of a privilege it is to work here is sometimes lost. 5. Google is struggling with some of the same issues that the US is politically. The company has the best intentions, but does fall into a hysteria over "diversity". Less than 50% hiring of females in engineering is seen as a systemic problem. Google is slowly starting to realize that this is mostly a pipeline problem, especially considering that the industry (and company) makes enormous efforts to hire existing qualified women. However, leadership does not seem very interested in respectful but contrary opinions on this topic, as the firing of James Damore demonstrated. If you care about racial and gender equality, but have doubts about a leftist political agenda, you may occasionally feel afraid to speak up at Google.