Juniper Networks

Good technical people, strong in hardware and networking knowledge.

A lot of middle-level management (Directors / Sr. Managers) are cautious and are only worried about their bug-fixing rate measure. The focus is on delivering on time; however, if crap is delivered, it is okay, plus you get credit for fixing bugs fast. There is no tracking of why there are so many bugs in the first place. Finally, nothing matters as most initiatives are scrapped.

1. Either spend money on projects or do not do them.

2. If someone promises aggressive deadlines, be wary. Phase 1, phase 2 will all be done in time, however, major issues will have been swept under the carpet. In the final phase, everything will be needed by then. The guys responsible will quit with huge rewards, leaving the real work to others who end up being blamed for a badly designed, badly managed project, which they are not responsible for.

Bottom Line: No rewards until all phases complete and HA and scale are really tested.

1. Most of sys-test are of very low standards, protected very fiercely by their managers. Juniper must not hire testers unless they are also coders. I have seen that in almost all systest teams, there are only 2-3 good testers. The rest are all simple black box testers. They request developers to share all unit test cases and then simply run the same tests most of the time. Apart from the 2-3 top guys in the team, the rest are all contributing nothing. The rest of the testing is done by these top 2-3 guys.