Pros: Good work/life balance. There is a culture of transparency from upper management. Very good benefits. Lots of training opportunities. The upper management seems dedicated to making the company a great place to work.

Cons: Pay is average or below, and advancement is very slow. As an engineer, it appears that the sales and support organizations are running well, but product development seems very broken. Huge amounts of unnecessary process burden all aspects of the product development cycle, from product definition down to the level of the individual code check-in. This results in some of the lowest productivity per engineer that I have witnessed. The engineers are working hard, but it is very difficult for them to get anything done. The upper management seems to want to change this, but the deep layers of middle management are so risk-averse that they seem to be locked in stasis until an EVP commands action. The HR policies are stuck in the 80's, with an oppressive annual review process (complete with annual goals), stack ranking, and a black-hole applicant tracking system that seems to grade every applicant unworthy of consideration. For those rare individuals that do get interviews (usually because the hiring manager bypassed HR), the risk-averse culture demands multiple rounds of interviews. I know of people hired only after running a gauntlet of 15-20 individual interviews, organized into 3 or 4 rounds.

Pros: Good culture, work-life balance, compensation.

Cons: None I can think of.

Pros: Work/life balance, collaborative culture, volunteer-time-off policy. I've had opportunities to work in different technology areas: product code, quality, and developer tools. The initiatives around quality have made it easier to find bugs sooner and back them out of the codebase. We are on a good trajectory in this area. I have great relationships with my colleagues and the first few levels of my management chain.

Cons: Life as a Data ONTAP developer has its frustrations. These start with access to the engineering environment (via the VMware Horizon client) and erratic build farm performance, which make it hard to be as productive as we'd like to be. Some programs were killed several years (and millions/billions of dollars) too late, and some acquisitions should never have been made. It's frustrating to see all this waste and to be told there's not enough money to make this or that improvement for developers.