rating for Dexia
posted
on
May 27, 2008
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 | ![]() |
| use of Windows |
![]() ![]() ![]()
|
| use of BSD | ![]() |
| use of Python | ![]() |
| use of Perl | ![]() |
| use of Ruby | ![]() |
| use of Lisp | ![]() |
| use of Java | ![]() |
| use of C# | ![]() |
| use of Objective-C | ![]() |
| use of C | ![]() |
| use of C++ | ![]() |
| use of PHP | ![]() |
| use of ASP | ![]() |
| use of legacy languages | ![]() |
