rating for Google Inc.
posted
on
November 27, 2006
1) Huge emphasis on good code design -- stringent internal code style standards for uniformity, mandatory peer code review process, etc. -- makes it much easier to deal with code you didn't write yourself.
2) Lightweight managerial structure; while I have spent some time dealing with managerial bureaucracy, most of my time is spent writing code, and the sort of nonsense I've heard of at other companies -- projects constantly being redesigned so that code must be rewritten because management has had a change of heart -- is relatively rare here.
3) Programmers are treated really well. Exceptional food for lunch and dinner (in the NY location, I think Mountain View has breakfast, too), free beer and wine at least once a week, and most importantly a management tier that knows how to code, takes coders seriously, and treats them with respect.
See 6 more ratings for Google Inc.!
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 | unrated |
| development of Free Software | unrated |
| use of GNU/Linux | unrated |
| use of Mac OS | unrated |
| use of Solaris | unrated |
| use of Windows | unrated |
| use of BSD | unrated |
| use of Python | unrated |
| use of Perl | unrated |
| use of Ruby | unrated |
| use of Lisp | unrated |
| use of Java | unrated |
| use of C# | unrated |
| 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 |