Pros: The quality of coworkers is pretty high; nearly everyone is pretty bright and fairly creative. The company is very flexible with its employees -- work matters more than hours and location. There are a number of interesting classes of problems to work on that are difficult to find elsewhere (large scale distributed systems, storage infrastructure, etc). The potential impact of your work is huge.

Cons: There's a culture of working long hours. The company is becoming larger and larger, which results in more processes and less creativity.

Pros: If you're a software engineer, you're among the kings of the hill at Google. It's an engineer-driven company without a doubt. That is changing, but it's still very engineer-focused. The perks are amazing. Yes, free breakfast, lunch, and dinner every weekday. Amazing holiday parties (at Waldorf Astoria, NY Public Library, MoMA, etc.); overnight ski trips to Vermont; overnight nature trips to the Poconos in the summer; summer picnics at Chelsea Piers; and on and on. I don't see this going away unless the company starts hurting financially. Speaking of which, the company is doing quite well, which reflects in bonuses and equity grants. There is a huge diversity of work, ranging from defending independent journalism worldwide (Google Project Shield) to crisis response during disasters (see Maps during Hurricane Sandy or Tsunamis), to the best machine learning experts and projects in the world, to more mundane revenue-driving projects in advertising. There's really something for everybody. It's easy to move around within the company, as long as you're in good standing (the vast majority of engineers are). The company is amazingly open. Every week, Larry Page and Sergey Brin host what's called TGIF, where food, beer, wine, etc., are served. A new project is presented, and afterward, there's an open forum to ask the executives anything you want. It's truly fair game to ask anything, no matter how controversial, and frequently the executives will be responsive. No, nobody cares if you use an iPhone, Facebook, shop with Amazon, stream using Spotify, or refuse to use Google+. The company is amazingly open and flexible. Neither pro nor con, but general information on work-life balance, promotions, and advancement. Work-life balance can be what you want it to be on most teams. Some teams are in more competitive sectors and require more crazy hours all the time, but very few of them. If you do what's expected, you'll be fine for at least a handful of years. Working a roughly 40-hour work week is possible, and many people do it. There are also people who are hyper-motivated and work like crazy just because they love it, or because they're competitive, or they want to get a promotion. If you work 40-hour weeks without putting in anything extra, you'll fall behind them as they advance, and you'll stand still. Maybe that doesn't matter, so it works out for everybody. But at least know where you would realistically stand. If you excel and work your butt off, you'll be compensated and promoted. If you let yourself be a code monkey and just sit coding with your head down all day, you'll be fine but won't advance. A big complaint from some Googlers is about not being able to advance "even at Google" with pure coding. Sure, if you're the uber-genius who created MapReduce and Bigtable, you're going to advance like a rocket without having to do anything but coding. But if you're like most engineers at Google—smarter than average, but just average compared to other Googlers—you're just a good coder and not revolutionary. Code monkeys are important to actually get stuff done, and to be sure, you absolutely need to be a good coder as a software engineer (it's the minimum requirement). But code monkeys won't advance because they're not leaders and they're easy to replace. To get promoted, you need to lead and do more than just code. There are plenty of ways to lead other than being an official tech lead, so this isn't actually that hard. The real point is just that you can't just sit there coding what other people tell you to code all day and expect to advance.

Cons: It is becoming larger, and with it comes growing pains: bureaucracy, slow to respond to market threats, bloated teams, cross-divisional tension (though nothing remotely approaching that of Microsoft's internal tension). The quality of the engineers is possibly dropping, but possibly not. It's hard to get real metrics. As the absolute number of people grows, naturally the number of bad apples grows. As a percentage, it's supposedly the same as it ever was, but with larger numbers of poorer quality engineers, it just feels like things might be changing for the worse. Also, with growth comes more internal-confidential data leaks (again, because of the raw numbers of people) -- product announcements being ruined, etc. That means the company has to be tighter-lipped internally to avoid leaks, which makes things less open. It's still an amazingly open place, but less so than it was even a couple of years ago. The good thing is they recognize it and actively look to improve things because they know how important it is to keep the good culture.

Pros: Good work-life balance, good pay, good leadership.

Cons: Too many proprietary tools to learn.