rating for Magenic



posted
by
ericksoa
on
December 12, 2006
* True project based work. The mix of staff aug to project work at Magenic leans heavily towards project based work. This gives Magenic more control over the project, leading to a greater chance of a successful outcome. This tide of success "lifts all boats" - so to speak - including the reputation and brand of the developers who work on said projects.
* Focused strategy. Magenic does the Microsoft platform. Thats it. This means that you wont be asked to work on PHP one month, Cobol the next month.
* True internal knowledge sharing. The internal tech lists form a knowledge sharing platform unmatched by other firms. By making it simple and email based, usage is encouraged. While you might be stuck on a problem for hours working for another company, at Magenic, you just send the question to the appropriate internal tech list, and you get very good answers - sometimes in minutes.
* Focus on the developer - Magenic has a position of Consulting Manager - whose job description is "keep the consultants happy". Seriously. What other companies do anything that compares?
* High bar to entry - Magenic hires very good .NET professionals. You can have faith that your co-workers are on the same level you are if you are here.
* Reasonable travel requirements - While travel is sometimes required for some clients - Magenic does a great job matching your desired level of travel to the actual amount of travel that you do.
* Great Reputation - If nothing else, having Magenic on your resume is a great door opener to speaking and authoring opportunities that simply dont exist at other companies.
All in all, as a consultant here myself - who has worked at lesser companies, I highly recommend considering Magenic in your career plans.
See 4 more ratings for Magenic!
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 | unrated |
culture | |
| cultivation of creativity |
![]() ![]() ![]()
|
| mitigation of risk |
![]()
|
| reasonable workload |
![]() ![]() ![]()
|
| prevention of crunch time |
![]() ![]() ![]()
|
| hitting deadlines | unrated |
| 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 | ![]() |
