[TruthPrevails]

My AWS team was good. I enjoyed my work as an intern. However I was warned that work in the group is operations intensive. I could see that myself in those 12 weeks. As an intern I was not given any operations work. Obviously it will change when I join as a full timer. As noted below I am looking at other AWS teams, Kindle silk browser team. I need to find out about these teams.

[skyo]

Yeah, I've heard that some AWS teams can have heavy operational load. If it's important to you to avoid that, you could consider somewhere in WAP/BuilderTools. That's where I work (so yes I am biased), and in my experience the operational load tends to be pretty light throughout the org. On my particular team we almost never get paged. Plus we get to build neat things in this org (remember how Stevey mentioned that Amazon's "versioned-library" system is good?).

Silk is probably a neat team to look into as well. They're building a cool product, they're still a small team, and they have good leadership. The director in charge of it used to be the head of Builder Tools and he's great.

But yeah, talk to a lot of teams and ask them about the things that are important to you (operational load, current/future projects, code quality standards, whatever other things you can think of to ask) and see if any of those teams sound cool to you. I won't lie and say that every place in Amazon is perfect, but if you choose well I think it's possible to find a great team to work on.

[TruthPrevails]

Just now found out that "no college hires" in Silk team. That sucks! College hires are high on energy and enthusiasm. I don't know why teams would not want college hires :(