Taro Logo

Some great teams, and a lot of terrible teams

Software Engineer II
Current Employee
Has worked at Amazon for 4 years
September 24, 2013
Seattle, Washington
3.0
RecommendsNeutral OutlookNo CEO Opinion
Pros

Great tools for programmers. A lot of them are very proprietary, but the concepts are there, and the whole software ecosystem meshes together well.

Some really smart people are scattered throughout the company. I've learned a ton being here.

If you find the right team, you can build products that customers love and have some say in how they're built. If you find a small team that's missing, say, a project manager, you get the chance to take on different roles.

The "leadership principles" – while receiving a lot of scorn from some employees – are awesome guiding principles for how to act. They're burned into my brain for the rest of my life.

Cons

Lots of crappy programmers. The blind leading the blind means many college hires get indoctrinated with bad practices.

Here's your choice of teams:

  • Small agile teams that are building cool products quickly
  • Massive orgs that have built themselves into corners and make every simple task take days to get right
  • Teams owning some of the oldest software in the company with crazy high attrition rates (think avg 6-8 months)
  • Teams that grew too fast and have 10 awful hacks for every good programmer, causing nightmares for whoever's on call.

If you're looking to work at Amazon, you NEED to talk to the manager/coworkers on the team you're being hired for. If they look defeated and sad, look elsewhere!

Advice to Management

The best teams are small and agile. Building a huge organization and trying to coordinate across it just gets you in the area of diminishing returns. Asking people to move quickly and hamstringing them by forcing them to use crappy tools is pretty Orwellian.

Was this helpful?

Amazon Interview Experiences