Pros: Overall compensation, although it is getting worse and worse every year.

Cons: Being a programmer means being creative. Well, not at Google. You will have artificially created restraints in almost every aspect of your work. Here is an example: readability. In order to be able to commit some code at Google, you would need to have readability in a language you're writing this piece of code. It doesn't matter if you have 10 years of experience in that language. It doesn't matter if you have a certificate from the company that developed this language. And in order to get readability, you would need to write a lot of code in that language. Catch-22. Also, you would have to wait for a pretty long time in the readability queue in order to just start with the process. You feel like you lost all the experience you had before with this language. Somebody who has readability and has less experience in this language than you will have power over you. You would have to persuade this other person that your code is OK. Hypocrisy. They still have courses at Google where they teach you that it is important to have a rest, it is important to manage your energy, it is important to work when you are excited and energized and not work when you're not. This is why they have all those massage chairs. It used to be the company that valued all this. It all changed. I saw my manager writing at 2 am and then writing at 6 am again. A manager sets an example for their subordinates, and this example is terrible. I also remember my manager writing an email about his current state that he is sick. In the same email, he tells that "he will do his best to do some work." At the same time, this same manager tells everybody else that "if you're sick - go home and take a rest and don't work." I lost respect for my manager a long time ago. They want you to deliver results as soon as possible, and yet they don't give you the ability to do it. Instead of JUST DOING IT, you would have to write design docs with the future possible architecture (which will always be different because we can't predict software development) and persuade people who have more power than you. Those people will do their best to make sure you don't just start working on your code. You would have to pass several rounds of this absurdity. They told me it is very important to predict how much time it would take to finish the project. I asked them what the technique is to predict the unpredictable and got no answer in return. They told me it is very important to make sure you did your project as close to your predictions as possible. I asked them what stops people from deliberately giving very large estimates, completing a project sooner, and just doing nothing for the rest of the time. I got no answer in return. I completely lost respect for this company. This is absurd. The management don't think about what they are doing and why. They don't think about their own behavior and their own words.

Pros: Great work-life balance with adequate opportunity for career development.

Cons: You can feel that it's a really big company now – difficult to advance and a lot of red tape.

Pros: I learn a lot. Google pays for my Master's degree at Stanford.

Cons: My teammates are not great at English, and this sometimes results in miscommunication. It's a team-specific problem, though; my other Googler friends don't have this problem.