Pros: Challenging problems, so you're never bored.

Cons: Way overworked and expected to spin diamonds out of bad situations.

Pros: At Amazon, you will excel if you are an extremely driven individual. If you are someone who absolutely adores coding, creating all kinds of scripts to make your job easier, and thinks about solutions day in and day out, then choose AWS. They will push, push, push. And if you can, push back. Make your code the best that anyone has seen, and you will have amazing results. If you want a job where you just go 9-5 and nothing outside of it, then AWS is not the place for you. You will have very long days, and though you can take the time off later, it can be very stressful.

Cons: Long hours. Very long hours, sometimes.

Pros: - Impact to a lot of customers - Pay better than most companies

Cons: Managers relied on metrics like the number of code review comments, the number of revisions before approval, and the number of lines of source code to conduct performance. I am fine with the metrics, but I am not fine with not defining the standard, like how many code review comments are good enough to be a software engineer. How many lines of source code contributed is good? Or how many revisions is good? Teammates did not help each other, and sometimes I felt my words were being purposely misrepresented for political gain. I attempted a meeting where the colleague mentioned he wanted to record the meeting, as he was afraid of being misrepresented. You may get blamed for not following some process written in an internal wiki, even though the process was written after the duties were performed. Not paying in par with companies of similar size.