| average scores for this employer | |
|---|---|
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 | unrated |
| use of GNU/Linux | unrated |
| use of Mac OS | unrated |
| use of Solaris |
|
| use of Windows |
|
| use of BSD | |
| use of Python |
|
| use of Perl | unrated |
| use of Ruby | unrated |
| 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 |
|
Boeing
-
average score:
- type of organization: public
- size: colossal (over 10,000 people)
- website: boeing.com
- development offices:
They make Airplanes, and (despite the "we don't do software" mantra) the software that they use.
1 rating
Rate this employer!-
Terrible place for devs
posted
on
September 14, 2009
I worked for Boeing for more than three years, right out of university. During that time, I spent two years on the same project. In two years, I managed to talk to the PM one-on-one exactly twice (PM's college major: communications. Hilarious!). I used the opportunities to explain everything that was wrong with our software project (more on that later), and was met with a deflection of blame. When management longer cares about producing something that more...