Coderific

rating for Amazon.com

1.0 Massive legacy codepiles... posted on January 31, 2008

Most of the SDEs here spend most of their time trying to keep the hack-filled legacy systems alive, rather than doing any development or engineering.

Computing resources... minimal. Amazon buys budget computers for everyone, and refuses to retire them until they're three years old, so it's quite common for developers to be working on computers that haven't even been in production for a year or two, and weren't anywhere close to state of the art when Amazon bought them.

There's not much engineering going on here. Most of the work is entry-level stuff; bug fixes, integration, some optimization. Between that and the ticket rotation, very few people here have time to do any development.

The technology is mostly ancient. A lot of mission-critical software is written in Perl, and relies heavily on constant reboots to stay alive. Very little of the company's mission critical software isn't ready for production. The code is largely undocumented and very brittle.

One side effect of this is that it makes adopting new technologies harder; Amazon has not moved up to jdk 1.6 yet, and there's even some software that requires jdk 1.4.

Benefits are stingy... the leave policy is atrocious. If you are considering working here, ask for more leave; the default is 2 weeks and a measly six holidays (no, that's not a joke). They've realized that they can't hire anyone senior with such stingy benefits, but they're still not willing to revise their policy... instead managers make under-the-table deals with recruits because most of the teams are chronically understaffed.

On the bright side, the company does a good job of hiring good developers. It just doesn't do a good job of using the skills that they interview for.

See 22 more ratings for Amazon.com!

0 comments

Write a comment!
    scores in this rating

    development process

    clear requirements 2.0
    design and planning 1.0
    quality assurance 1.0
    automated testing 2.0
    peer review 2.0
    development environment 1.0
    development hardware 1.0
    physical workspace 2.0
    infrastructure and support 1.0
    issue tracking 2.0
    source control 2.0
    product quality 1.0

    culture

    cultivation of creativity 3.0
    mitigation of risk 1.0
    reasonable workload 3.0
    prevention of crunch time 2.0
    hitting deadlines 2.0
    taking responsibility 2.0
    development autonomy 1.0
    keeping ego in check 1.0

    compensation

    salary 4.0
    health coverage 3.0
    paid time off 1.0
    snacks 2.0
    other perks 2.0

    organization

    advancement opportunities unrated
    employee retention 1.0
    hiring process 4.0
    quality of development management 3.0
    quality of upper management unrated
    quality of developers 4.0
    team-to-team communication 1.0
    internal team communication 4.0
    management-developer communication 3.0

    general

    location 3.0
    nearby food 3.0
    business model 4.0
    cool technology 1.0
    vision and strategy unrated
    warm fuzzy feeling 1.0
    overall 1.0

    preferences

    casual dress code 4.0
    use of Free Software 3.0
    development of Free Software 1.0
    use of GNU/Linux 4.0
    use of Mac OS 1.0
    use of Solaris 1.0
    use of Windows 4.0
    use of BSD unrated
    use of Python unrated
    use of Perl 4.0
    use of Ruby 1.0
    use of Lisp 1.0
    use of Java 4.0
    use of C# 1.0
    use of Objective-C unrated
    use of C unrated
    use of C++ unrated
    use of PHP unrated
    use of ASP unrated
    use of legacy languages unrated