| 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 | ![]() |
| use of GNU/Linux | ![]() |
| use of Mac OS | ![]() |
| use of Solaris | ![]() |
| use of Windows |
![]() ![]() ![]()
|
| use of BSD | unrated |
| use of Python | ![]() |
| use of Perl | ![]() |
| use of Ruby | ![]() |
| use of Lisp | ![]() |
| use of Java | ![]() |
| use of C# | ![]() |
| use of Objective-C | unrated |
| use of C | ![]() |
| use of C++ |
![]() ![]() ![]()
|
| use of PHP | unrated |
| use of ASP | unrated |
| use of legacy languages | unrated |
Flying Lab Software
-
average score:



- type of organization: private
- size: small (11 to 50 people)
- website: flyinglab.com
- development offices:
A Seattle game studio, currently working on the award-winning MMO Pirates of the Burning Sea.
1 rating
Rate this employer!-



Yarr!
posted
on
September 04, 2006
I have never enjoyed working someplace as much as I love working at the Lab. True, it's an all-windows environment, but what do you expect from a small game company?
The company doesn't feel segmented; I've gone out to lunch and even dinner with most of the people in the company. The founders are absolutely great guys. And everyone (especially the leads) understands what it takes to make a great game, and are ready to do The Right Thing.
