rating for Amazon.com

posted
on
October 04, 2006
* Oncall -- engineers are typically part of an oncall rotation for the features their group owns. This is usually 1 week of 24/7 pager duty. Recently, they've made engineers the first teir of support for the databases.* Operational load -- about 30% of your time is spent keeping the existing systems running. Not maintaining code, literally keeping the systems running. Planning migrations from one version of the operating system to the next, allocating hardware, deploying, backfilling your caches, handling the fallout from network events, handling urgent requests from business groups. Some teams have more operational load than others. Much more. The plus side is that you're working with brilliant people, and dealing with scaling problems that almost no one else has. With the variety of stuff you need to handle, and the complexity of the problems, it's an excellent training ground for someone who wants to be the CTO of a startup.Amazon has a culture of cheapness which is fairly annoying. Desktop and laptop equipment is not the best that money could buy, it's barely adequate for the job.Turnover is very high -- leaving at two years is very common, and many people don't even make it that long. At a recent tech-talk by one of our senior managers, he mentioned that the team had 200% turnover while he was there -- three years. Promotion between levels (there are three levels for engineers -- plus the big wig engineers, so four) is ill-defined.Office space is often very tight, and the cafeteria at PacMed is not good. The location is convenient, though.It's a very good spot for a junior engineer, right out of college, getting their feet wet. You'll learn more than at any other company, and faster too. Curiously, it's also a good place for older employees -- I haven't seen the usual age discrimination there, and you see lots of grey haired developers (surely they cannot all have gone grey early!).I don't regret coming to Amazon, but I also don't think I'll hit the three year mark.
See 24 more ratings for Amazon.com!
0 comments
Write a comment!| scores in this rating | |
|---|---|
development process | |
| clear requirements |
![]()
|
| design and planning |
![]()
|
| quality assurance |
![]()
|
| automated testing |
![]() ![]()
|
| peer review |
![]() ![]()
|
| development environment | ![]() |
| development hardware | ![]() |
| physical workspace | ![]() |
| infrastructure and support | ![]() |
| issue tracking |
![]() ![]()
|
| source control |
![]() ![]()
|
| product quality |
![]() ![]() ![]()
|
culture | |
| cultivation of creativity |
![]() ![]() ![]()
|
| mitigation of risk |
![]()
|
| reasonable workload |
![]()
|
| prevention of crunch time | ![]() |
| hitting deadlines | ![]() |
| taking responsibility |
![]() ![]() ![]()
|
| development autonomy |
![]() ![]() ![]()
|
| keeping ego in check |
![]() ![]()
|
compensation | |
| salary |
![]() ![]()
|
| health coverage |
![]() ![]()
|
| paid time off |
![]()
|
| snacks | ![]() |
| other perks | ![]() |
organization | |
| advancement opportunities |
![]() ![]() ![]()
|
| employee retention | ![]() |
| hiring process |
![]() ![]() ![]()
|
| quality of development management |
![]()
|
| quality of upper management |
![]()
|
| quality of developers |
![]() ![]() ![]()
|
| team-to-team communication | ![]() |
| internal team communication |
![]() ![]()
|
| management-developer communication |
![]()
|
general | |
| location |
![]() ![]() ![]()
|
| nearby food | ![]() |
| business model |
![]() ![]()
|
| cool technology |
![]() ![]() ![]()
|
| vision and strategy |
![]() ![]()
|
| warm fuzzy feeling |
![]()
|
| overall |
![]()
|
preferences | |
| casual dress code |
![]() ![]() ![]()
|
| use of Free Software |
![]() ![]() ![]()
|
| development of Free Software |
![]()
|
| use of GNU/Linux |
![]() ![]() ![]()
|
| use of Mac OS | ![]() |
| use of Solaris | unrated |
| use of Windows |
![]()
|
| use of BSD | unrated |
| use of Python | ![]() |
| use of Perl |
![]() ![]() ![]()
|
| use of Ruby |
![]()
|
| use of Lisp | unrated |
| use of Java |
![]() ![]() ![]()
|
| use of C# | unrated |
| use of Objective-C | unrated |
| use of C | unrated |
| use of C++ |
![]() ![]()
|
| use of PHP | unrated |
| use of ASP | unrated |
| use of legacy languages | unrated |
