Pros: 1. High pay 2. Tech stack is up to date 3. Teammates are cooperative 4. Managers are supportive

Cons: Benefits are not ideal: * Few paid holidays

Pros: Good sign-on bonus and initial stock awards. Opportunity to work with very large distributed systems at uncommon scale. Working for Amazon Web Services looks good on the resume. Opportunity to get better at operations and how to debug and fix issues more efficiently, although sometimes under a lot of pressure. Learn development from end to end: design to deployment to operations. Dynamic: depending on the team, you will have the feeling of being in a startup but without worrying about having money for your project.

Cons: - You do some development, but you are not a software developer. The title "software development engineer" is misleading, and this is the first thing to be aware of when considering Amazon as an employer. You may develop, but the vast majority of people spend most of their time doing other things, like fixing issues, testing, documenting, trying to plan the project, handling bureaucracy, adapting existing code, and doing some program and project manager work. After a few years at the company, I would say that I may have actually coded 10% of the time. You are more of a "software engineer" if this breadth of experience attracts you, but few will be technical experts that develop a lot. - Operation burden: There are teams that suffer with a lot of operations, and the vast majority of developers need to be on-call. Yes, you will be tied to a pager. The problem is that pager duty is usually 24 hours for 7 days, and there is little to no respect from management for people that have to work around the clock. Don't expect to have a follow-the-sun model or any other arrangements unless things are very ugly (particularly true for AWS). Just to give you some numbers, there are teams that get paged more than once every hour of the day (yes, 25+ pages a day). You are expected to be online in a few minutes, so don't think that running a quick errand while on-call is a good idea if you are on such a team. - Long hours: Examples are better than just saying things here. These were rewarded in AWS' all-hands meetings: a developer who called in to help debugging a ticket during his daughter's wedding, and another developer that was working while his wife's baby was being delivered. This is the message that is sent, and the bar is set so high about dedication that, if you try to meet it, your life will be your work. Many do, especially if they are young. Some even seem to think it's worth the effort. - Long-term compensation: Amazon typically offers good sign-on bonuses and initial stock awards, but what is not said is that these bonuses and awards are going to be used in the following years not to give you any additional bonuses (manager's talk is "including your shares and sign-on bonus, your compensation this year is pretty good, so I can't give you anything else"). There isn't a cash bonus during performance review, and when managers give you stock awards, they are much lower than your initial stock awards. - Short-sighted: Although Jeff Bezos is visionary, Amazon is still not a technology company, and all development is targeted at the near future and how much revenue it will bring. Some AWS platforms would require much long-term investment and vision to be more reliable or develop in-house expertise, but they are often rushed for business' sake, which affects a lot of technical decisions. Although backed by a multi-billion business, Amazon is still not the company that will invest a few years into an effort without seeing the dollar value of that venture. - Lack of QA teams: Since it's short-sighted, QA is very much below what one would expect for such a large company with such systems - especially if we are talking about infrastructure for so many other companies, like AWS is. It's not uncommon to see tens of SDEs without a single person dedicated to testing (QA engineer, SDETs). - No learning/training on the job: Do not expect to have much chance of learning on the job. You must do it on your own if you want your career to progress. - Career progression: Your chances of career progression vary substantially depending on the business. Retail, AWS, and Digital are very different in terms of promotion, and depending on your group, the bar may be so high that it seems impossible to meet it in practice. That opens up a lot of opportunities for politics to take place. You may be stuck in your position for many and many years – do not be surprised to see competent people being SDE II for 10+ years, without prospects of any advancement. Also bear in mind that, although you can transfer internally, in practice, that resets your history, so you better put up with your current team and do what your manager wants if you want to have any chance of being promoted. - Benefits/Frugality: They are OK, but nothing compared to other companies. You will have 6 paid holidays – no day after Thanksgiving for you, for instance. You will have to pay for your coffee at company meetings. Good, but not the best hardware for your development – it’s not uncommon to see people paying out of their pockets for a keyboard, more memory, a better chair, and sometimes even buying or bringing monitors from home. Depending on the org, you will be able to expense books, but oftentimes, it will be so much work to get your manager's approval (including proving that it's work-related) that it will not be worth all the effort. Team lunch? Be prepared to chip in, as team events are rare, and, not uncommon, your manager's budget will not cover it all.

Pros: - Challenging projects to work on. - High salary. - Nice working environment.

Cons: - Not many extra benefits.